![]() ![]() ![]() The section compares procedural and OO code in terms of changeability and understandability. The next idea is about the difference between procedural and object-oriented code. The Design Stamina Hypothesis suggests that early on in a project you'll get more done if you don't bother too much with design, but a point will come when you'll be better off if you invest some energy into it. Notice that the blue line rises fastest early on, but that the orange line eventually overtakes it. The blue line illustrates the outcome if you defer serious design. The orange line illustrates how much functionality you will produce by any point in time by investing in design from day one. The further to the right, the later in time. The horizontal axis represents time passing. The higher the line, the more that got done. The vertical axis above represents cumulative functionality. #1: Design Stamina Hypothesisįowler illustrates this idea with the following graph. The first idea is Martin Fowler's Design Stamina Hypothesis. Imagine me waving my arms and drawing on the whiteboard. YMMV, but it'll give you something to think about. These thoughts are very definitely my opinion, justified only by past experience. In this newsletter I'll introduce each one and connect them together, in hopes that understanding these connections will help us understand our apps. Three apparently unrelated ideas have been percolating in my head. I've been thinking about how applications evolve, and what we might do if we're unhappy with the results.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |