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 hapSep 15 · 16 min readbarnaby-dev-blog.hashnode.dev
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 taAug 28 · 14 min readbarnaby-dev-blog.hashnode.dev
Designing a Task Format Humans and Machines Can ShareOnce you decide that a task should be a file, the next question looks easy. What should the file look like? It is not easy. At first, the temptation is to make the format rich. Tasks have titles. StatAug 24 · 13 min readbarnaby-dev-blog.hashnode.dev
Git Is Already a Distributed Project DatabaseIn the previous article I asked a simple question: why do tasks live outside the project? Code lives in Git. Tests live in Git. Documentation lives in Git. Configuration lives in Git. But the work thaAug 17 · 12 min readbarnaby-dev-blog.hashnode.dev
Why Are Software Tasks Outside the Git Repository?I’ve worked on software projects built with very different methodologies. Some were Agile. Some were Scrum. Some were “Scrum” mostly because there was a board and a daily meeting. Others were closer tAug 13 · 9 min readbarnaby-dev-blog.hashnode.dev