4 ms·
I was lucky enough to start my career at a place which appreciated stable working software and the principle of slowing the fuck down. Then I had the unfortunat
by stevebot 12y ago
I was lucky enough to start my career at a place which appreciated stable working software and the principle of slowing the fuck down. Then I had the unfortunate experience of changing jobs and ending up at a place where speed was king. Developers were worshiped by their ability to blast through projects. I would call this the "Get Shit Done" principle.
What I have found is that you need a balance. "Slow the Fuck Down" gets you working software, but if that takes you twelve months to a year, you lose the sense of progress and accomplishment that having a live product gives you. There has to be a healthy balance between "Slow the Fuck Down" and "Get Shit Done" which usually involves cutting features, prioritizing and temporary fixes. Most projects using MOSCOW is a good place to start with this.
- sanderjd 12y agoI think it's unfortunately common to have "Get Shit Done" people that work on making greenfield stuff quickly and "Slow the Fuck Down" that make that stuff work and keep working, which is both technically and politically. Also, what is MOSCOW?
- V-2 12y agoPresumably http://en.wikipedia.org/wiki/MoSCoW_method http://en.wikipedia.org/wiki/MoSCoW_method