3 ms·
Great topic and from scanning the table of contents the guidelines are well chosen. The matter maintainability is discussed far too seldom! I would like to add
by kluck 11y ago
Great topic and from scanning the table of contents the guidelines are well chosen. The matter maintainability is discussed far too seldom!
I would like to add that "maintainability" more often than not refers to maintenance "by someone else other than who wrote the first revision of some code".
- crististm 11y agoMaintainability is not the first topic of discussion when mantra is "build software to throw away". We're in an age of consumerism in software. We reinvent large pieces of software because we don't have a grip on existing ones to be able to repair or extend them. All the known acronyms including NIH are at work.
- adrianN 11y agoI guess it depends on your perspective. I'd argue the exact opposite; we're entering the age of huge, ancient, yet mission critical codebases that nobody really understands. Look at any piece of popular business software, eg SAP, or the software controlling most computer powered machinery, like factories. It's layers upon layers dating back to the 80s. The systems perform poorly even on modern machines, and have terrible usability because changing them is too hard.