2 ms·
As one of the dreaded "process enforcers" at my company, it's a tough line to walk. Any organization with more than a handful of people needs some written and a
by ryandrake 7y ago
As one of the dreaded "process enforcers" at my company, it's a tough line to walk. Any organization with more than a handful of people needs some written and agreed upon process or it's just chaos. But you can't just blindly follow a process for its own sake. You need to be able to articulate why we follow it with examples from the past of what happens without it. And, you need to be willing to constantly look for ways to improve it. Anything I can do to automate processes or simplify them makes the developers happier and more productive and me less of the bad guy. An inefficient process where people are always waiting on something to happen is demotivating to everyone.
Most process is scar tissue from something that went wrong in the past. We have mandatory code reviews because when we didn't we let a severe security bug get deployed to production. We have legal review all changes to the terms of service so we don't get successfully sued over it again. We have a schedule with code freeze N weeks before release because when we didn't we could never release anything because...just...one...more...change.
I was hired at a small company once without any process for anything. No release process or schedule. No bug tracker. No testing plan. No code reviews. Nobody used source control. Builds from different workstations produced wildly different binaries. It was a total madhouse and it was amazing that anything got done at all. The CEO simply thought the engineers just weren't competent enough, but they were--it was just a circus because nobody stepped up to formalize anything. Once we got a bug tracker and SVN set up, things turned around pretty quickly.