Contract Termination

[SandyDown]

That's a bit harsh isn't it.

If the Sys Admin department deliver a tulipe PC to a new starter (which IME happens about 101% of the time), why is it the newbies fault?

tim

Termination is very harsh, most client would ask contractors to do impossible jobs, that's why they hire us, if your face fits in and they like you then they'll ignore it and admit the job is impossible. If they don't like you then they'll use it to terminate you.

Don't know what you think but talking to agents while working for the client is bad if not done extremely discretely. I usually switch my mobile off and check messages every half hour, or immediately ask them if I could phone them back another time. You can always leave the office at lunch time and make all the phone call you want offsite. But again, it seems for whatever reason they didn't like you that's life, as Shilpa Shetty puts it ' the five fingers on your hand all different, don't expect everyone to like you'

Best thing is to move on and look for a new role to start ASAP

[SallyAnne]

as Shilpa Shetty puts it ' the five fingers on your hand all different, don't expect everyone to like you'

I never quite worked out what she was getting at with that, although it sounded beautiful when she said it

[MarillionFan]

"1/2 day for development and a week for testing"

LOL

[malvolio]

That's a bit harsh isn't it.

If the Sys Admin department deliver a tulipe PC to a new starter (which IME happens about 101% of the time), why is it the newbies fault?

tim

Yes it is harsh. But that's exactly how the client PM will have seen the issue. It might not be fair, it's certainly not "nice" but it is reality.

[MarillionFan]

"1/2 day for development and a week for testing"

ROFL.

I'd have fired you for giving that quote.

[black_knight]

"1/2 day for development and a week for testing"

LOL

Ahh...Don't be harsh. They wanted a small change, BUT my first clue at a problem should have been that I was being handed a system that had been worked on by someone who just left. It was mostly developed, but there was no testing done on it.

And AFTER I estimated the time, I found out that it was mostly written in VB.Net but some smart ass had thought "I know. I'll do a straight conversion to C#, and then not test any of it".

I knew I would be testing someone elses work, but found out late that the C# conversion was not tested at all.

I think I walked right into it.

My lesson learnt is to keep the client informed every step of the way. In the past I have been a little blck box, where requirements go in, and a product (and invoices) come out. In future I will provide a minimum of daily updates as to any issues and progress.

[black_knight]

I agree that this is a golden rule. NEVER EVER criticise or even comment neutrally on the working practices of the client's staff or the culture. Either say nothing or say positive things. no matter how obviously negative and counterproductive the culture is. Never be tempted to discuss or moan to others in secret or private even if you are invited to or to let off steam or if your confidante seems to be your best friend with equally negative things to say. It never stays private and you can guarantee the info will get back to those with the power to terminate your contract. To the permies it's like having a house guest and then hearing them criticise the furniture or curtains. Even if they too don't like the curtains or furniture that doesn't mean to say they want to hear it from you or have their noses rubbed in it that their working conditions are not that great implying that they've made a lousy career choice being with a company you couldn't bear to be staffed in. They'll soon make sure your career choice isn't all that hot either - hence the termination.

In fact, observe, notice and SAY NOTHING if it really is awful but doesn't affect your work. That is the only way you'll survive. You really need to be sure of your ground before you can start being 'open' about the working practices of others and you need to be aware of how critical your own role is before doing so. If the person you want to desparately slag off is more powerful or better positioned politically than you then it's best not to risk it because ultimately the only person who will be let go is the one that's easiest to replace not the one to blame.

Wise words. Where where you two weeks ago?

[Churchill]

I never quite worked out what she was getting at with that, although it sounded beautiful when she said it

Somehow, I didn't think you would.

What about the seagull and trawler referencence by "Sir Eric", did that spark a glimmer of understanding?

[lukemg]

OP - wouldn't be a telecoms company based in and around Crewe would it ?

[Ruprect]

You were in there a week and already bitching about the hours other people were doing? That's asking for trouble. Even if I wasn't happy about the hours I was doing I'd keep my gob shut for the first couple of weeks, at least until I'd established myself and had a PC that worked and I knew my way around the system. THEN if I was unhappy with the hours, i'd do 9-5.30 and put the onus on the client to ask for me to do longer hours, THEN tell them politely that the hours I keep are the ones I am contracted to do. If they want me to stay longer then they pay me for it.

Keep your head down and you gob shut - here endeth today's lesson.