hark at her

[vetran]

Problem is you need someone technically good enough to know what is possible who is happy to hear lots of people banging on that its all IT's fault that yet again the system has failed to guess what parts they need without a decent forecast or release goods when the customer has a credit rating a Tramp would be embarrassed about.

What you get is people who say yes and drive new Audis while the people that butcher the systems to get it to do what they want and fix the after effects who drive beat up Fords.

The Board and the Audi Driver look down on the Ford drivers and blame them when their Grand plans fail due to lack of customer engagement.

Now interestingly enough in my family that was an even gender split the males all chose technical subjects but the females chose softer subjects. There was no expectation of gender specific roles in their raising.

[Old Hack]

Very true. I can Masturbate at the highest level using one hand. Actually I don't need a whole hand - just a couple of fingers.

FTFY

Of all the bulltulipping Bulltulipers, you really do talk some bulltulip...

[Old Hack]

Your first point is wrong and contradicted by your second which is correct.
We don't need technical bulltulipters at board level (there are plenty of those already). We need good techies who can communicate important concepts in technical terms and have the balls, personality and credibility to put their view across.

You're right about there not being many of those.

That's ahorse load of tulipe for a start.

What's needed at board level are good techies who can communicate important concepts in non-technical terms. Having the balls is a given, if you're already there putting your views across, or even being asked in.

The main problem is people who over complicate tulip at board level. My last major permie role was with a software company headed up by 2 former Accountants (CEO and CFO). The Chief Technical Officer was not technical either, per se, coming from a lecturing background on the companys' niche area; knew shed loads about the subject matter, but not how to technically implement it.

[sasguru]

FTFY

Of all the bulltulipping Bulltulipers, you really do talk some bulltulip...

That's the other thing about techies. They imagine everyone is as crap as themselves.
Guess what, you smelly, sandal-wearing, hygienically challenged geek - I reported directly to the MD in my last (permie) role as where I created an analytics department from scratch.
I'm a suit who loves techie stuff and is good at it.
Not the sort of crappy dev stuff you do but the stuff that requires hard maths: Bayesian stats, HE modelling, that kind of stuff.

[doodab]

We don't need technical bulltulipters at board level (there are plenty of those already).

That's what I was getting at. It's a self policing clique.

We need good techies who can communicate important concepts in technical terms and have the balls, personality and credibility to put their view across.

These people exist. The trouble is they frequently end up trying to communicate important concepts in technical terms to people who lack both the background to understand and the time or motivation to listen to proper explanations.

I recently had to explain something to a fairly senior chap* at a very large IT services provider (essentially because some middle manager had decided there was a problem where no problem existed) and however many times and ways I tried to explain that distributing n things between n-1 boxes would result in at least one of the boxes having more than one thing in it, he just couldn't grasp it. I even gave a physical demo with pens, and he appeared to get it, except that he then proceeded to ask "so how are we going to stop it happening then"?

You can't explain something to someone who doesn't want to understand.

*doddering old fart

[vetran]

old hack, stop poking SasGuru.

It's cruel.

[sasguru]

old hack, stop poking SasGuru.

It's cruel.

It's like being licked by a dead sheep.

[sasguru]

What's needed at board level are good techies who can communicate important concepts in non-technical terms. .

That, at least, is correct. I meant non-technical.

[Old Hack]

That's the other thing about techies. They imagine everyone is as crap as themselves.
Guess what, you smelly, sandal-wearing, hygienically challenged geek - I reported directly to the MD in my last (permie) role as where I created an analytics department from scratch.
I'm a suit who loves techie stuff and is good at it.
Not the sort of crappy dev stuff you do but the stuff that requires hard maths: Bayesian stats, HE modelling, that kind of stuff.

Oh dear, I thought you had trouble squeezing one out, but I was wrong.

You have no idea what I do you fool, no idea at all. If you did, you'd wind that chicken neck of yours in.

I'd love to tell you, just to shut you up, but I fear the only thing guaranteed to do that, would be a good smack in your mouth.

I work at all levels Sas, as do heaps here.

Your stupidity knows no bounds.

[sasguru]

Oh dear, I thought you had trouble squeezing one out, but I was wrong.

You have no idea what I do you fool, no idea at all. If you did, you'd wind that chicken neck of yours in.

I'd love to tell you, just to shut you up, but I fear the only thing guaranteed to do that, would be a good smack in your mouth.

I work at all levels Sas, as do heaps here.

Your stupidity knows no bounds.

And there you have it. The comms skills of a typical techie.

So what great rocket science do you work in O great one?