Quite a premium for speed. Especially when Gemini 3 Pro is 1.8x the tokens/sec speed (of regular-speed Opus 4.6) at 0.45x the price [2]. Though it's worse at coding, and Gemini CLI doesn't have the agentic strength of Claude Code, yet.
I hate the current token gym membership pricing models, they are too complicated and abstract and even worse, you have issues like what this post points out. They favor the providers, not the users. They create a lot of stress for users who have to decide if they can afford to point GasTown at their codebase.
The problem is that the companies serving LLMs can't delineate compute between users. You're using a cloud of compute, not a single individual unit of compute. If you could measure at the unit of compute, then you'd just pay by the minute for what you use instead of by the token, we would get out of this situation.
If you’re writing that much boilerplate as part of your day to day work, I daresay you’re Doing Coding Wrong. (Virtue number one of programming: laziness. https://thethreevirtues.com)
Any drudgework you repeat two or three times should be encapsulated or scripted away.
meetings hardly reach anywhere. most of the details are eventually figure out by developers when interacting with the code. If all ideas from PMs are every implemented in a software, it would eventually turn into bloatware before even reaching MVP stage.
I'm trying to work with vibe-coded applications and it's a nightmare. I am trying to make one application multi-tenant by moving a bunch of code that's custom to a single customer into config. There are 200+ line methods, dead code everywhere, tons of unnecessary complexity (for instance, extra mapping layers that were introduced to resolve discrepancies between keys, instead of just using the same key everywhere). No unit tests, of course, so it's very difficult to tell if anything broke. When the system requirements change, the LLM isn't removing old code, it's just adding new branches and keeping the dead code around.
I ask the developer the simplest questions, like "which of the multiple entry-points do you use to test this code locally", or "you have a 'mode' parameter here that determines which branch of the code executes, which of these modes are actually used? and I get a bunch of babble, because he has no idea how any of it works.
Of course, since everyone is expected to use Cursor for everything and move at warp speed, I have no time to actually untangle this crap.
I predict it's going to be a bloodbath. People who worked for Big Tech have no idea what's coming. Some of us software engineers who have been outside have been experiencing issues for almost a decade. The industry is extremely anti-competitive.
Whatever you produce, nobody is going to use unless you produce it under the banner of Big Tech. There are no real opportunities for real founders.
This feeling of doom that software engineers started to feel after LLMs is how I was feeling 5 years earlier. People are confused because they think the surface problem is that AI is automating them but reality is a systemic issue at the core of our economic system. AI is just a convenient cover story, it's not the reason why we are doomed. Once people accept that we can start to work towards a political solution like UBI or better...
The answer is the AI. It's already handling complex issues and debugging solely by gathering its own context, doing major refactors successfully, and doing feature design work. The people that will be held responsible will be the product owners, but it won't be for bugs, it will be for business impact.
My point is that SWEs are living on a prayer that AI will be perched on a knifes edge where there is still be some amount of technical work to make our profession sustainable and from what I'm seeing that's not going to be the case. It won't happen overnight, but I doubt my kids will ever even think about a computer science degree or doing what I did for work.
I beg to differ. Let's say you're right. Code producers should turn to agriculture and let their managers and product owners prompt AI to produce code. How about code maintainers? Ever heard the mantra "You build it, you run it"? Lets say that AI can build it. Can it run it though? All alone, safely, securely and reliably? No. It can't. We can keep dreaming though, and when will AI code production services turn profitable? Is there a single one which turned profitable?
> I believe we already have the resources to colonise the Moon and maybe Mars right now.
That is or was essentially the mission of the US government's Artemis program, as I understand it. Some elements of the plan are (or were):
'Civilize' (my word) the Moon - build PNT, situational awareness, communication infrastructure, bases, permanent human presence etc. Bring it within a normalized region of operations, like Earth orbit (though obviously much more expensive and less utilized). A benefit is developing plans for infrastructure and operations on Mars, in a much more friendly and less expensive environment. What does it take to support humans efficiently and reliably on another body?
Also conduct experiments and develop technology for Mars in cislunar regions - again, much friendlier and less costly.
i can't remember who said it but a long time ago i remember reading "Linux is free if your time is worthless". Now we all use Linux one way or the other.
Some of us bloggers have been writing about cool tech for 20+ years already. We didn't need to get paid to do it then, why should we need to be paid now?
I mean, you're just talking about spending money. Google isn't trying to build data centers for fun. These massive outlays are only there because the folks making them think they will make much more money than they spend.
The world IS responsible for handling the people. Thats the whole fucking reason we made society to take care of children. Nothing is inevitable. It serves the interests of the few.
Zero as long as your time is worth nothing, and bad code and security issues cost you nothing maybe.
"Getting code" has always been dead simple and cheap. Getting actually good code that works and doesn't turn into a problem for you down the road is the expensive part
Given that providers of open source models can offer Kimi K2.5 at input $0.60 and output $2.50 per million tokens, I think the cost of inference must be around that. We would still need to compare the tokens per second.
NATO could certainly rollover the Russian army in a conventional war, but that was just as true before the Ukrainian war. The idea that Russia is/was a serious threat is a convenient fiction: It helps maintain Russia's image as a superpower, and it provides a justification for the existence of NATO and the associated military industrial complex that supports it.
What is true however, is that Russia does possess a huge arsenal of nuclear and other weapons:
Despite Putin's posturing, Russia's never going to risk deploying them in a conflict with Ukraine. But in an actual war between NATO/Europe and Russia, with the regime facing an existential threat, then there's a very good chance they would. But even before it got to that point, the nature of the conflict itself would make nuclear escalation very likely. Both sides would be firing huge numbers of missiles, attempting to gain air superiority by wiping out the other's own missile launchers, radar bases, etc. With that many missiles flying, and stressed people and automated systems making split-second decisions, it's very likely that an error or miscalculation would result in an accidental nuclear strike, at which point it would be impossible to put the genie back in the bottle.
> The type of programmer were people would put up with just because they could really go in their cave for a few days and come out with a bug fix that nobody else on the team could figure out is going to have a hard time.
As an aside, I wonder why this wasn't discussed during the recent Greenland dispute. The US government basically legally pirate the drug, and it'd make a fairly large dent in Denmark's economy. It'd be a politically popular move too.
I think I 100% agree with you, and yet the other day I found myself telling someone "Did you know OpenClaw was written Codex and not Claude Code?", and I really think I meant it in the same sense I'd mean a programming language or framework, and I only noticed what I'd said a few minutes later.
