[mb_72]

One place I worked - the main electricity supply and management company for a certain state and certain country - I didn't have admin rights to my own machine, and had to put in a (paper) request for any software that I needed to install to do my job (as the image started as the same image used by someone who would only need Word, email etc). I didn't know exactly what tools I needed, so it took - seriously! - some few weeks before I could actually do any work.

My job was supporting, enhancing and debugging internal tools used by engineers. Upon arrival I was handed a USB key with ZIP files of the source. There was no source control. I initiated a request and the political process necessary to 'allow' me to use source control and setup an SVN (this was quite a while ago) server. I quit in disgust a year later, and the first meeting to discuss whether I should be allowed to use SVN or not was scheduled for the day after my departure. My last work action there was to leave a note on my desk advising my replacement where the most recent ZIP files of source were stored.

None of the above was explained to me before I was employed, and I've since learned not to assume, and explicitly ask "Do you use source code control?" and other basic questions at interview / contract negotiation stages.

[Viliam1234]

> I've since learned not to assume, and explicitly ask "Do you use source code control?"

So did I, but when they told me "Yes", it often turned out to mean "Yes, but only in a few departments; not the one you will be working at", and in one case "Yes, but we only use it as a backup system for the completed project, not during development".

Asking the right questions is important, but it's only half of success; the other half is getting truthful and non-misleading answers.