My learning programming journey. I will create something useful for BHW!

Damn, you started coding a few days back and you're already sending targeted mass DM's on a site?

Outstanding, keep on going!

PS:
Don't forget me when you'll reach that $1 mil soon.
 
Damn, you started coding a few days back and you're already sending targeted mass DM's on a site?

Outstanding, keep on going!

PS:
Don't forget me when you'll reach that $1 mil soon.
Thank you so much, mate.

You can also suggest me more things to learn. I am open to new informations all the time. I will do my best.

For now at least I can do the basic math, conditions, loops, http requests and controlling Chrome browser with selenium also.
 
13th day:

- Studied basic ASP.NET Core lessons

- Learned MVC (Model View Controller) architecture

- Learned about Razor in ASP.NET

- Created a basic CRUD database application where you can enter and edit and delete your posts with Entity Framework

- Sent some test http requests to some public example APIs in my ASP.NET Core MVC web application
 
You can also suggest me more things to learn.
I'm only experienced with Python. Started from the beginners books to the more advanced ones by O'Reilly.

What helped me a lot in web automation is getting to fully understand the HTTP protocol, so in many cases I can find workarounds of my own to what seems to be unbreakable issues on the outside.

I saw you're playing with some requests. Web is made of HTTP transactions, if you master that, you might be able to rule part of the highway.

Then there comes fingerprint detection/prevention on the app side. This is mostly a Javascript thing which I'm just starting to dive into. I highly recommend getting to know about this also.
 
Really good progress man. Like @aurim mentioned, learning requests is a goldmine. You're getting into some pretty good stuff! Do you have a pretty good grasp on OOP principles yet?
 
I'm only experienced with Python. Started from the beginners books to the more advanced ones by O'Reilly.

What helped me a lot in web automation is getting to fully understand the HTTP protocol, so in many cases I can find workarounds of my own to what seems to be unbreakable issues on the outside.

I saw you're playing with some requests. Web is made of HTTP transactions, if you master that, you might be able to rule part of the highway.

Then there comes fingerprint detection/prevention on the app side. This is mostly a Javascript thing which I'm just starting to dive into. I highly recommend getting to know about this also.
Any good sources to maater http part?
 
Thank you so much, mate.

You can also suggest me more things to learn. I am open to new informations all the time. I will do my best.

For now at least I can do the basic math, conditions, loops, http requests and controlling Chrome browser with selenium also.
looks like you know your stuff already.

I tried to learn coding to automate a simple task but gave up. Ended up paying someone to do it for me.
 
Any good sources to maater http part?
This is the book name: HTTP: The Definitive Guide.
For 'innovation' to name it so, apply your knowledge in ways that defy constraints. Stay curious.
 
Last edited:
Really good progress man. Like @aurim mentioned, learning requests is a goldmine. You're getting into some pretty good stuff! Do you have a pretty good grasp on OOP principles yet?
Yes I became better at OOP principles and concepts. However, if I go into deep with this subject, all of a sudden it gets complicated a lot especially with .NET and C# ecosystem.

Such as Design Patterns or Enterprise Architectures in projects, it really looks like hell and feels like I will never learn it LOL. So boring part.

Anyway when my code does the job, why should I learn the detailed architectures?
 
And the thing is when I try to develop web based app, you need to know lots of design related front-end languages such as:

HTML, CSS, JS.

Some frameworks like Bootstrap, and JS frameworks: angular, react, jquery etc etc.

Too many things to learn and the design part is also boring. This is a very long-term journey, no matter how fast you grasp or how hard you work.
 
Anyway when my code does the job, why should I learn the detailed architectures?
You would want to do that once you want to get more serious about it. This can be because you want to scale, build and sell a project or service or just become more experienced so you always have an option of a fat paycheck.

Another thing is: by lacking fundamentals, when things go wrong you don't know why that happened. You will need help of a developer who took the time to learn things the proper way.

Too many things to learn and the design part is also boring.
Being a full-stack developer is hard (to stay sane) and isn't for everyone. This is where delegating or making a team can make sense.
For example, I'm great at backend, hooking up things together behind the doors, if I need a proper frontend I better delegate.
 
15th day:

- Studied on basic HTML, CSS and JS. It was not that hard because now I know programming concepts and logic. Also copied some jquery codes to help my projects

- Studied PHP basics

- Got deep into SQL commands

- Created a custom cloud project where I can keep my private notes. Created this cloud database application with: HTML, CSS, JS, PHP, SQL. Codes were in plain spaghetti PHP. But anyway I uploaded this project to my own hosting. Now I have a private custom web based note application. PHP was fun to develop with too!

Now from now on, I really don't know on which subject I need to keep on going. There are too many languages and frameworks. Now I know lots of basic things:

