Menu

1 / 3

Ship Now, Finish Later: gh stack Kills Branch Gymnastics

DEV Community: github·Giorgio Boa·17 days ago
#OWI6PrND
#devtogithub#technology#devto#dev#stack
Reading 0:00
15s threshold

The problem

Picture a Monday morning stand-up. A new feature has just landed on the board, and it is too big for one person. Someone takes the database schema, someone else picks up the API layer, and a third developer claims the UI. In practice, each piece depends on the one below it: the API needs the schema, and the UI needs the API.

Nobody wants to sit idle for two or three days while the first pull request waits for a reviewer, so everyone starts building on top of code that has not been approved yet .

Now picture a different conversation, this time with another team. The mobile developers need our new endpoints today. The business logic behind those endpoints, however, will take at least another week. The sensible move is to ship the API contract first, with the routes, the request and response types, and even mocked handlers returning realistic data.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.