4 ms·
That's from "The mythical man-month". Old, and some parts are obsolete, but still worth a read as it does have a bunch of good insights.
by bla3 4y ago
That's from "The mythical man-month". Old, and some parts are obsolete, but still worth a read as it does have a bunch of good insights.
- mianos 4y agoI have not read it in a while but it would be interesting to debate what essays are no longer relevant. I'll be grabbing it off the shelf next to my original copy of the Byte issue on C mentioned yesterday and having a look for expired relevancy.
- bla3 4y agoI haven't read it in a while either, but from memory the team organization of one "architect" and a bunch of implementers seems obsolete, for example.
- mrelectric 4y agoImho it's more relevant than ever, with the influx of cheap offshore remote developers
- EamonnMR 4y agoThere are some sections about physical copies of documentation and managing the logistics of that when I read it.
- 13of40 4y agoReminds me of a book I picked up about twenty years ago called "Testing Computer Software". I think it must have been written in the 80s, because instead of having a bug database, it talked about filling out a hardcopy form describing the issue and dropping it off at the programming department. I reckon you'd want to do it in duplicate on carbon paper, just so you can keep it in your own filing cabinet.
- froh 4y agowouldn't wikis be good the contemporary successors of that section? it's about documentation being disconnected from code, about co-evolving and providing both in an economical way, in contrast to being inefficient or even ineffective in documenting technology.