"New Junior Developers Can't Actually Code"
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
How does Claude Code *actually* work?
Theo - t3․gg
189.3k views
Claude Code - Full Tutorial for Beginners
Tech With Tim
56.5k views
Learning to code has changed
Tech With Tim
174.5k views
Vibe Coding is For Senior Developers
Theo - t3․gg
109.1k views
Lovable vs MeDo, which AI app builder actually works?
Tech With Tim
87.9k views
Data Structures - Full Course for Beginners
Tech With Tim
45.8k views
How to Write Production Python Code
Tech With Tim
63.1k views
The Best AI Coding Tools for Developers in 2025 (That I Actually Use)
Tech With Tim
168.4k views
How To Become a Full Stack Developer in 2025 - Full Roadmap
Tech With Tim
61.1k views
Coding is NOT Enough in 2025...
Tech With Tim
24.5k views
Top Comments (10)
Check out ManageEngine Site24x7 today and get 6 months for FREE to evaluate the platform! https://https://www.site24x7.com/promo-signup.html?pack=1001&utm_source=TECHWITHTIM-1&utm_medium=Youtube&utm_campaign=YoutubeInfluencer
Good luck to all junior/new devs out there they definitely need it!
I use AI as a teacher I write the code myself and then ask AI to optimize and explain it. That helps me a lot. I've improved significantly; I now write cleaner and more readable code, and my logic has improved as well, especially in avoiding redundancy as a good developer don't copy you don't understand ~
Agree 100%. AI will try to find a solution, but it may not be the best solution. Often LLMs solve problems at the expense of space complexity & scalability. If you're not aware of the concepts, and can't read the code well enough to understand what's going on, then you'll "make" a program and wonder why it's so slow, resulting in more work for yourself in the (near) future.
The debate about the use and misuse of AI is a very popular topic. In my opinion, I once heard my favorite professor say something that really stuck with me: "If you know exactly how the code is produced—like if you're building a calculator app—you already understand the operations and logic behind it. In that case, using AI to help generate the code is fine, because it boosts your productivity without sacrificing your understanding. But in a different scenario, like building a networking system, if you rely on AI without knowing how it works, you risk losing the opportunity to actually learn and grow."
This is such a thoughtful and well-balanced take. The debate over outsourcing our thinking has been raging at least since the introduction of calculators. In a similar vain, using calculators doesn’t necessarily make us worse mathematicians, because the hard part of math isn’t doing arithmetic. It’s reasoning through a problem and breaking it down into logical steps, as well as analyzing and testing your assumptions.
When you build with frameworks like React, Angular (yes, some people still use it), or any other, you can get pretty far without deep JavaScript knowledge. But as your app grows in complexity, and you start caring about performance or advanced features, solid JavaScript skills become essential. Abstractions are powerful! They help you move fast and build things easily. But eventually, you’ll hit a wall where the details start to matter. AI has taken abstraction to a whole new level, but even that has limits. Abstraction is great for using systems, but if you want to extend them or go beyond what’s provided out of the box, you need to understand what’s under the hood. Even today, Assembly remains a valuable skill. It's not required for most developers, but if you know it, it's like having a superpower. It gives you a deeper understanding of how computers work and lets you push boundaries that others can't.
When I started Python, I was using GPT for help, but then I realized it was making me weak. When it's time to really study, I actually write out the flow and code by hand. From doing that, I became able to spot bugs and help other people with their code.
My professor lost his shit when I started using a calculator for doing integrals back in the day (70s). He was convinced calculations done with a computer would contain errors 😂. Made up "problems". If you don't know what you're doing you won't get far. And if you do, that's on who hired you. Ignore the rest
I will say something the beauty of solving problem is getting the dopamine as a reward i don't want to skip this lovely headache ❤
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)
Check out ManageEngine Site24x7 today and get 6 months for FREE to evaluate the platform! https://https://www.site24x7.com/promo-signup.html?pack=1001&utm_source=TECHWITHTIM-1&utm_medium=Youtube&utm_campaign=YoutubeInfluencer
Good luck to all junior/new devs out there they definitely need it!
I use AI as a teacher I write the code myself and then ask AI to optimize and explain it. That helps me a lot. I've improved significantly; I now write cleaner and more readable code, and my logic has improved as well, especially in avoiding redundancy as a good developer don't copy you don't understand ~
Agree 100%. AI will try to find a solution, but it may not be the best solution. Often LLMs solve problems at the expense of space complexity & scalability. If you're not aware of the concepts, and can't read the code well enough to understand what's going on, then you'll "make" a program and wonder why it's so slow, resulting in more work for yourself in the (near) future.
The debate about the use and misuse of AI is a very popular topic. In my opinion, I once heard my favorite professor say something that really stuck with me: "If you know exactly how the code is produced—like if you're building a calculator app—you already understand the operations and logic behind it. In that case, using AI to help generate the code is fine, because it boosts your productivity without sacrificing your understanding. But in a different scenario, like building a networking system, if you rely on AI without knowing how it works, you risk losing the opportunity to actually learn and grow."
This is such a thoughtful and well-balanced take. The debate over outsourcing our thinking has been raging at least since the introduction of calculators. In a similar vain, using calculators doesn’t necessarily make us worse mathematicians, because the hard part of math isn’t doing arithmetic. It’s reasoning through a problem and breaking it down into logical steps, as well as analyzing and testing your assumptions.
When you build with frameworks like React, Angular (yes, some people still use it), or any other, you can get pretty far without deep JavaScript knowledge. But as your app grows in complexity, and you start caring about performance or advanced features, solid JavaScript skills become essential. Abstractions are powerful! They help you move fast and build things easily. But eventually, you’ll hit a wall where the details start to matter. AI has taken abstraction to a whole new level, but even that has limits. Abstraction is great for using systems, but if you want to extend them or go beyond what’s provided out of the box, you need to understand what’s under the hood. Even today, Assembly remains a valuable skill. It's not required for most developers, but if you know it, it's like having a superpower. It gives you a deeper understanding of how computers work and lets you push boundaries that others can't.
When I started Python, I was using GPT for help, but then I realized it was making me weak. When it's time to really study, I actually write out the flow and code by hand. From doing that, I became able to spot bugs and help other people with their code.
My professor lost his shit when I started using a calculator for doing integrals back in the day (70s). He was convinced calculations done with a computer would contain errors 😂. Made up "problems". If you don't know what you're doing you won't get far. And if you do, that's on who hired you. Ignore the rest
I will say something the beauty of solving problem is getting the dopamine as a reward i don't want to skip this lovely headache ❤