För några år sedan skröt Norges skattedopade batterifabrik Morrow om att man var ”två år bakom Northvolt”.
I dag gick de i konkurs. https://t.co/Jk3oqlpJKS
If the USA does not intend to honour the obligation to defend NATO because European countries dont join an offensive war of choice against Iran that we have absolutely no obligation to join, the USA membership of NATO is already worthless.
The NATO oath to defend each other is unconditional. If you dont intend to honour it because you are offended about disagreements that have nothing to do with the treaty obligation that you have sworn to uphold, your are not a realiable ally. Tresties with you are worthless and your word means nothing.
Unfortunately, that seems to be the case for the USA.
AI about to get 20x expensive.
These $200 / month claude subscriptions are burning $5,000 worth of credits.
The bubble is going to pop and it will pop soon.
Claude Code 2.1.71 has been released.
4 flag changes, 28 CLI changes
Highlights:
• Added /loop command and cron scheduling to run prompts on a recurring interval within a session
• Fixed long-running sessions where stdin stopped processing keystrokes
• Fixed /fork plan file sharing so edits in one fork no longer overwrite another
Complete details in thread ↓
If you are a software engineer "experiencing some degree of mental health crisis", now hear this, because I've been coding for 50 years since the days of punched cards and I have a salutary kick in your ass to deliver.
Get over yourself. Every previous "programming is obsolete" panic has been a bust, and this one's going to be too.
The fundamental problem of mismatch between the intentions in human minds and the specifications that a computer can interpret hasn't gone away just because now you can do a lot of your programming in natural language to an LLM.
Systems are still complicated. This shit is still difficult. The need for people who specialize in bridging that gap isn't going to go away.
As usual, the answer is: upskill yourself and adapt. If a crusty old fart like me can do it, you can too.
If the US annexes Greenland we must confiscate all US bases in Europe, says Austria's NATO enlargement committee chairman Fehlinger.
"If you take Greenland, you have to leave".
The Sun is an incredible source of fusion, not a controllable system.
Engineering isn’t about where the biggest energy exists, it’s about where energy can be converted, throttled, stored, routed, and scaled on demand.
We don’t build reactors because we forgot the Sun exists.
We build them because civilization needs local, dispatchable, controllable power that doesn’t require orbital megastructures, perfect transmission, or planetary-scale risk.
Same reason we don’t power laptops by pointing them at stars.
Microservices is the software industry’s most successful confidence scam. It convinces small teams that they are “thinking big” while systematically destroying their ability to move at all. It flatters ambition by weaponizing insecurity: if you’re not running a constellation of services, are you even a real company? Never mind that this architecture was invented to cope with organizational dysfunction at planetary scale. Now it’s being prescribed to teams that still share a Slack channel and a lunch table.
Small teams run on shared context. That is their superpower. Everyone can reason end-to-end. Everyone can change anything. Microservices vaporize that advantage on contact. They replace shared understanding with distributed ignorance. No one owns the whole anymore. Everyone owns a shard. The system becomes something that merely happens to the team, rather than something the team actively understands. This isn’t sophistication. It’s abdication.
Then comes the operational farce. Each service demands its own pipeline, secrets, alerts, metrics, dashboards, permissions, backups, and rituals of appeasement. You don’t “deploy” anymore—you synchronize a fleet. One bug now requires a multi-service autopsy. A feature release becomes a coordination exercise across artificial borders you invented for no reason. You didn’t simplify your system. You shattered it and called the debris “architecture.”
Microservices also lock incompetence in amber. You are forced to define APIs before you understand your own business. Guesses become contracts. Bad ideas become permanent dependencies. Every early mistake metastasizes through the network. In a monolith, wrong thinking is corrected with a refactor. In microservices, wrong thinking becomes infrastructure. You don’t just regret it—you host it, version it, and monitor it.
The claim that monoliths don’t scale is one of the dumbest lies in modern engineering folklore. What doesn’t scale is chaos. What doesn’t scale is process cosplay. What doesn’t scale is pretending you’re Netflix while shipping a glorified CRUD app. Monoliths scale just fine when teams have discipline, tests, and restraint. But restraint isn’t fashionable, and boring doesn’t make conference talks.
Microservices for small teams is not a technical mistake—it is a philosophical failure. It announces, loudly, that the team does not trust itself to understand its own system. It replaces accountability with protocol and momentum with middleware. You don’t get “future proofing.” You get permanent drag. And by the time you finally earn the scale that might justify this circus, your speed, your clarity, and your product instincts will already be gone.