peter_marklund

The Maintenance Burden of Microservices marklunds.com/articles/one/4…

@gudmundson_per In a sense music has been democratized though since now everybody can make music on their laptop and release it to Spotify with the click of a button and it won’t cost you almost anything and you will have professional music technology. Just don’t expect to make any money from it

Slutparentesen för min generations kultur är satt. Rock'n'roll 1955-2012.

Microservices youtu.be/y8OnoxKotPQ?is… via @YouTube

Logging Sucks - Your Logs Are Lying To You loggingsucks.com

Why AI won’t wipe out white-collar jobs | The Economist youtu.be/1CAvNn5tUR8?si… via @YouTube

Useful overlooked JavaScript console functions for debuggning - table, assert, trace, time, timeEnd @me4saurabh4u/agethe-console-log-trick-that-senior-developers-dont-want-you-to-know-af66d61eda99" target="_blank" rel="nofollow noopener">medium.com/@me4saurabh4u/…

Head of Claude Code: What happens after coding is solved | Boris Cherny youtu.be/We7BZVKbCVw?si… via @YouTube

I just open sourced a little command line tool called json that I use as a complement to jq for working with JSON data in the terminal github.com/peter/json

Is Hetzner a Good Alternative to AWS? Real Migration Cases by Gart Solutions   gartsolutions.com/hetzner-is-alt…

Everyone is Staff Engineer / Architect Now! youtu.be/O9uSrCEV1MY?si… via @YouTube

OpenCode vs Claude Code builder.io/blog/opencode-…

Ship first and scale later youtube.com/watch?v=U9xY9V…

The job market

The Infinite Software Crisis – Jake Nations, Netflix youtu.be/eIoohUmYpGI?si… via @YouTube

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.

“Just write code like a normal human f*cking being, please”

THE BIGGEST AND MOST DANGEROUS BUBBLE (Guest: Julien Garran) youtu.be/q8Uy1pjrBC0?si… via @YouTube

Clickhouse: Faster Queries, Faster Answers (with Alasdair Brown) youtu.be/S8ldDYxjyLQ?si… via @YouTube