ZeroMQ

Step 5: Solve One Problem and Repeat

You’re now in the happy cycle of issue-driven development, where you can start to solve tangible problems instead of adding features. Write issues that state a clear problem, and propose a solution for each. As you design the API, keep in mind your standards for names, consistency, and behavior. Writing these down in prose often helps keep them sane.

From here, every single change you make to the architecture and code can be proven by running the test case, watching it not work, making the change, and then watching it work.

Now you can go through the whole cycle (extending the test case, fixing the API, updating the protocol, extending the code, as needed), taking problems one at a time and testing the solutions individually. It should take about 10–30 minutes for each cycle, with the occasional spike due to random confusion.