Experts Have It Easy...
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
It's all fake
The PrimeTime
88.9k views
I Watched It
ThePrimeTime
210.0k views
Exposing Brain Rot To AI
ThePrimeTime
139.2k views
We did it?
ThePrimeTime
102.6k views
The Who Cares Era
ThePrimeTime
139.0k views
ThePrimeagen's Arch Experience - Standup #7
ThePrimeTime
154.9k views
JUST USE HTML
ThePrimeTime
327.7k views
Simple Made Easy - Prime Reacts
ThePrimeTime
176.4k views
C Must Die
ThePrimeTime
222.3k views
Top Comments (10)
My first project in Accenture was a Java applet. Under my tutelage it grew to over 1000 classes. Then I left the project and a senior engineer on the project rewrote the thing in 13 classes. That was a beautiful lesson (and a relief that no one would have to maintain that pile of spaghetti!)…
In this field you have to be comfortable with and accept you may not know everything - fail forward, keep learning and iterating always. In order to write 'good' code you probably had to write 'bad' code, it's all apart of the process And most importantly have fun and don't be too hard on yourself
this article was very frustrating to listen to. It feels like the author expects others to be responsable for the author's learning, and is so scared of making mistakes that he would rather nag someone about every minute detail of the code instead of risking the chance that the decsions he took were not the "correct" ones according to the "experts".
This article is describing a symptom of being a "novice", but not the solution. It is true that novices are often oblivious of the tools and techniques to solve their problem, and are often apparently incapable of even recognizing possible solutions, however they are not robbed of their agency. The way you push through that in the short term is that you research and read documentation so that you learn what others have done and what tools and techniques you could avail yourself of and then you force your way through the maze until you gain experience. The way "novice" and "junior" developers stay "novice" and "junior" is when they reach these confused states of not know how to solve the problem, and then sit down and wait for some well-meaning senior to come along and tell them what to do. They then, instead of using that as a general guide and researching it to understand why this is maybe a good approach and the surrounding information on this tool/technique, they plow blindly ahead in the new direction they were pointed out until they once again hit a brick wall. Don't be that guy. You will never improve unless you take the action to learn and improve.
That comment about socializing is so relatable, I used to be quite sociable in high school, I know everyone in my grade and most people in my grade know me, because I've interacted with many circles, first year of college I asked a girl out on orientation day when the first semester hadn't even started. then fast forward 2 semester later I almost dropped out due to quarter life crisis, shut myself up the entire pandemic era and I literally forgot how to start a conversation.
08:31 Look at this man dancing with his mic in a truly passionate way
Right Hand Wall Rule is maze talk for Depth First Search
Counter point to the solitary learning. Even though you learned "alone" by looking for stuff on the internet, that stuff did not appeared out of the ether, someone somewhere wrothe that down and then you found it, another person helped you even though you never met them
The paving slabs on the road to success, are made of 'managed failures' and the border flowers are "oppsie daisies.".
I just realized ThePrimeTime just loves to list all possible outcomes of hypotetical situations he talks. he is such a programmer-minded person that he creates a switch-case of any random conversation.
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)
My first project in Accenture was a Java applet. Under my tutelage it grew to over 1000 classes. Then I left the project and a senior engineer on the project rewrote the thing in 13 classes. That was a beautiful lesson (and a relief that no one would have to maintain that pile of spaghetti!)…
In this field you have to be comfortable with and accept you may not know everything - fail forward, keep learning and iterating always. In order to write 'good' code you probably had to write 'bad' code, it's all apart of the process And most importantly have fun and don't be too hard on yourself
this article was very frustrating to listen to. It feels like the author expects others to be responsable for the author's learning, and is so scared of making mistakes that he would rather nag someone about every minute detail of the code instead of risking the chance that the decsions he took were not the "correct" ones according to the "experts".
This article is describing a symptom of being a "novice", but not the solution. It is true that novices are often oblivious of the tools and techniques to solve their problem, and are often apparently incapable of even recognizing possible solutions, however they are not robbed of their agency. The way you push through that in the short term is that you research and read documentation so that you learn what others have done and what tools and techniques you could avail yourself of and then you force your way through the maze until you gain experience. The way "novice" and "junior" developers stay "novice" and "junior" is when they reach these confused states of not know how to solve the problem, and then sit down and wait for some well-meaning senior to come along and tell them what to do. They then, instead of using that as a general guide and researching it to understand why this is maybe a good approach and the surrounding information on this tool/technique, they plow blindly ahead in the new direction they were pointed out until they once again hit a brick wall. Don't be that guy. You will never improve unless you take the action to learn and improve.
That comment about socializing is so relatable, I used to be quite sociable in high school, I know everyone in my grade and most people in my grade know me, because I've interacted with many circles, first year of college I asked a girl out on orientation day when the first semester hadn't even started. then fast forward 2 semester later I almost dropped out due to quarter life crisis, shut myself up the entire pandemic era and I literally forgot how to start a conversation.
08:31 Look at this man dancing with his mic in a truly passionate way
Right Hand Wall Rule is maze talk for Depth First Search
Counter point to the solitary learning. Even though you learned "alone" by looking for stuff on the internet, that stuff did not appeared out of the ether, someone somewhere wrothe that down and then you found it, another person helped you even though you never met them
The paving slabs on the road to success, are made of 'managed failures' and the border flowers are "oppsie daisies.".
I just realized ThePrimeTime just loves to list all possible outcomes of hypotetical situations he talks. he is such a programmer-minded person that he creates a switch-case of any random conversation.