Never as complicated or sophisticated as client makes out

[eek]

Rarely on the first day.

I've worked in on many complex implementations, though, from a business requirements perspective, a technical implementation perspective, and a UI requirements perspective.

I can't think of a project that I've work on where I've thought "that's straightforward".

I don't think I've ever worked anywhere where there isn't one or two things which prompt the question "why on earth, do you do that, that way?"

[speling bee]

Maybe you only get offered easy contracts.

Maybe it all looks a bit simple if you are a bit simple.

[Mich the Tester]

I don't think I've ever worked anywhere where there isn't one or two things which prompt the question "why on earth, do you do that, that way?"

WHS, leading to the possible answers;

- 'that's how we've always done it'
or
- 'it's best practice'

Both of which can irritate me somewhat.

[Scruff]

Only 4 years?!

Yeah, but I have to go to Africa for a month a year R 'n R...

[woohoo]

I started a contract that used various design patterns and a whole load of WCF to communicate between layers. It was one of the most complicated dev environments I worked in only because there didn't seem to be any logic to why certain patterns and tech had been used.

I thought it was me at first being dim, but after being there for a little while I noticed that other dev's didn't have a clue either. They even had an architect there, I think he must of used this application as his first design project and wanted to get every damn pattern in there.

Oh the fun of finding out that your test system running locally was actually using a test service running on a test machine that was being amended by someone else or hijacked for testing of another product. Coming into work and never knowing if you would be able to run the application was always fun.

[OwlHoot]

... the biggest obstacle to getting productive at clientco is actually the tool chain, which they think is highly advanced but is actually a rather ramshackle collection of overpriced tools connected by fragile in-house interfaces and completely loony MS word and excel macros ...

Yep, seen it loads of times at various client sites (including some large multinational ones who should know better).

Complicated and unreliable largely because it _is_ unsophisticated, in the kind of way you summarise.

[eek]

Yep, seen it loads of times at various client sites (including some large multinational ones who should know better).

Complicated and unreliable largely because it _is_ unsophisticated, in the kind of way you summarise.

Its hackville and just about works. No one would however dare change it as that is the system and process

[original PM]

Yep, seen it loads of times at various client sites (including some large multinational ones who should know better).

Complicated and unreliable largely because it _is_ unsophisticated, in the kind of way you summarise.

I know why this happens - have you ever tried to get even the most simple of changes/updates done to a system in some companies?

It is like pulling fookin teeth with all the red tape and beaurocracy and politics and stupidly exensive outsourced systems cos the bloke who owns that company is the mate of the MD and so can charge a fortune.

OMFG - chuck in a macro in excel so we can all get on with our lives.

[Sysman]

Agreed. Many years ago when I was a junior desktop one of the secretaries asked me how to do xyz in wordperfect (shows how long ago). Buggered if I know I told her - you know more about it than me (she used it all day every day). She was aghast that I worked in IT and didnt know every feature of every single software package that every person in the company used.....

That reminds me of a nightmare contract that was up for grabs in the early-nineties when work was scarce.

The client had apparently got through a few folks already because as soon as he caught them looking something up in a book they got their marching orders. This was in the days before internet or even decent built in help.

I didn't bother applying for that gig.

[Sysman]

WHS, leading to the possible answers;

- 'that's how we've always done it'
or
- 'it's best practice'

Both of which can irritate me somewhat.

How's about:

It's got to run with full privileges because it's special

Absolute cobblers! Just fixing basic things like file ownership meant it could run fine with ordinary privilege levels.