Thank you so much, mate.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.
examples?bots making more than 20k/monthly on passive
Are you using puppeteer or cheriobots making more than 20k/monthly on passive
I'm only experienced with Python. Started from the beginners books to the more advanced ones by O'Reilly.You can also suggest me more things to learn.
Any good sources to maater http part?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.
looks like you know your stuff already.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.
This is the book name: HTTP: The Definitive Guide.Any good sources to maater http part?
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.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?
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.Anyway when my code does the job, why should I learn the detailed architectures?
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.Too many things to learn and the design part is also boring.
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.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.