3 ms·
I once worked one project with (against?) a guy who saw his job as ‘finding problems before they happen’. It was fine at first but as the project progressed, he
by taneq 2y ago
I once worked one project with (against?) a guy who saw his job as ‘finding problems before they happen’. It was fine at first but as the project progressed, he became more and more focused on proving that the project would fail. Every molehill was a mountain, and flat ground was just a tapestry of molehills. Eventually I realised that if the project didn’t fail, he felt superfluous.
- CoastalCoder 2y agoI've been that guy at various points. I thought I was being a valuable counterweight to developers who weren't thinking things through. But as you said, it can be taken to an unproductive excess. I managed to calibrate myself out of that, but it took longer than I'd have liked.