4 ms·
>"you shouldn't remove/replace/change something until you've understood why it was done that way in the first place". That only works until you encounter somet
by stult 9y ago
>"you shouldn't remove/replace/change something until you've understood why it was done that way in the first place".
That only works until you encounter something for which there was no rational reason in the first place.
- artimaeis 9y agoI've yet to encounter anything erected for no reason at all. But there are plenty of projects where rationality didn't have much a role in their choice of creation. Examples like that can usually be tied to a previous dev/engineer wanting to pad their resume with a new project, maybe with a new framework. Or a manager who wanted their team to have more completed work to look better on some miscalculated performance metric. Failing those options - it could be a bored employee who just wanted to make _something_. That is to say - most people are acting rationally, but their context to an outsider may not appear rational. Maybe there's something to be said for a general relativity of rationality?