3 ms·
For me the key thing is that if you are doing "bottom-up" programming, then those macros/functions/etc. should be abstract and not related to business rules. El
by liampulles 3y ago
For me the key thing is that if you are doing "bottom-up" programming, then those macros/functions/etc. should be abstract and not related to business rules. Else you are doing premature abstraction, and you'll end up creating big rocks you have to carry on your back when you want to make a change.
As a consequence, I personally practice bottom-up very sparsely and carefully.
- jinwoo68 3y agoI don't think the bottom-up model denies the importance of the top-down architecture. In practice, you have pressures from both sides. You need to explore what's possible at the bottom but also respect what's required from the top. And they are complimentary. You explore what's possible from the bottom and then you need to adjust how you should organize those possibilities according to the requirements from the top. At the end of the day, as everything else in the world, it's all compromise.
- liampulles 3y ago100%