Claude Code does empower developers to do deep higher level work. It's easier to generate advanced changes now.
E.g. database optimisations a Senior Engineer might do, such as designing a database partition or creating a complex composite index. The problem? When Claude recommends more advanced solutions without a deep understanding it is easy to miss where the foot guns lie or if Claude got it outright wrong.
It's like being handed a chainsaw when you had an axe. Without good judgement, it's easy to cut down the wrong trees.
You are right, but the responsibility of the final artifact must fall on the human.
Think about what we did before if we didn't have another human around to ask and think together about a problem.
We searched for solutions or more info on Stack Overflow, Reddit , random blogs or HN even. The we tried to evaluate the pros and cons of each possible solution and then decide what to do.
Now we should use the LLM to get that info from the internet (be it from its lossy memorized or better fresh from its search tool). Then try to ask the LLM for pros and cons and follow the links it provided if you don't trust its "judgement".
That assumes the problem is a common one others have encountered, which the examples I gave above certainly were. When you're wrangling with poorly documented legacy code operating under the context of its own internal domain logic (e.g. arcane country specific banking regulations), often the only source of good "judgement" (that's the commonwealth spelling btw) are those in the past who wrote the code the way they did.
This is an area where Claude Code is both valuable and dangerous. It can propose sweeping (correct) changes based on inconsistencies it finds within the codebase. The developer, in situations where nobody more senior is around to answer those design questions, is left making a judgement call based on vibes and what logic they can piece together about Claude's changes.
I can't think of anything scarier than a military planner making life or death decisions with a non-empathetic sycophantic AI. "You're absolutely right!"
All of those are true, yet the US's (PPP-adjusted) per capita GDP was over 37% higher than the EU's in 2024 [0], and GDP growth has significantly outpaced the EU for years. Basically, whenever there was a choice between anything and economic growth, the US chose growth. Other places made different choices. You can argue about which choices were better, and how the results are distributed, but the difference in salaries for most people using this site are even more stark.
Counter to your point, what's most striking from that chart is how comparably similar both Europe and the United States are in their GDP per capita growth.
As AI tooling improves, tech workers are finding their opportunities for high-paying prosperity fizzle out. Non-AI tech jobs are going the way of the rust belt and most tech professionals have seen their pay flatten. https://www.itbrew.com/stories/2024/02/05/tech-salaries-stag...
If I work for a megacorp and they sell more widgets while paying me the same amount then GDP goes up. This is not actually a direct measure of human flourishing.
But they can't sell more widgets if nobody has any money to buy them.
Sure, you could model a pretend economy where only the wealthy ever buy stuff, but that's not how the US economy works, and Consumer Confidence has a massive influence over our GDP - so when our GDP goes up, it's often hand in hand with our population buying more widgets with extra money, even as they complain that they don't have the cash for "necessities" (I.E. burrito taxis, vanity pickup trucks, and owning a house with two spare bedrooms with a <30 minute commute to their workplace).
Note: I'm not saying that low-income Americans don't genuinely struggle, just that there's a mismatch between the Americans that are genuinely low-income and the Americans that perceive themselves as low-income because they need to save a little to make major purchases or need to tell themselves no sometimes.
> All of those are true, yet the US's (PPP-adjusted) per capita GDP was over 37% higher than the EU's in 2024 [0], and GDP growth has significantly outpaced the EU for years.
And? So what? What has that gotten the US?
Lower life expectancy, higher infant/maternal mortality, higher (violent) crime, and generally much less happiness with life:
Most of their numbers were about the quality of life. It's absolutely absurd to say,
> Well you're twice as likely to be killed, more likely to be sick and obese, will die earlier, are more likely to be in poverty under a tech baron, have a poisoned ecosystem, your babies or wife may die or your kids die in school, or they'll go in insane debt to go to their higher education, and if you're not a white man you're basically less human and risk becoming a part of the permanent ~~slave~~ criminal caste... But think of the moderately higher salary potential!!!!
>
> You know, as long as the economy grows forever and nobody calls any of your debts.
High GDP per capita does not immediately mean that people are rich. As one other commenter noted, Ireland has a very high GDP per capita, but your average Irish person is not living rich
So we chose growth, and now are trying empire, because of memes about our supposed strength on paper, pushed by unserious “conservatives” who can’t form a cohesive argument about anything?
We stand a good chance of this totally destroying us, because the “technocracy” set actually believe their own Paper Divisions are unstoppable and the legal mind of “stick your fingers in your ears and say NAH NAH NAH” to be unassailable.
What an embarrassing ending to the American story this all is, eh?
Maybe whatever comes next will be more serious and will choose differently.
Disturbance storm time index (DST) is a better measure of peak intensity as KP is just a weighted average of the intensity from the last three hours across monitoring stations.
I've heard about technology like this for over a decade. Have never encountered a use case (even no coverage at music festivals) where it once became viable.
E.g. database optimisations a Senior Engineer might do, such as designing a database partition or creating a complex composite index. The problem? When Claude recommends more advanced solutions without a deep understanding it is easy to miss where the foot guns lie or if Claude got it outright wrong.
It's like being handed a chainsaw when you had an axe. Without good judgement, it's easy to cut down the wrong trees.
reply