January 27, 2015
I swear a good part of my day is spent listening to developers make a case for why something can't be done—it's too hard, it will take too long, it will introduce another bug, it will require convoluted code or introduce a tremendous amount of technical debt—and then synthesizing their argument and making a case to the product owner or the engineering director that the work should be altered, put off, or just axed entirely... only to find that...