Like a carpenter won't get more money for their cabinets if they make them all painstakingly by hand, not using a single power tool. (OK, some do but it's more of an art piece than a functional thing).
Like a carpenter won't get more money for their cabinets if they make them all painstakingly by hand, not using a single power tool. (OK, some do but it's more of an art piece than a functional thing).
I think that's the difference though. I commented on a similar topic earlier, but I think the issue is that people are using these tools for both the coding AND the problem solving. They've turned over both ends of the workflow to the bots. When you ask them "Why did you add these new libraries to our project to solve this?" you get "I dunno, Claude did it". When you ask "Why did you avoid using our entire DI system for these static vars?" they respond "I dunno, Claude did it. But the tests pass!".
If you still tackle the problem solving part, that's great. Thank goodness. But I wouldn't assume that's how the rest of the lazy gits are using LLMs as well.
It's like complaining about a chef who make all their food from fresh ingredients instead of buying off-the-shelf processed versions. People will pay more for that freshy made food.