13. is gold! Thinking in MVP is a golden skill. 16. Algos and DS are needed. They are not the goal, but you should know what they are so you dont reinvent the wheel. 25. Tech books are not overrated, if you don't educate yourself you will not work smarter. Also look at point 16 :D The rest is awesome! Thanks for the list, coming from an almost 10 year engineer
This mania to discredit proper education in the basis of CS only creates issues and gaps in the knowledge that are really detrimental to growing in the carrer.
I am a certified professional Java programmer, pretty high level coder. But primarily, a backend developer. I just recently started working with AWS, and a few days ago started learning JS and Node.js. And due to my previous experience with Java programming language, and most of the OOP concepts i picked up with just perfecting myself in one programming language, i am able to accelerate my learning of JS, where basically in a few days i can start building web applications and some serious projects using this language and its technologies. With GPT now, i can learn these things like 50x faster than before. The most important thing is to learn and perfect programming in general and application development, learning and addapting to a new technology becomes a non issue.
Algorithms, like money, don't matter when you got 'em, because whether you realize it or not, it's all algorithms in software. Algorithms and data structures pretty much, yeah. The best way to "got 'em" is not to learn them, but to try and understand them: what basic steps they're built out of, why those steps are the best way to achieve your goal and how they apply to structures you work with. It's actually kinda fun, too. Well, like learning in general.
1. How do you develop transferable skills unless you’re actually building experience in lots of different libs, frameworks, languages, etc, and transferring your skills? Instead, become an expert of the common patterns used across frameworks, languages, libs, etc. Use more things, try more things, not less. 2. lol what are the fundamentals? Again, I think it’s the common patterns that are important. Should probably elaborate on that now but it’s a CZcams comment so I won’t.
thank you for this, we will add these points to our next videos. Particularly "what are the fundamentals" question which a lot of devs struggle with, thanks again!
1. Stick to one framework 2. Focus on the fundamentals 3. Believe in yourself 4. Always negotiate your salary 5. Ignore nasty people 6. Don't take anything personally 7. Confidence comes from competence, but it also comes from clarity (know what you don't know) 8. You get motivated by getting this done, not by watching motivatonal videos 9. Technical interviews are hard but they get easier with practice 10. The best-paying developer skill is passing technical interviews 11. Be ready to fail, a lot (winners find a way to win, losers find a way to lose) 12. Learn debugging 13. To be a senior, learn how to deliver 14. AI won't replace developers, so keep on getting better 15. Be kind to junior developers 16. Algorithms and data structures are overrated 17. Work smarter not harder 18. Take care of yourself 19. Think long-term 20. Ignore tech twitter 21. The only job security you have is your employability 22. The fastest way to get a big increase in salary is by switching jobs 23. The easiest way to earn extra money without working harder is to ask for a raise 24. Don't threaten your boss 25. Technical books are overrated 26. Don't be afraid of hard-work (don't do shortcuts) 27. Prioritize quality over quantity 28. Optimize for earning, not for learning 29. Blogs are overrated 30. Surround yourself by people you admire
I think the advises are pretty good for junior and mid (semi-senior) developers, but to be a "good senior" or, even worst, to try to be a 2% top developer/engineer, you NEED to do the "overrated" part. Algorithms, data structures, and technical books, are the difference between the 10x developers and the normal developers (be it jr, ssr or sr). I would argue even as a junior developer, you need to have basic understanding of the first two topics, and a basic understanding of CS in general. But no, I don't think you can't become a true senior, or a 10x, without having complete understanding of complex CS topics. At least that's what I've seen in my experience.
Algorithms aren't the goto in day to day coding. Effective patterns are. 80% of your coding will see you using certain things over and over again with subtle variations that stop them from being fully reusable, and thus packageable. Also, spelling and readability are essential for long-term code support. You can write anything in the heat of the moment, but you should always take a moment to ask if future-you is going to be mad at current-you for writing that. Also, to be a good programmer, remember that coding isn't done for computers so much as for humans. If we coded for computers we'd need 16kb RAM and write everything in assembly. We code for humans to read and understand. Developing low-level coding skills is important early on, but it will only take your career to the 2 or 3 year mark. Coding well while being an effective teammate who can also operate independently? You're in pretty good shape if you can pull off that balance.
🔍 Find your technical gaps with this Free Technical Assessment: www.theseniordev.com/free-technical-assessment
8. "You get motivated by getting things done, not by watching motivational videos". Word!
🚀
13. is gold! Thinking in MVP is a golden skill.
16. Algos and DS are needed. They are not the goal, but you should know what they are so you dont reinvent the wheel.
25. Tech books are not overrated, if you don't educate yourself you will not work smarter. Also look at point 16 :D
The rest is awesome! Thanks for the list, coming from an almost 10 year engineer
Glad you enjoyed it @darth1anyan!
This mania to discredit proper education in the basis of CS only creates issues and gaps in the knowledge that are really detrimental to growing in the carrer.
I am a certified professional Java programmer, pretty high level coder. But primarily, a backend developer. I just recently started working with AWS, and a few days ago started learning JS and Node.js. And due to my previous experience with Java programming language, and most of the OOP concepts i picked up with just perfecting myself in one programming language, i am able to accelerate my learning of JS, where basically in a few days i can start building web applications and some serious projects using this language and its technologies. With GPT now, i can learn these things like 50x faster than before. The most important thing is to learn and perfect programming in general and application development, learning and addapting to a new technology becomes a non issue.
Algorithms, like money, don't matter when you got 'em, because whether you realize it or not, it's all algorithms in software. Algorithms and data structures pretty much, yeah.
The best way to "got 'em" is not to learn them, but to try and understand them: what basic steps they're built out of, why those steps are the best way to achieve your goal and how they apply to structures you work with. It's actually kinda fun, too. Well, like learning in general.
1. How do you develop transferable skills unless you’re actually building experience in lots of different libs, frameworks, languages, etc, and transferring your skills? Instead, become an expert of the common patterns used across frameworks, languages, libs, etc. Use more things, try more things, not less. 2. lol what are the fundamentals? Again, I think it’s the common patterns that are important. Should probably elaborate on that now but it’s a CZcams comment so I won’t.
thank you for this, we will add these points to our next videos. Particularly "what are the fundamentals" question which a lot of devs struggle with, thanks again!
Love your videos, Thankyou for posting this
You are welcome! Glad you enjoyed it :)
Excellent advice!! This video should have a millions views. I think everyone needs to see this in this job market.
thank you so much :)
1. Stick to one framework
2. Focus on the fundamentals
3. Believe in yourself
4. Always negotiate your salary
5. Ignore nasty people
6. Don't take anything personally
7. Confidence comes from competence, but it also comes from clarity (know what you don't know)
8. You get motivated by getting this done, not by watching motivatonal videos
9. Technical interviews are hard but they get easier with practice
10. The best-paying developer skill is passing technical interviews
11. Be ready to fail, a lot (winners find a way to win, losers find a way to lose)
12. Learn debugging
13. To be a senior, learn how to deliver
14. AI won't replace developers, so keep on getting better
15. Be kind to junior developers
16. Algorithms and data structures are overrated
17. Work smarter not harder
18. Take care of yourself
19. Think long-term
20. Ignore tech twitter
21. The only job security you have is your employability
22. The fastest way to get a big increase in salary is by switching jobs
23. The easiest way to earn extra money without working harder is to ask for a raise
24. Don't threaten your boss
25. Technical books are overrated
26. Don't be afraid of hard-work (don't do shortcuts)
27. Prioritize quality over quantity
28. Optimize for earning, not for learning
29. Blogs are overrated
30. Surround yourself by people you admire
I think the advises are pretty good for junior and mid (semi-senior) developers, but to be a "good senior" or, even worst, to try to be a 2% top developer/engineer, you NEED to do the "overrated" part. Algorithms, data structures, and technical books, are the difference between the 10x developers and the normal developers (be it jr, ssr or sr). I would argue even as a junior developer, you need to have basic understanding of the first two topics, and a basic understanding of CS in general. But no, I don't think you can't become a true senior, or a 10x, without having complete understanding of complex CS topics. At least that's what I've seen in my experience.
Algorithms aren't the goto in day to day coding. Effective patterns are. 80% of your coding will see you using certain things over and over again with subtle variations that stop them from being fully reusable, and thus packageable.
Also, spelling and readability are essential for long-term code support. You can write anything in the heat of the moment, but you should always take a moment to ask if future-you is going to be mad at current-you for writing that.
Also, to be a good programmer, remember that coding isn't done for computers so much as for humans. If we coded for computers we'd need 16kb RAM and write everything in assembly. We code for humans to read and understand. Developing low-level coding skills is important early on, but it will only take your career to the 2 or 3 year mark. Coding well while being an effective teammate who can also operate independently? You're in pretty good shape if you can pull off that balance.
Thank you!
You're welcome! :)
Thank you so much. You got a new subscriber
Welcome to the channel @peacemelodi1145! You are welcome :)
Thank you Dragos.
You are welcome!
Very very good advice. Practical philosophy.
Thanks :)
No bs, best advice !!
Glad you enjoyed it @leularia
This is good advice!
🚀
Great advice!
Glad you enjoyed it @10Rmorais
“Tech books 📕 are overrated”, 2seconds later “check out my top 10 tech books”
I died 😂😂😂 that’s hilarious 🤣
lol, heheh, yes, most of them are indeed overrated, some are true gems :)
Thank you sir.
You are welcome Michal
Subscribed ❤
Welcome to the channel @richclueking
Get good at solving hard problems not by talking about them. Key word "PROBLEMS" it's easy to get lost otherwise
31. Ignore quitters.