![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Entry tags:
Developing software piecemeal
My programming at work recently has mostly followed a familiar sequence. For each component,
The second step is hardest on my sleep when I think about detail of what to do next and just want to get up and do it. It is also the most interesting with its
It made sense to complete my work on the webapp component first because the product and user experience people can test and improve it while I work on the less visible and interactive facets of the project. Further, the component I am working on now isn't strictly required for launch as long as it follows soon afterward. I expect to be able to finish it this coming week.
- figure out how to make it work
- for a missing piece, write its code, rinse and repeat
- test and debug it.
The second step is hardest on my sleep when I think about detail of what to do next and just want to get up and do it. It is also the most interesting with its
rinse and repeatin that, even if I do not start with a complete picture, if I keep filling in the next piece that I see that I need then eventually I end up having done them all. Sometimes, I find myself building a scaffold of increasing abstraction, such that I build pieces that enable other pieces to be built more easily: earlier pieces make the shape of other pieces clearer and simpler. Fortunately, it always seems that if any pieces remain to be done then at least one of them has a clear path forward, so they all get done in the end.
It made sense to complete my work on the webapp component first because the product and user experience people can test and improve it while I work on the less visible and interactive facets of the project. Further, the component I am working on now isn't strictly required for launch as long as it follows soon afterward. I expect to be able to finish it this coming week.