Omarchy Review: Seven Weeks, Three Machines, One Verdict
Seven weeks after my first install, I'm keeping Omarchy. What worked on an RTX 3070 desktop, what broke, and what 4.5 RC changes.
We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
Long-form essays for founders, engineering leaders, and senior ICs building at AI-native startups. Real numbers from real engagements, opinionated on what actually works. Browse all 21 topics → Earlier writing from the original Sublime Coding blog lives in the archive.
Curated reading orders by subject. Start here if you want the argument for a topic compressed into 5–6 essays rather than browsed across the full index.
What production AI engineering actually looks like in 2026: the autonomy ladder for agents, the workflow shift, telemetry, and team sizing.
A guided reading order for startup security: what to read first on SOC 2 as a revenue tool, vCISO hiring, and securing AI-native products.
Engineering leadership at startup scale: hiring from one engineer to fifteen, rituals that work at small teams, the staff-engineer interview loop.
Why language choice matters for AI systems: BEAM concurrency for agents, what Go frameworks cost you, and why Elixir is the language AI writes best.
Running Omarchy with coding agents, starting on an M1 MacBook: the install, what breaks, the keyboard, and what a security lead inherits from agents.
Seven weeks after my first install, I'm keeping Omarchy. What worked on an RTX 3070 desktop, what broke, and what 4.5 RC changes.
AI vulnerability discovery is turning years-old bugs in PHP and Linux into week-long finds. What old code you expose, who owns it, and a checklist.
Anthropic's AI code review works because flags and fast rollback sit under it. A small team should first add checks an agent can't talk into a pass.
Two critical PHP flaws, php2shell, got fixed on Oct 21. A triage order for anyone with PHP on a server: inventory, patch and restart, mitigate, isolate.
Eight eMudhra CA keys were guessable. Browsers blocked them in hours. Req reads CAs from the OS first, so bumping castore usually does nothing. Here's the fix.
A fractional Chief AI Officer for a 5-20 engineer team owns the daily agent workflow, not a governance board. The four jobs and the first 30 days, week by week.
Anthropic built Scion and moved its monorepo off git in five months. Here is why a small team shouldn't copy it, and where to spend the attention instead.
Engineers run Claude Code and the auditor wants proof. The managed settings that work as controls, the SOC 2 criteria they support, and the evidence to give.
This site has no database. Here's how a future-dated post stays invisible until its timestamp, and the three places the gate gave the wrong answer anyway.
If robots do the work and nobody earns, who buys? I think the economy dies slowly and the company store fills the gap. That's where I think it goes.
Tax all US output at 100% and it comes to about $95,000 a person a year. Why I doubt UBI arrives, and think robots become the measure of wealth.
Teams built real review gates around agent-written code. The PR descriptions, design docs, and incident summaries the same agent writes pass through nothing.