2 ms·
Years ago, and in fact as I was coming off of a security-related job, I had the notion that we should map out decisions as a first class citizen of the developm
by hinkley 3y ago
Years ago, and in fact as I was coming off of a security-related job, I had the notion that we should map out decisions as a first class citizen of the development cycle, instead of or in addition to requirements (requirements are just one sort of decision). The problem with unexpected behavior is often a matter of Chesterton's Fence. We know something was done on purpose, we can't remember why, and so we break the constraint with crossed fingers and an uneasy feeling. If we tracked why we did things, which ideas supported which other ideas, which ideas complicated other ideas, maybe we would spot these sorts of things, and also the contradictions we try to put into the code.
What ended up souring me on the whole idea was realizing this would be a wonderful Blame Allocation System, by attaching names to decisions. It's been a while since I went from full enthusiasm to creeping dread so fast on a product idea, and probably not since.