Christoph Sprenger

CTO & Co-Founder of Dotbite ⚫️ Laravel ⚡️VueJS 🔥 NeoVim

[Christoph Sprenger @spre803]

@TablePlus Now i have this error :o

Internet connection was not interrupted.

[Christoph Sprenger @spre803]

@TablePlus From the app: kali-linux-2026.2-installer-arm64.iso

[Daniel Lockyer @DanielLockyer]

good lord what have I done

[Daniel Lockyer @DanielLockyer]

i don't know what they did but Anthropic cooked with Opus 5.5

[Taylor Otwell @taylorotwell]

Which Laravel? 😏

[Laravel @laravel]

Laravel MCP 1.0 is here 🎉

This is a big protocol upgrade with support for MCP version 2026-07-28.

Stateless servers, searchable tool catalogs, caching, improved OAuth, MCP Apps updates, and a lot more.

Quick thread 🧵

[vas @vasuman]

https://t.co/haApURmzAN

[Laravel @laravel]

Laravel 13 is here. This update focuses on AI-native workflows, stronger defaults, and more expressive developer APIs.

If you're running Laravel 12 or higher you can run /upgrade in Laravel Boost and have your agent upgrade your app for you.

[Gael Breton @GaelBreton]

Now living in Europe is a competitive advantage 😎.

Double usage until 2pm Every weekday 😇.

[Christoph Sprenger @spre803]

@TweetsOfSumit Opus is way better than GPT in my experience. And it also helps when providing a component library. Otherwise it gets tough very fast

[tobi lutke @tobi]

The most European thing imaginable.

Monitoring the situation!
(next week Monday)

[Christoph Sprenger @spre803]

@thdxr Isnt claude code and opus just way cheaper than codex? And thats why most use Opus over Codex?

[Christoph Sprenger @spre803]

@thekitze They are trying way too hard. All they produce is some short hype for some twitter baitors and afterwards nobody is using it anymore…
They should concentrate on making their models better

[Christoph Sprenger @spre803]

https://t.co/AOFWHKZlEx

[Christoph Sprenger @spre803]

@marcelpociot What do they change/make better?

[Benjamin Crozat @benjamincrozat]

Best Cursor rule for PHP developers:

Never use the "final" keyword.

[DHH @dhh]

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.

[Christoph Sprenger @spre803]

@TweetsOfSumit @vercel @render Seid ihr von nuxt auf next gewechselt oder wie kommts, dass ihr auf Vercel wart?

[Christoph Sprenger @spre803]

@benjamincrozat Next up is a client, who wants to participate in the work itself but has absolutely no idea, what he is doing. „And now you make it good“…