HTML, CSS, JS, PHP, SQL, C#, ASP.NET, Python.

But I don't know which web framework should I choose to keep going: Django, PHP Laravel, Or ASP.NET Core MVC?

We'll think and see.
 
I've learned programming by myself on Youtube channels and it was quite efficient .
You tried learning on Youtube ?
 
Good luck! Following!

My recommendation is to make your own small projects. Or to make a "bigger" project yourself, e.g. Customer Billing System. Integrate it with the database, create a backend API, a frontend interface... that's where you'll learn the most. Also publish your work on GitHub (thank me in a year).
 
22nd day:

Now I know:


HTML5, CSS, JS, PHP, SQL, C#, ASP.NET Core MVC, Python.

Http requests, Database CRUD operations, OOP concepts, A little design patterns, Git and GitHub.

Still not a professional backend coder or frontend designer of course, but I can create tools.

I still don't know:

What to create and publish.

What to learn more.
 
This feels like a very misleading thread. Not trying to be that guy, but saying you've learned all these things in just 22 days is very misleading, especially when you're using AI to create these tools on your behalf. While I love to play around with ChatGPT, just like anyone else, I also see how AI will be used to create a generation of poor programmers. For example, what do you do when asking it to continue doesn't work (ie: continuously starts from the beginning, skips lines of code, uses variables / modules that don't exist, etc)?
How about when it spits out code outside of code blocks? How about when there are errors and it fails to correct the errors when you tell it about them?

Do you know how to debug that code?
Saying that you developed these tools that AI actually developed on your behalf, can be quite misleading to new people wanting to get into the industry of programming.

When you use ChatGPT to write code for you, are you studying every line of the code and manually recreating it for yourself to truly understand how it works, or are you simply reading the comments it generates along with the code?

I guess what I'm getting at, is if ChatGPT goes away on January 1st (or whenever, as the date has not yet been disclosed to conclude this open beta test), will you be lost when it comes to writing code? Will you need to start over? If the honest answer is 'yes', then I either suggest using ChatGPT to truly learn the way to create things you want to build, or taking an actual programming course -- or both. I know a course was mentioned earlier, but don't substitute that for ChatGPT as the replacement.

ChatGPT is a supplement. It's like a protein shake. It's not a replacement for food.

Good luck on your journey. I love to see new programmers entering into this space, and so I hope you do well. Keep the motivation and keep going. You have the potential to do really well, but please know the difference between knowing about something and actually knowing it. To say you "know" Python (and all that other stuff) in less than a month, is a bit misleading.
 
This feels like a very misleading thread. Not trying to be that guy, but saying you've learned all these things in just 22 days is very misleading, especially when you're using AI to create these tools on your behalf. While I love to play around with ChatGPT, just like anyone else, I also see how AI will be used to create a generation of poor programmers. For example, what do you do when asking it to continue doesn't work (ie: continuously starts from the beginning, skips lines of code, uses variables / modules that don't exist, etc)?
How about when it spits out code outside of code blocks? How about when there are errors and it fails to correct the errors when you tell it about them?

Do you know how to debug that code?
Saying that you developed these tools that AI actually developed on your behalf, can be quite misleading to new people wanting to get into the industry of programming.

When you use ChatGPT to write code for you, are you studying every line of the code and manually recreating it for yourself to truly understand how it works, or are you simply reading the comments it generates along with the code?

I guess what I'm getting at, is if ChatGPT goes away on January 1st (or whenever, as the date has not yet been disclosed to conclude this open beta test), will you be lost when it comes to writing code? Will you need to start over? If the honest answer is 'yes', then I either suggest using ChatGPT to truly learn the way to create things you want to build, or taking an actual programming course -- or both. I know a course was mentioned earlier, but don't substitute that for ChatGPT as the replacement.

ChatGPT is a supplement. It's like a protein shake. It's not a replacement for food.

Good luck on your journey. I love to see new programmers entering into this space, and so I hope you do well. Keep the motivation and keep going. You have the potential to do really well, but please know the difference between knowing about something and actually knowing it. To say you "know" Python (and all that other stuff) in less than a month, is a bit misleading.
I agree with this. OP, you should look into the Dunning-Kruger effect. Right now you're at the peak of "Mount Stupid". You aren't stupid, you're just at a place where you don't even know what you don't know.

Take your time to actually build and understand things. Don't let AI do it for you. You mentioned earlier in the thread that you know MVC architecture now. Have you built anything using proper MVC, or just had AI spit out some boilerplate code that you copy/pasted. Do you understand the purpose of MVC?

This isn't an attack, so please don't take it that way. Software Development is a super deep field. I'm proud you've been looking into so many different things, but dive a bit deeper into things before moving onto the next and deciding you know them. :) You'll be better off for it in the long run!
 
Back
Top