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 don't think this case has much to do with the mono party system but with the state taking interest to support a local industry at a loss but for future security.
Like for example the French government massively supported its aerospace and nuclear industry, and German government gave massive support to its legacy auto industry and they're not a mono party totalitarian system.
So it can be done even in democracies, but you need visionary leaders to spend money wisely on future industry bets and not just on buying votes from pensioners.
The big issue EU now has compared to the past when it kickstarted its nuclear and aerospace industry, is the massive burden of the welfare state that leaves little money for investments into other ventures, and boomers who are the largest beneficiaries of that welfare state, also account for the majority of the voter base, so the major EU economies France and Germany are stuck in a quagmire where the party who wins the elections is the one who goes more into debt for the welfare state.
It's easy to blame the welfare state but IMO the problem is the general culture of being extremely risk-averse beyond reason. Same reason why big US companies lose the ability to innovate. Europeans just hate doing things the new way even if it's better.
>Is Hungary a paragon of growth and strategic planning?
Kinda, yeah. Foreign investors love doing business with dictators due to guaranteed stability versus the political pendulum swinging every 4 years.
HEnce why more manufacturing is opening in Hungary.
BMW: Opened a new, fully electric vehicle plant in Debrecen in September 2025, with series production of the BMW iX3 starting in late October 2025.
Mercedes-Benz: Announced expansion of its Kecskemét plant to start producing the A-Class model in 2026, further solidifying its presence in Hungary where it already manufactures other models.
BYD: The Chinese EV maker is building its first European production facility in Szeged, with operations set to begin by the end of 2025 or early 2026. The €4 billion plant will initially produce tens of thousands of vehicles annually, focusing on EVs for the European market.
CATL: The world's largest battery manufacturer is constructing a massive plant in Debrecen, expected to start production in early 2026. This supports Hungary's EV ecosystem, supplying batteries to automakers like BMW.
Flex (Flextronics): Inaugurated a new high-tech "NextGen" plant in Zalaegerszeg in November 2025, worth 35 billion HUF (about €90 million). It focuses on electronics and components for the automotive industry, creating 210 jobs in research and production.
> Say what you want about China's monoparty system, but it enables planning that spans decades.
That's not a trait of a monoparty system, or even any totalitarian autocratic system. There are democratic multiparty systems which have plans that spans decades, and autocratic totalitarian regimes that barely put together a coherent multi-year project.
Hmmm, I think we're more likely to face an Idiocracy outcome. We need more Geordi La Forges out there, but we've got a lot of Fritos out here vibe coding the next Carl's Jr. locating app instead
we would be lucky to have idiocracy. president camacho had a huge problem and he found the smartest person in the country and got him working on it. if only we can do that
Star Trek illustrated the issue nicely in the scene where Scotty, who we should remember is an engineer, tries to talk to a computer mouse in the 20th century: https://www.youtube.com/watch?v=hShY6xZWVGE
Sure, LLMs can understand images and video, but when you make your program spit debug text you make it easier and faster for Claude Code to iterate on it and fix any problems.
See how much value does a text UI program like Claude Code provide, it really doesn't need anything else than cannot be done in a terminal.
> it really doesn't need anything else than cannot be done in a terminal
I strongly disagree with this.
Claude-code would be super-powered if it had a better grasp of running processes without logging output. Imagine if it could somehow directly trace running programs, spotting exceptions and gauging performance in real-time.
It would be super-powered if it could actually navigate around a code-base and refactor through language servers without having to edit files through search & replace.
Imagine if instead of code, the program was first compiled to an Abstract Syntax Tree and claude worked directly on that AST instead of code.
Never a misplaced semi-colon* or forgotten import directive.
It needs a fundamentally different model to an LLM to operate it, but I'm convinced that thinking that Text is the endgame is a form of blub.
It's where we are now, and it's working very well, but it shouldn't be considered the long term goal. We can do better.
* To be fair, this one hasn't been an issue for a while now.
For small games I work on I make sure claude (well, codex cli) can produce screenshots of whatever screen it's working on and evaluate them. It has some instructions on using codex exec (claude -p) to use a clean instance for evaluation, so it can pass a screenshot and description of expectation and get a pass/fail and description of the failure. The main agent can also just view the image but for things with a clear pass/fail I prefer it invoke a clean context.
reply