When the Repository Becomes the Project InterfaceThere is a strange thing about good architecture.Sometimes the best features are the ones you never had to build. You change the model. Then certain problems simply disappear. That is what started hap16 min read·barnaby-dev-blog.hashnode.devSep 15
When Tasks Branch With the CodeOnce tasks live in the repository, something strange happens. They stop behaving like tickets. They start behaving like project state. At first this seems like a small difference. A task is still a ta14 min read·barnaby-dev-blog.hashnode.devAug 28
Designing a Task Format Humans and Machines Can ShareHow should tasks, workflows, and team identities live in Git? Exploring simple file formats that work for humans, tools, and AI agents.13 min read·barnaby-dev-blog.hashnode.devAug 24
Git Is Already a Distributed Project DatabaseExplore how tasks, workflows, and team data can live inside Git, turning the repository into a distributed source of truth for the whole project.12 min read·barnaby-dev-blog.hashnode.devAug 17
Why Are Software Tasks Outside the Git Repository?Code, tests, docs, and configuration live in Git. This article explores why tasks usually do not—and what if a task is saved to the repository.9 min read·barnaby-dev-blog.hashnode.devAug 13