Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!
You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:
You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.
Logging in...
Previously on "Idiot team member cannot cope then passes blame"
The place I just left (good ridden) had no source control and the work was all over the place with no idea of who owned what or who was working on what. Thank God I am out there and now back at Radbroke where I can get involved in the discussion surrounding what source control to use rather than if to use it at all.
My point on source control, is that if you hand it over working, then some monkey works on it, you have an audit trail of who made the changes which fooked it.
Always good to have demonstrable proof you didn't, or did, do something.
Currently working with ACOMPANY who have denied just about everything about a working application, but have been quickly slienced with emails conforming delivery, and the actual stuff you delivered, with an audit trail in SourceSafe.
Keep just about everything you can, as in todays dog eat dog IT world, everyone is looking to dick you/preserve themselves.
My point on source control, is that if you hand it over working, then some monkey works on it, you have an audit trail of who made the changes which fooked it.
Always good to have demonstrable proof you didn't, or did, do something.
Currently working with ACOMPANY who have denied just about everything about a working application, but have been quickly slienced with emails conforming delivery, and the actual stuff you delivered, with an audit trail in SourceSafe.
Keep just about everything you can, as in todays dog eat dog IT world, everyone is looking to dick you/preserve themselves.
In my first ever job, I was handed code by a senior Consultant untested, told it worked, he farked off and it didn't work. I worked all weekend to fix it, which he could have done in a couple of hours possibly, knowing the project and all. On the Monday, I explained what had occurred, explained if he'd not been in such a hurry to go home (Fri afternoon and he lived many miles away) and actually tested it, it wouldn't be what it was. He wouldn't accept this and we actually had to go through an internal HR investigation as I was adamant I wasn't taking the can for someone elses cock up.
He was fired, and now, ironically, works for the company whom the major project was for.
Did you not put the code in Source Safe/others? I do religiously now, so I can pull an ear file or whatever else to prove where we were, with suitable comments. Don't get burned by liars BP.
Leave a comment: