3 ms·
I used to approach problems bottom-up, and I often prefer it when I'm working on my own because I do feel I have a much deeper understanding of the system as a
by cwilper 3y ago
I used to approach problems bottom-up, and I often prefer it when I'm working on my own because I do feel I have a much deeper understanding of the system as a whole that way. But on larger teams, and especially teams with junior developers or communication boundaries, I find a top-down approach to be much easier to get everyone on board with.
- deleted 3y ago[deleted]
- fuzztester 3y agotop-down is impossible because real systems have no top. https://softwarequotes.com/author/bertrand-meyer https://softwarequotes.com/author/bertrand-meyer
- Jtsummers 3y agohttps://bertrandmeyer.com/OOSC2/ https://bertrandmeyer.com/OOSC2/ - The book being quoted is now available for free, the quote you're referencing comes from page 108. (PDF page 138)
- fuzztester 3y agoThanks. I had read most of it many years ago, the print version, but will read this online one again. IIRC, there's an Easter egg of a kind at the end of the book. Looked it up. It seems the Notation section of the book's Wikipedia page mentions two Easter eggs (sort of). https://en.m.wikipedia.org/wiki/Object-Oriented_Software_Construction https://en.m.wikipedia.org/wiki/Object-Oriented_Software_Con... I had tried out Eiffel at that time. Very systematically designed language, I thought, though I'm not a language lawyer.
- fuzztester 3y agoActually, seven, not two. Six times throughout the book, and once in the Epilogue. Again, see the Notation section.