Back to coding

[Francko]

2- Are you a coder or an Architect?? for the last few years you have been bragging that you are an architect, do you classify managing a team and drawing few diagrams with arrows from one box to another as technical?? I bet you haven't done a line of code since you were contractor last (I think that was around 2000?? but that's not to put you down or anything, as I said before some of my best friends are architects - but frankly I think IT architecture is a glorified system analysis

I can still do coding but doesn't take longer than 5-10% of the full time. But still you can learn, study, help developers on some issues, review the code, etc. And no I have never been a "powerpoint" architect. Architecture is about analysis, of course. I yet don't see the point of these barricades....

[shoes]

you need to be very intelligent to succeed in a technical position and obviously in business too with the exception that in the first there is very little space for the middle ranges. Either you are good or you are bad. There is not much space for mediocrity. Business positions instead have a wide range of mediocre skills, simply because most tasks can be satisfactorily performed based on what everybody has learned at primary school, such as the ability of writing, talking, reading, etc. Sure you can spot a difference with the good ones but the mediocre can be good enough. In a technical activity you can't get away with what you have learned at school but it's all new learning and requires continuous training.

This is the main point - well made. Coders can do your job using 5% of the ability they use for their day to day activities. Why a 'management' position is seen as 'higher' or an evolution in my view is a relic from an industrial past. Those operating the machinery were seen as an extension to that machinery, with a per hour cost like that of the machine and an end product you can sell being produced. Those managing the machines and their operators were a step up the chain, because who wants to be the guy getting greasy and operating the knobs all day in the noisy workshop. You want to be wearing the suit and working in the nice office telling the others what to do. That used to be the hard bit. This is now on its head, with those operating the machinery needing much more skill and intellect than those organising who is doing what and when. Attitudes towards both groups of workers have yet to evolve. The 'operators' are aware this is an issue, the 'higher up' people are not.

It's hard work and it's without any thanks or recognition. Enjoy the current topsy-turvy circumstances while they are still here, don't make a move into coding!

[SandyDown]

As usual you look at the end product of a BA and think, huh I could do a word document and PP too, in 5% of the time, but they don't know what it took to get the work completed??
They don't know how much running, talking and meetings it took to extract the information get it reviewed by 20 people and changing it 50 times to keep everyone happy, before these work products are completed and handed to them on a silver plater stating every little darn thing the coders needs to do, and still they get it wrong, and constantly phone to ask questions .

Can coders sit in stakeholders' meetings and convince programme directors to adopt a strategy/methodology? can they convince them why they need to spend a few millions on making a change? Can they gain sign off from various arsehole workstream leaders based in different parts of the world, can they chase numerous people and explain over and over the necessity of resolving issues and reviewing specs?

The answer is mostly no, and that's not because they are not intelligent enough to do it, but because they can't be bothered they are way up their own arses to do it, and the end of the day who gets the visibility, who gets to be well known with top CEOs and major stakeholders?? not the coder who is sitting in a dark corner in front of his black screen thinking to himself woooooohoo am so clever I can edit XML in vi !!!


Sheesh I never really meant for this thread to be another stupid pissing match ... but hey we all got to make a living and at this moment, I fecking don't care if a coder pretend coder think they are smart cuz they spend most day trying to decipher his/her predecessor’s code ... who iffing cares as long as I get to invoice I don't care!!

[shoes]

Not in 5% of the time, using 5% of the intellectual capacity. And I don't care either, I do my time and invoice, Im not in it to win a geek contest. Im trying to point out why those developers you work with have a low opinion of you. Im also trying to help you by pointing out you have the sweetest deal - what you do is relatively easy no matter how impressive you try and make it sound, and your rates are probably higher than a coder. Enjoy it! You wouldn't want to be on the other side of the fence dealing with people like you!

[sasguru]

Most IT people have a high IQ and low EQ.
Most managers are the opposite.
I have both.
HTH

[DBA_bloke]

As usual you look at the end product of a BA and think, huh I could do a word document and PP too, in 5% of the time,

Not only could a Coder do it in 5% of the time, but it'd actually all work properly, too. Always a bonus. I've known ONE BA who knew his stuff - and he, sadly, had to go back to India. While he was with us, projects whizzed along and worked! Guess what? He was an accomplished coder, too. So there! Ha!

[OrangeHopper]

... they can't be bothered they are way up their own arses to do it ...

Careful Sandy. Bit strong that. Not everyone is eloquent and quick witted enough to do what you say you can do. I'm certainly not. I have recognised this and have therefore chosen to remain a techie. I will happily fire-fight projects but I chose not to manage. I have every respect for those that can and, at the same time, maintain the respect of the technical staff.

[DBA_bloke]

... they can't be bothered they are way up their own arses to do it ...

Careful Sandy. Bit strong that. Not everyone is eloquent and quick witted enough to do what you say you can do. I'm certainly not. I have recognised this and have therefore chosen to remain a techie. I will happily fire-fight projects but I chose not to manage. I have every respect for those that can and, at the same time, maintain the respect of the technical staff.

That was diplomatic!

[OrangeHopper]

That was diplomatic!

Obviously shouldn't be a code monkey.

Now, where is my arse?

[Churchill]

Obviously shouldn't be a code monkey.

Now, where is my arse?

It won't be difficult to find, it resembling a baboons.