Re:How to Build Good Software
by lifeisstillgood on Monday August 19, 2019 @01:52AM
(#20735219)
It's not that they have the knowledge but that the knowledge is now encoded in software and available to anyone else - software shares knowledge without the users having to learn it (for example having to learn which five systems need to have their names enters in order to pay their parking fine
[ Parent
| on HN ]
Re:How to Build Good Software
by jeffreygoesto on Monday August 19, 2019 @02:16AM
(#20735325)
This is not what I have experienced, at least not in real world software with mediocre documentation. Usually the software encodes only the "how", but the important parts are "why" and what aspects of the original problem led to that design.
Good teams learn how to transfer and adapt in the next project. Starting with the software only, lots of that can only be reverse engineered.
That was something I picked up from one of the more experienced software devs when I started - in his code there were far fewer comments saying "This section does x and y", than there were comments saying "We are doing x and y because ..."