I Feel Bad For New Programmers
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
"I suck" -ThePrimeagen
The PrimeTime
55.8k views
The Evolution of Programming | The Standup
ThePrimeTime
93.3k views
Programming From Prison
ThePrimeTime
66.2k views
Progressive JSON
ThePrimeTime
239.5k views
Be A Great Programmer
ThePrimeTime
220.0k views
The Best Programmers I Know - Prime Reacts
ThePrimeTime
234.4k views
The End Of Programming As We Know It
ThePrimeTime
447.2k views
AI Is Making You An Illiterate Programmer
ThePrimeTime
480.8k views
Maybe HTMX Is Bad...
ThePrimeTime
161.7k views
i created my own protocol for my games...
ThePrimeTime
70.7k views
Top Comments (10)
I have a different take on this. I am a seasoned programmer who has been in the industry for over 30 years now. I have a background in electrical engineering and that pretty much gave me an edge when I was starting out. I had an in-depth understanding of how computers worked from the basic circuitry. There are so many layers of abstraction even in those circuits and trying to understand all of them won't get you anywhere. The software industry is moving fast and companies are looking for engineers who are familiar with their stack. So I see no harm starting out at a higher layer of abstraction and moving on to lower layers when you get a job or after you get relevant industry experience. In the end people need to get by and it's okay if you want to start from a higher layer. Your value as an engineer is not measured by how much you know, but how you use what you know and what is available to solve existing problems. That's my opinion.
As a new programmer, learning higher level stuff is kind of like watching family guy without knowing references. You kinda get it because the jokes work on their own so you just move on without much thought. Then when you learn about the references (or tools) you look back at the episode and you’re like “omg I understand everything now!”
This is why I feel bad for people trying to change careers at React bootcamps.
The bad thing is that after learning all these things, we don't become good at programming; we just become good at using those abstracted tools. We don't know how these things work internally, and the moment these abstracted tools become obsolete, we're thrown back to step one
dude my university doesn't even teach how MEMORY works, none of my peers know what assembly is, the lowest level language we're being taught is JAVA
I personally prefer the bottom-up way of learning since your knowledge never depends on things you don't know yet and the bigger picture usually just clicks immediately.
The discipline required to peel back the abstraction layers is pretty overwhelming these days.
2 pieces of news for programmers who are just starting out: 1. It's hard, and most of you probably will quit after a few punches you'll inevitably receive. 2. If you can manage the stress and take those punches without throwing your laptop out of the window and staying diligent, you'll have a high chance of becoming a professional in this field.
This is why it took me so long to learn basic JavaScript. Because JavaScript used to be "simple" language to manipulate your website, but then it turned into, "We also want OOP, we also want array methods, we also want X, Y, Z" And now there are 50 ways of doing the same thing instead of just one or two. As a beginner that's super overwhelming since programming itself is already quite confusing for a total beginner. This is why modern JS is just a bad way to learn programming IMHO.
self taught web dev here in this day and age, there's no wrong answer in picking your stack. Every framework and new technology is copying features from each other, not to mention open source contributions. So any way you take will get the job done, accordingly pick whatever you're comfortable with
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
I have a different take on this. I am a seasoned programmer who has been in the industry for over 30 years now. I have a background in electrical engineering and that pretty much gave me an edge when I was starting out. I had an in-depth understanding of how computers worked from the basic circuitry. There are so many layers of abstraction even in those circuits and trying to understand all of them won't get you anywhere. The software industry is moving fast and companies are looking for engineers who are familiar with their stack. So I see no harm starting out at a higher layer of abstraction and moving on to lower layers when you get a job or after you get relevant industry experience. In the end people need to get by and it's okay if you want to start from a higher layer. Your value as an engineer is not measured by how much you know, but how you use what you know and what is available to solve existing problems. That's my opinion.
As a new programmer, learning higher level stuff is kind of like watching family guy without knowing references. You kinda get it because the jokes work on their own so you just move on without much thought. Then when you learn about the references (or tools) you look back at the episode and you’re like “omg I understand everything now!”
This is why I feel bad for people trying to change careers at React bootcamps.
The bad thing is that after learning all these things, we don't become good at programming; we just become good at using those abstracted tools. We don't know how these things work internally, and the moment these abstracted tools become obsolete, we're thrown back to step one
dude my university doesn't even teach how MEMORY works, none of my peers know what assembly is, the lowest level language we're being taught is JAVA
I personally prefer the bottom-up way of learning since your knowledge never depends on things you don't know yet and the bigger picture usually just clicks immediately.
The discipline required to peel back the abstraction layers is pretty overwhelming these days.
2 pieces of news for programmers who are just starting out: 1. It's hard, and most of you probably will quit after a few punches you'll inevitably receive. 2. If you can manage the stress and take those punches without throwing your laptop out of the window and staying diligent, you'll have a high chance of becoming a professional in this field.
This is why it took me so long to learn basic JavaScript. Because JavaScript used to be "simple" language to manipulate your website, but then it turned into, "We also want OOP, we also want array methods, we also want X, Y, Z" And now there are 50 ways of doing the same thing instead of just one or two. As a beginner that's super overwhelming since programming itself is already quite confusing for a total beginner. This is why modern JS is just a bad way to learn programming IMHO.
self taught web dev here in this day and age, there's no wrong answer in picking your stack. Every framework and new technology is copying features from each other, not to mention open source contributions. So any way you take will get the job done, accordingly pick whatever you're comfortable with