I'm 60 years old. Claude Code killed a passion
171–180 of 206 posts
Re: I'm 60 years old. Claude Code killed a passion
#172We start to understand those old fogeys who we blew past we were young once we get to their age. It's the way of the world.
Re: I'm 60 years old. Claude Code killed a passion
#173Re: I'm 60 years old. Claude Code killed a passion
#17414 years ago hearing Dan Pink talk on motivation ( https://youtu.be/u6XAPnuFjJc ) catalyzed the decision to change jobs. One of the three motivators he mentions is mastery. And cites examples of why people waste hours with no pay learning to play instruments and other hobbies in their discretionary time. This has been very true for me as a coder. That said, I enjoy the pursuit of mastery as a programmer less than I u…
Re: I'm 60 years old. Claude Code killed a passion
#175Re: I'm 60 years old. Claude Code killed a passion
#176AI poses many challenges from security to ensuring code safety. When paired and met with the same expectations before the hype, you could consider it good enough to shave off 8 hours of work. But this is just the first 8 hours of getting some code ready.
A savvy dev could easily just grab an existing template they made prior and stitch things together in a degree better than AI.
Now it is just massage the prompt and hope it adheres.
Re: I'm 60 years old. Claude Code killed a passion
#177Earlier quoted context omitted.
>AI has just exposed that many "engineers" are "temporarily embarrassed project managers", which is fine in the sense that it makes it clearer who actually enjoys making things and who just wants the end result regardless of how it's made. AI has also exposed that many "engineers" are just "people who like fiddling with code" and that's fine in the sense that it makes it clear who are the actual engineers who are eng…
> Like imagine slandering a civil engineer "you just want a bridge that is safe and lasts for a century, you don't care about enjoying the journey of construction". Would you currently trust a bridge designed by a civil engineer using AI for all of their calculations ?
Of course. I've seen how sloppy and lazy humans are, and I already use the bridge, and if the safety truly came down to the output of single person, then the risk is already significant.
I must say, I got a chuckle at "using AI to do their calculations". Oh no, my agent is going to write a python script to do basic maths, and check their work against a series of automated tests, the sky is falling!
Re: I'm 60 years old. Claude Code killed a passion
#178Earlier quoted context omitted.
>AI has just exposed that many "engineers" are "temporarily embarrassed project managers", which is fine in the sense that it makes it clearer who actually enjoys making things and who just wants the end result regardless of how it's made. AI has also exposed that many "engineers" are just "people who like fiddling with code" and that's fine in the sense that it makes it clear who are the actual engineers who are eng…
Haha! Your analogy doesn't work on multiple levels. Firstly, if you're outsourcing your work to AI you're not the engineer anymore. A civil engineer is different from a manager of a civil engineering project. Just like I wouldn't call myself an artist if I got AI to generate me some art, I wouldn't call myself a software engineer if I got AI to write all the code for me. Secondly, it's not just about "enjoying the jo…
- Outsourcing
False. If you "outsource your code" to a compiler and just write higher level language, you're not an engineer. You literally don't own any of your own code, just an abstraction of it written in human language. See how that works? An engineer can delegate -- period.
- "I wouldn't call myself a software engineer if I got AI to write all the code for me"
If all you do is write code you're not an engineer. I think you fundamentally don't know what engineering is. In a very real sense engineering is what you do when you're not coding. The civil engineer doesn't construct the bridge personally.
- "Secondly, it's not just about "enjoying the journey of construction", it's also about caring about the quality of the end results".
Codemonkeys DON'T CARE about the quality of the end result. They only care about their little corner of the zen garden. Writing real software for real users is by far the worst part of a codemonkeys job.
- "Getting vibe coded software that is as stable as a "bridge that is safe and lasts for a century" is not a matter of careful engineering decisions, it's mostly a matter of luck"
Nonsense. The engineer who spends 90% of his time architecting systems and testing them at a high level is making safer and more stable software than the codemonkey who spends 90% of his time tinkering with the details. Forest for the trees.
- "unless you're doing extensive reviews of the generated code, at which point you greatly diminish the time you're supposedly saving."
Who said anything about "saving time"? We're engineering high quality systems. Some of us spend our time at a higher level, thinking holistically about the system, testing multiple concepts and rapidly iterating. Others demand bespoke handwritten code and in the time allowed can barely finish a single concept with a questionable amount of polish. Whatever their first idea is will ship, and they'll have no real ability to justify the architecture other than vibes.
Re: I'm 60 years old. Claude Code killed a passion
#179Enjoyers of journey vs Enjoyers of journey destination! you gave me something to think about.