Zach Attack is Back

a lowly code plumber getting paid 💰💰💰 to use c̸u̸r̸s̸o̸r̸ ̸a̸i̸ claude coder and LLMs to generate mid code that doubles my MRR every year.

[Zach Attack is Back @zachwritescode]

@awnihannun maybe open source claude models that run on MLX soon!?!!?

[Zach Attack is Back @zachwritescode]

lol, I broke @Alibaba_Qwen 's brain:

[Zach Attack is Back @zachwritescode]

@FrankieAshcroft @flyosity @SecWar thank you grok 🙄

[Zach Attack is Back @zachwritescode]

are people really this dumb? or is this rage bait?

[Doug McCormick @Extrodinarily]

@BlackBeret3 @InterceptorNews So soldiers are allowed to get FREE LOBSTER AND PRIME RIB meanwhile food stamps recipients can't? END THE UNFAIRNESS

[Zach Attack is Back @zachwritescode]

is it just me or is opus 4.6 kinda worse than 4.5?

[Zach Attack is Back @zachwritescode]

@awnihannun My favorite thing to do every morning now is git pull mlx and mlx-lm its like christmas every day

[Wenting Zhao @wzhao_nlp]

This release is an emtional one for me because I had stayed up so much for it 🥹 It has been truly amazing to see this model becomes better bit by bit through every change we make, and we have come a long way.

Since I did mid-training for this model, I wanted to share a little anecdote about this part. We really made this model with user experience as first-class consideration. We want people to actually use it, period. We took it so serious that we redid midtraining because we saw cases where models failed to follow instructions on out-of-distribution scaffolds. We decided straight-up that we would fix this in a fundamental way instead of surface-level patching. The resulting base model, which we also release, is thus a healthy base. We find that, compared to other base models, this one better learns new tasks.

Try fine-tuning our base and lmk what you think 🥳
https://t.co/KSvowSEdTu

[Zach Attack is Back @zachwritescode]

@brankopetric00 Mistake #1.5 - running services like ssh on standard ports

[Zach Attack is Back @zachwritescode]

@everythingnow52 @xavierjp__ Christianly speaking, ur an idiot and an embarrasment to christianity

[Zach Attack is Back @zachwritescode]

Lol. @theo is a junior dev? Shots fired.

[Lewis Campbell @LewisCTech]

Starting to realise that the pro/anti LLM debate is just a junior/senior programmer debate in disguise.

Think about it.

Senior devs like Ryan Fleury, Tsoding and Notch are all skeptics... but junior devs like Theo cite AMAZING productivity gains because their floor is so low.

[Zach Attack is Back @zachwritescode]

Honest question. Are you willing to pay $1500 for this?

[badcop @badcop_]

@dillon_mulroy git actually already has a really nice way to see which specific changes are associated with some text description

not many people know about this!

https://t.co/n1EdNcmhwj

[Zach Attack is Back @zachwritescode]

@alexschultz002 @badcop_ @dillon_mulroy People still write commit messages manually? This task was replaced by AI a long time ago.

[Zach Attack is Back @zachwritescode]

@badcop_ @dillon_mulroy

[Zach Attack is Back @zachwritescode]

@kenwheeler @Enscion25 Genuinely concerned for humanity at this point. I thought political divides were bad, but now we have to explain that LLMs are just computer programs and somehow that brands us insensitive or “virtue signaling” ?

This whole situation is in fact insane.

[Douglas A. Boneparth @dougboneparth]

If a man says he will fix something, he will! There’s no need to remind him every 6 months.

[Zach Attack is Back @zachwritescode]

Ok, starting to fall in love with the design of the new https://t.co/ETMJivl8YH ... @IanBakerRV @CampingWorld When can we get a manufacturing tour of these new 5th wheels!?!?!

[Zach Attack is Back @zachwritescode]

@SledgeDev @kenwheeler @theo @theCTO @AnthropicAI @cursor_ai @Apple Said no one ever

[Zach Attack is Back @zachwritescode]

@dillon_mulroy @BraydenWilmoth And then get out of their way, let them cook and ship. If you pile on protocols, hurdles, multiple review processes, specific release days, that take days/weeks to ship the fix to prod… you will lose those people.

[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.