New top story on Hacker News: Ask HN: Software design patterns for projects without a scope?
Ask HN: Software design patterns for projects without a scope? 3 by rlayton2 | 0 comments on Hacker News. My work often involves starting with creating small prototypes that show a concept or solve a very specific problem. That prototype solves that problem, the client is happy and wants to extend it. The software grows from there, usually one feature at time. For these projects, the client usually doesn't know what comes next until they need it. This extension can sometimes be immediate, or could be years after the fact. "Common wisdom" states that the prototype should be thrown away when the concept is proved and the funds come in, but for me there is never a point at which that makes sense. As I mentioned, it's one feature at a time. I feel I do a good job at designing those prototypes in a decoupled, extensible way. I think about what direction the project could take, and try to put the right levels of abstraction in. Despite my best efforts, oftentimes I'm...
