2 ms·
What "good enough" means depends entirely on the maintenance horizon of the code. Is it some campaign web site that runs for 2 years with two updates in it's li
by alkonaut 10y ago
What "good enough" means depends entirely on the maintenance horizon of the code. Is it some campaign web site that runs for 2 years with two updates in it's lifetime? Or is it a code base that will receive 20k commits every year for the next 20 years? Working in the latter kind, I really wished people hadn't shipped so much "good enough to ship" code and had written more "good enough to maintain with ease for 10 years". I have only worked on one single project my whole career - with the first 12 years being before the first release! Not typical perhaps, but goes to show that "shipping more projects" isn't always an option.
Often these are conflicting goals too. If that guy hadn't shipped the kludge 10 years ago perhaps the company and project wouldn't exist today.
- deleted 10y ago[deleted]
- kwhitefoot 10y agoWell said!
- reallydontask 10y agoOften these are conflicting goals too. If that guy hadn't shipped the kludge 10 years ago perhaps the company and project wouldn't exist today. On some occasions the company folding would've been a better outcome for everybody involved in the medium term.
- Retric 10y agoThe trap is to look back and assume you can separate A from B. No system is universally maintainable for all new requirements and not all new requirements are predictable. Further code is always flexible as the absolute worst case is to start over with all the lessons from the first system. However, code that has not shipped is not creating value.