Matthew GarrettTrying to convince my students that having all your security policy changes include a design doc describing the status quo, the desired outcome, why this change will achieve it, why alternatives were rejected, and then implementing it via some automation schema so it can't accidentally be reverted for no obvious reason is good actually
They have apparently never known the pain of it being literally impossible to determine why something is the way it is and having no idea whether changing it will break anything
Lars Wirzenius@mjg59 Ah to be young again. Software development in general is much easier when you're young, with good memory, and working on something that didn't exist last week. It gets harder the older you get, the older the project gets, and the more people have been involved.