Linux Setup Was a Hazing Ritual. Agents Changed It.
Why developers picked macOS over Linux was never the OS. It was the setup. Six breakages on my own machines, and what an agent changed about fixing them.
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.
Why developers picked macOS over Linux was never the OS. It was the setup. Six breakages on my own machines, and what an agent changed about fixing them.
Going fractional? Get in the door with one narrow problem, then make the rest of your work easy to find, because the engineers who find you pull you into more.
This site has no Ecto, no Repo, no database at all. Here's how the newsletter signup works when the system of record is a third-party API, not a table.
Every talk, bio, and commit you publish to build a name is also recon and impersonation fuel. A vCISO's founder-scale checklist for hardening your identity.
Ten skills my coding agent runs to fact-check drafts and find where my posts stop reaching people, tested on my own site before I sold them.
Discord and Supabase publish Elixir libraries. What each solves, whether it is still maintained in 2026, and whether a small team should depend on it.
Omarchy's new Agentic QA swarm tests every release. I run Omarchy on two machines and update within days. Here's what the design catches, and what it can't.
A viral infographic ranked 15 companies using Elixir by valuation. Fact-checked: nine rows hold up, three are stale or unsupported, four name the wrong system.
DHH told Rails World 2026 that hand-writing code no longer pays. What he gets right, what Basecamp 5 proves, and who owns the code nobody reads.
An engineer wants to run Omarchy on a company laptop. Here's the verdict a security lead signs off on, control by control, for a SOC 2 Type II shop.
I graded my own site against a 2014 developer-marketing course. It was right about the two things I skipped, dated on platforms, and silent on AI answers.
Omarchy has 200+ keybindings and most work unchanged on a MacBook. Here's the ~15 that don't — screenshots, brightness, Fn, lid, trackpad — and why.
Omarchy's launcher gives every coding agent a skip-approval flag by default. The attack surface a security lead inherits, and what Omarchy gets right.
An engineer who builds AI systems ranks 13 ways to make money with AI in 2026 by ceiling, moat, time to first dollar, and fulfillment burden.
Cisco NSO and ConfD run their core on Erlang. Why the network-automation world never noticed, and where the BEAM actually fits this domain.
PRC labs harvested their own users' sessions, many arriving via third-party model routers. The fix isn't about Claude — it's treating the router as a vendor.
I set two agent frameworks loose on real work in team-of-agents mode. They agreed their way into the wrong product. The research says exactly why.
Omarchy's own AGENTS.md, skills, and a design doc reviewed by two other vendors' agents — read from the quattro branch, not the README.
Anthropic published an economic upside scenario and an alignment risk admission the same week. The upside needs the thing nobody has a plan for.
Ecto schemaless changesets as the pre-execution trust boundary on LLM tool-call arguments, not another output-shape validator.