3 ms·
I've recently taken time to start reading The mythical man-month book by Fred Brooks. As far as I remember (first read through this week and big parts of the b
by eitland 7y ago
I've recently taken time to start reading The mythical man-month book by Fred Brooks.
As far as I remember (first read through this week and big parts of the book is stuffed with quotable material) he says that
- that the architect should be able to provide an example implementation
- but that it is also important that the architect steps back and stays away from the actual implementation
I've more or less already decided to re-read that book.
Highly recommend and available in searchable selectable PDF form from archive.org
- closeparen 7y agoThe book’s use of the term “architecture” is pretty different from modern usage. It refers to the shape that the new computer/OS will present to application developers. The architect is something like a product manager; a voice for what the customer wants. What my team calls “architecture” - the decomposition into services and classes, database schemas, interfaces between major components - I think Brooks would call “implementation design.”
- eitland 7y agoPartially agree: It seems to me that he would think interfaces between major subsystems would be architect level while any database table that only gets used within a single sub system is implementation level. Trying to be careful as I realize HN is the kind of forum where he or a close friend of him might show up to correct me :-)