Topic · 7 posts
Engineering culture
What "good" looks like when three teams have to ship through each other. Notes on design-doc hygiene, disagreement-without-injury, and the review habits that make a codebase feel boring-in-a-good-way.
Code gets shipped by teams, and teams are held together by habits that nobody puts in the README. The posts under this hub are attempts to name those habits so they can be copied, argued with, or replaced on purpose rather than absorbed by accident.
§ Editor's picks
Start here
§ Writing
All writing on engineering culture
- Jan 2026 Why I run five CLI agents, not one Most frame LLM-coding-agents as winner-takes-all. My reality: five in rotation, each good at a different local minimum, swapped atomically via a Go CLI I wrote.
- Sep 2025 AI-assisted engineering is a new collaborator model, not autocomplete After 3,400 commits running Claude Code, Codex, Gemini, PI, and OpenCode side-by-side: the pattern that works is clear, and most teams miss it.
- Feb 2025 The onboarding doc I wish I'd had at 22 A letter to every new software engineer about what nobody told me in my first decade. Specific habits that compound, with receipts from 15 years of shipping.
- Dec 2024 Playing Captain What it actually means to lead by staying in the code - and why 'engineering managers should stop coding' is advice for a different team shape than mine.
- Mar 2024 From Gaming Center Net-Admin to Architect What an unusual path through retail, LAN cables, and a gaming hall in Amman taught me that a straight line from CS degree to big tech never could.
- Feb 2024 Teaching Open Source at 22 in Amman I co-founded a university OSS club in 2009 when open source was still an unusual pitch in the MENA region, and J2ME was a viable mobile platform.
§ Related