in reply to OT: Job Advice

My advice - find somebody who shares similar ideals for clean code, that way you have an ally. Don't force your ideas upon people, but just suggest small changes at team meetings - start with source code control - suggest that you should have a backed up CVS server (or some alternative revision control engine). And follow it through by simply installing one in your lunch hour - otherwise nobody is going to use it. Show your boss how great it is to get commit emails showing you what has changed and who changed it.

Once you start to bring improvements like that to the company, you'll soon find that you are both trusted, and that your probation period is very quickly over.

Replies are listed 'Best First'.
Re: Re: OT: Job Advice
by dsheroh (Monsignor) on Jun 26, 2002 at 14:17 UTC
    Of course, that may not work... At my previous employer (R.I.P.), I introduced them to the wonders of CVS and bug tracking systems. I thought they were great. The other linux-friendly programmer loved them in principle, but rarely used them. The Windows-zealot-consultant bitched and moaned about being asked to use something which didn't come from Redmond, even after I showed him how to integrate CVS into the MS IDE. And the QA guy (yeah, we needed more than one tester and I kept telling management to get more of them, but it was a small company and one was all they'd give us) absolutely hated me for insisting that he file bugs in a trackable fashion instead of just walking over and saying, "X isn't working".

    But that company doesn't exist any more... Small wonder.