We can't find the internet
Attempting to reconnect
Something went wrong!
Attempting to reconnect
All 138 posts, newest first. The latest are on page 1, and the topic directory groups them by subject.
Most pre-Series-A AI founders hire in panic order, not strategic order. The result is a team that can't ship the product the company actually needs. The hire-by-hire plan I'd run, who comes first, and why hire #4 isn't another engineer.
The hardest part of agentic AI in 2026 isn't getting the agent to do the work. It's knowing when to override it. The four-level autonomy ladder, the five signals an agent is going off the rails, and a real example of catching one before it shipped a quietly broken auth flow.
A fractional engineering engagement starts with a codebase you've never seen. You have ninety minutes to form a useful POV before the kickoff call. The seven-step triage I run, the two questions I bring back to the founder, and how AI tooling has accelerated the process.
A walkthrough of how I run 4–7 agent sessions in parallel through a normal engineering day. Morning background tasks, mid-morning pair programming, afternoon reviews, end-of-day ops. The interaction modes that work, the handoff protocol, and the trap that makes most agent workflows produce slop.
Most 'we delivered late' stories trace to one decision: the team scoped the first slice too big. The vertical-cut rule, the deploy-by-Friday filter, the pattern that breaks the heuristic, and a real before-and-after example.
A 4-person engineering team is the most overlooked unit of management in startups. Big enough that the lead can't write all the code. Small enough that hiring an EM kills velocity. Five rituals that work at this size, three traps to avoid, and the signal that tells you it's time to evolve.