[thelist] setting team standards and guidelines

Jeremy Weiss eccentric.one at gmail.com
Tue Apr 24 11:38:52 CDT 2012

On Tue, Apr 24, 2012 at 11:23 AM, Hassan Schroeder
<hassan.schroeder at gmail.com> wrote:
> Uh, what?
>  ..."institute procedures and standardize things" ...
> To what end? What's broken that you're being asked to fix?

Basically, they have a room full of developers who each do things in
their own ways. There's no set guidelines for how things are done.
Some code in vim on the dev server while others check code out of the
svn and code locally. Some commit things back at the end of the day
regardless of stability, others only commit stable code. There's no
guidelines for when to branch or merge code.

Does that help explain things any better?

I could easily just roll in and say 'this is how I like it done' and
follow the procedures I've learned in previous positions. But I'd like
to learn more about how other companies do things so that I can make
better educated decisions.


More information about the thelist mailing list