The remaining friction is fundamentally the same as that which existed when writing code manually. The gap between what you envision for your design/solution and the tools for implementing that vision. With code, the friction encountered when implementing your vision is substantial; with AI, that friction is significantly reduced, and what's left is in areas different from what past experience would lead you to expect.
I'm 60 years old. Claude Code killed a passion
131–140 of 206 posts
Re: I'm 60 years old. Claude Code killed a passion
#132I feel you. For me it was a love of problem solving. Now that’s been taken away from me and people keep telling me how happy I should be about it.
The world still has problems to solve?
Re: I'm 60 years old. Claude Code killed a passion
#133Earlier quoted context omitted.
> Your company isn’t paying you to solve puzzles. If you aren’t putting things into production, what good are you as an employee? No, the company is exactly paying their employees to solve puzzles, which company labels them as problems or requirements. And when an employee focuses on solving puzzles and enjoys it, the code naturally ends up in production, and gets forgotten because the puzzle is solved well.
And if they could solve the problem faster with AI? But there is no “puzzle” to solving most enterprise problems as far as code - just grind. And code doesn’t magically go from dev to production without a lot of work and coordination in between.
It's such a shame that everyone only cares about "faster" and not "better"
What a shameful mentality. Absolutely zero respect for quality or craftsmanship, only speed
Re: I'm 60 years old. Claude Code killed a passion
#134Earlier quoted context omitted.
If I wanted to become a project manager I would have become one. 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 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…
Would you currently trust a bridge designed by a civil engineer using AI for all of their calculations ?
Re: I'm 60 years old. Claude Code killed a passion
#135Earlier quoted context omitted.
And if they could solve the problem faster with AI? But there is no “puzzle” to solving most enterprise problems as far as code - just grind. And code doesn’t magically go from dev to production without a lot of work and coordination in between.
> And if they could solve the problem faster with AI It's such a shame that everyone only cares about "faster" and not "better" What a shameful mentality. Absolutely zero respect for quality or craftsmanship, only speed
My employer just like any other employer cares about keeping up with the competition and maximizing profit.
Customers don’t care about the “craftsmanship” of your code - aside from maybe the UI. But if you are a B2B company where the user is not the customer, they probably don’t even care about that.
I bet you most developers here are using the same set of Electron apps.
Re: I'm 60 years old. Claude Code killed a passion
#136Earlier quoted context omitted.
I hope the companies you worked for had someone else taking care of security, as what you've described is a ransomware writer's wet dream.
You have a gateway / platform for that. You aren’t exposing those services to the internet.
You aren’t knowingly exposing those services to the internet.
FTFY. Furthermore, internal services can still be abused to get data that shouldn't be shared. For example, imagine if your imaginary API was for a HR system, and could be used to determine salary information for staff.
If you aren't considering API security, you're almost bound to make major mistakes, and I'd bet money that most APIs designed and implemented in 2 days have tons of security holes.
Re: I'm 60 years old. Claude Code killed a passion
#137Re: I'm 60 years old. Claude Code killed a passion
#138> it depends on what you enjoy: the journey or the destination This has been 100% my experience. I enjoy the puzzle solving and the general joy of organizing and pulling things together. I could really care less about the end result to meet some business need. The fun part is in the building, it's in the understanding, the growth of me . I have coworkers who get itchy when they don't see their work on production, and…
I agree with this sentiment as well. Without a doubt, my favorite part of the job is coming up with a solution that just 'feels right', especially when said solution is much cleaner than brute force/naive approach. It sounds cheesy, but it truly is one of my favorite sensations.
I'm the senior-most engineer on my team of about 15. I try to emphasize software craftsmanship, which resonates with some but not all. We have a few engineers who have seemingly become reliant on AI tooling, and I struggle with them. Some of them are trying to push code that they clearly don't understand and aren't reviewing, and I think they're setting themselves up for failure due to lack of growth.
Re: I'm 60 years old. Claude Code killed a passion
#139Earlier quoted context omitted.
> And if they could solve the problem faster with AI It's such a shame that everyone only cares about "faster" and not "better" What a shameful mentality. Absolutely zero respect for quality or craftsmanship, only speed
I care about exchanging labor for money to support my addiction to food and shelter. My employer just like any other employer cares about keeping up with the competition and maximizing profit. Customers don’t care about the “craftsmanship” of your code - aside from maybe the UI. But if you are a B2B company where the user is not the customer, they probably don’t even care about that. I bet you most developers here ar…
Just because things are this way doesn't mean they should be or that we should just accept that they must always be this way
Re: I'm 60 years old. Claude Code killed a passion
#140I've always done networking (isp, datacenter, large enterprise), security (networking plus firewall, vpn, endpoint), unix/linux admin, even windoze stuff with active directory, but never any development or programming directly. I was just never wired for it, though I can do ip/cidr/bgp/acl stuff in my head for days. I missed out on higher ed entirely after high school, and I learned along the way what I did after 45 years of tinkering with pc's from apple II on i life.
Right now I'm taking my network and security knowledge in writing an mcp to do network and security tasks enabling agents like claude-code, claude-desktop, codex, openclaw a means of accessing resources indirectly via my mcp, and it's something I could have never done before the advent of AI as I "don't do code". Now I can tell it intimately everything I need/want it to do, and it just literally does it. It's extremely effective too, if not at times aggravating/infuriating.
My biggest gripe is it does everything half ass, but nothing I haven't seen time and again from outsourcing. It feels like the usual contractor slop you might get hiring wipro/infosys or any other offshore development effort, but at least without human idiocy.
AI in general really needs a "don't do half-ass work" option, as it typically feels like I'll get "good enough for government work" sort of results until I kick and slap it at least twice to fix its shortcomings. It invariably feels like it always only gives me half of what I ask for. You can almost tell it's built to not give you everything up front, instead make you work for it.
It's a trap, as a wise man once said.