

As someone somewhere between junior and intermediate developer, I will say vibe coding on my personal projects has accelerated my learning so much on the proper way to code things so much more than constantly bugging my seniors who don’t have time to properly review and critique my code (because surprise surprise! We’re understaffed). At least now I can ask Claude to explain its approach and fact check it myself, and the times I’ve had it run too loose, I’ve gotten practice debugging code I’m unfamiliar with since Claude eventually hits a point where it fucked something up and has no idea how to fix it. But obviously the caveat is you have to approach it as a learning tool not an automation tool.


A lot of these engineers get stuck in sisyphian goals where if they just work a little bit harder for a little bit longer they’ll get the boulder over the hill and finally “make it.” It’s not about the money; it’s the promise of early retirement and justifying the sacrifices they’ve made to get to this point in their careers. But yeah, part of the sacrifice is their morals.