Notes from the work.
Writing on product decisions, developer experience, and the practical side of AI.
Published at Oracle
Selected essays
All other essays 35
Proof points should route to evidenceDiscovery paths should name the first moveStart cards should name the routeGitHub Profiles Should Keep One Context Link Per TrackProject Tracks Should Point to Published WorkHomepages Should Offer Short Paths by IntentAlerting Starter Patterns Should Normalize Before They NotifyDecision Logs Should Keep the Revisit Date VisibleStarter Patterns Should Leave One Stable Handoff ArtifactDocs Checks Should Point at Publish BlockersValidation Gates Should Fail in a Useful ShapeAnchor Repos Should Carry the BatchRepo Tracks Should Recommend a First ExampleProject Pages Should Explain the BatchGood Small Repos Should Show the Second MoveGitHub Profiles Should Choose the First ClickGitHub Should Prove and the Site Should RouteRepeated Work Should Become a CheckFun Projects Get Stronger When They Leave a Reusable ArtifactStarter Repos Should Stop at the Right BoundarySmall Repo Batches Should Teach a PatternIncident Timelines Need A Stable ShapeAI Work Needs Real ToolsExamples Are the Interface for Small ToolsDependencies Need Owners Before They Need SlidesPublic Repos Need a Short Path to First Useful SuccessFun Projects Are How I Test Workflow IdeasOne-Page Tools Beat Premature DecksPublic Surfaces Should Route, Not ReciteGrowth Breaks In The Operating ModelAI Support Is A Workflow Design ProblemDeveloper Platforms Mostly Fail On FrictionFeature Registries Are About Operational ClarityMigration Readiness Is A Product ProblemWhy I Still Like Small Python Tools