👉Get 40% OFF for 3 months of Coursera ➡️ https://imp.i384100.net/c/6306369/3808548/14726

👉Get 40% OFF CodeCrafters: https://app.codecrafters.io/join?via=codehead-01
👉Git gud at coding for FREE with Scrimba  https://scrimba.com/courses:free?via=codehead  (and save 20% on Pro plans with my link).
👉ACE your next technical interview with 50% OFF AlgoMonster: https://algo.monster/codehead
👉I made a Discord server for all of you code heads to join: https://discord.gg/MfCKFK2fTe
👉Buy this tired Code Head a ☕: https://buymeacoffee.com/codehead

🎶beats:  @massobeats  
honeyjam: https://www.youtube.com/watch?v=XC9yPcYAYhE&list=RDEMl_yAA40g1NBRjgxECyPLSw&start_radio=1

#programming #fullstack #developer

CodeHead

A reflective piece questioning whether developers should keep coding amid AI disruption and tech layoffs. It argues that many so-called AI layoffs are actually cover for pandemic-era overhiring mistakes, and that vibe coding has a real understanding gap — non-technical users can't debug what they don't understand. The piece emphasizes that coding teaches problem-solving and structured thinking that remains valuable regardless of market shifts. Ends with a sponsored recommendation for Coursera courses in Python, Unix, and software architecture.

Should You... Keep Coding?

OF COURSE.
IMO, I think the collective industry hangover is starting to set in. AI coding has exacerbated the worst parts of coding and development, by accelerating the parts that didn’t need accelerating in the first place.
We didn’t need to write code faster, nor did we need to generate code we didn’t fully understand.
If you like to code manually: keep it up! Real understanding comes from friction, and friction comes from problem solving. If you cut out the problem solving, whatever you think you know is superficial.
Also keep in mind: everything fails at some point, nothing is infallible, especially non-deterministic pattern interpolators like LLMs. Everything works, until it doesn’t. When it doesn’t, who debugs the debugger? I’ve started <a href="http://confident-coding.com" target="_blank" rel="noopener nofollow">confident-coding.com</a> to address this, because I think we’re going to need to constantly remind, educate and guide people on what it means to think carefully, think critically, and know how to find the rope that can pull you back above the surface when you’re drowning in the error codes.

Never would I ever think about Omni man and coding

“You don’t need to code anymore”
Cool, so who’s debugging the hallucinated edge cases at 2am?

Yes, we should. Even with AI assistance how do you even expect for formulate good, meaningful prompts that express clearly your intent when you don’t know how to structure problems, so they can be written with code. Writing code is 20-25% of the job.
Without good understanding of what’s going on underneath, you’ll waste time and tokens trying to get things to work. The bigger the solution, the harder it gets, regardless of using AI or not. Knowing the craft by hand allows you to not only create more meaningful prompts, but also “get down and dirty”, when AI won’t cut it.

“Don’t quit, but do evolve.”