A Professional Owns the Whole Outcome
Professionalism in software is owning the whole outcome: the cost, the failure, the 3am page, the wrong call. Process and titles don't cover it.
Writing, page 10 of 12
All 138 posts, newest first. The latest are on page 1, and the topic directory groups them by subject.
Prove the Return or Don't Spend the Time
Time is the only budget you can't refill, so every dollar and hour has to show a demonstrable return. The most common way businesses break that rule is buying software nobody asked for.
Elixir's BEAM Is the Runtime AI Agents Want
Go won the agent daemon and Python owns the reasoning. The layer nobody claimed is the one that bites you: thousands of long-lived, stateful, crash-prone agents you must keep alive. That's the BEAM's home turf.
Elixir Is the Language AI Codes Best
A Tencent benchmark across 20 languages found Elixir at the top of LLM code-completion rates: Claude Opus 4 hit 80.3% on Elixir vs 74.9% on C#. The reasons are the same boring properties that have always made Elixir pleasant, now compounded by AI.
Prompt Skills, Not Claude: Four Rules from Anthropic's Engineers
Most engineers prompt Claude one sentence at a time. Anthropic's own engineers prompt skills. Four rules from their recent talks, with the operator nuance the talks left out.
Elixir's Concurrency Model Is the One You Actually Want
async/await and goroutines solve scheduling. The BEAM solves failure. Why most concurrency pain is actually failure-isolation pain, and only the actor model plus supervision trees fix it.
Why Every AI Agent Framework Is Written in Go (And What That Costs You)
Open the repos behind the agent tooling you run (Ollama, the MCP SDKs, the orchestration engines) and it's all Go. The reason is that an agent tool is a concurrent network daemon that ships as one binary.
Ruby Isn't Dead, It Got Boring — And Boring Is Why It Ships
The "is Ruby dead" obituary runs every year and confuses hype velocity with shipping velocity. Rails 8 deleted the actual reasons people left: Redis, Sidekiq, the Node build step.
How I Prompt Claude as a Staff Engineer (50 Prompts I Actually Use)
Fifty prompts I use to ship production AI features, debug distributed systems, and write docs that don't rot. Code review, debugging, refactoring, system design, and PR-quality writing, with five full examples.
Ruflo (formerly Claude Flow): An Honest Deep Dive on the Multi-Agent Orchestration Platform
Ruflo (formerly Claude Flow) is a hive-mind orchestration layer for Claude Code and friends. 45,000+ GitHub stars, 700,000+ npm downloads, three queen-types...
The Claude Code Resource Bible: 46 Tools Worth Knowing in 2026
The 46 Claude Code tools worth installing in 2026, and the ones to skip, sorted by category with a recommended starter stack at the end.
What 90 Days of a Fractional Security Engagement Actually Looks Like
Most founders who book the intro call have already read three or four of my posts and arrive at the same question: "Okay, but what would the next 90 days actually look like if I hired you?" Here's the answer, week by week, with the real numbers.