The Argument for Process
I've been on a very accelerated timeline for a project that has the potential to make a very big impact to The Shop. But I've been amazed at the number of times that I've wanted to scream at the guys on my team about making sure they're doing the right things. I guess I take it for granted that developers know what it is they should be doing. In general, I've seen that not a lot of folks really do get it, and so it's clear why so many people fall back on process.
It's the way to ensure that things get done. But it's based on the idea that you don't really have skilled labor - you have a bunch of advanced beginners, and they need all the rules and regulations because that's how they code.
I understand why people push for this - it makes it appear that you can get good work out of marginally skilled workers. But you can't. Not really. The rules can't cover every possibility, and there will be things that fall in the cracks. There's no silver bullet - you have to have good, skilled people, and then you don't really need the rules.
Unfortunately, I'm not "there" yet. So I have to try to make the most with the people I've got.