The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
Yeah, worked out the anagram but referred to a song called Amaranth by one of my favourite bands which I vaguely recalled meant undying flower. I just added the 'ine' to the end as a typical chemical name.
Then... I cheated slightly by looking it up to check about the purple / red colour bit before posting.
We had an kickoff meeting regarding a new software development,
Requirement was locked in ( at least on paper) and the meeting was called in to come with some concrete architecture.
It was chaired by one of our Legend Architect.
As the meeting started, it turned into a brainstorming among developers and he being just silent. Finally we zeroed on a architecture and we all felt it is the best considering all the constrains.
The "legend" said "Good, Put this on paper and lets start fine tuning among with various stake holders" That's was his only statement till now and he contributed nothing else.One Dev made a snide remark, saying why was he there and earn so much when he did not even come with the architecture which he was supposed to.
He replied, " I am paid to cover your A$$ when sh1T hits the fan and to clean the mess. Also If I come and trust an architecture on you, you would be going multiple rounds objecting it. The best solution is always when it comes from you rather than someone else telling what/How you should do.
Too much of good is bad,mix some evil in it
Sounds like basic leadership to me... let the people who will do the work brainstorm it. If you see any major issues help guide them, else sit back, observe, see who is the major contributor, who is the greatest roadblock, etc...
Sounds like a seasoned veteran who knows his stuff. Also, he seems to know how to get the junior developers participating to help them learn. One of my great mentors taught me a great lesson: "teach the juniors to replace you".
Much easier to get buy-in for a idea from the consumers of a thing rather than forming the consumers around an idea of buying in. The former almost always will result in the fewest rebels to the process while the latter is almost always going to produce the greatest rebellion.
One Dev made a snide remark, saying why was he there and earn so much when he did not even come with the architecture which he was supposed to
Well, well! What I've found being in IT for almost 30 years is that comments like this, though considered bold and edgy at the time (making you a hero among your peers!), they ultimately work against you. You will never know when the people in position above you make an offhand remark, good or bad, to the CIO or an VP about you. They might say they'll cover your @$$ when it hits, but don't count on it. Negative things will happen to you and you'll never even know they happened.
If you are tight with the Architect, troll away. If not, suppress the urge to say what you're thinking.
With that said, my Dad gave me this advice. He was an Engineer at International Harvester for 30 years. He spoke his mind many times and he knows he was held back because of it. It happens. Understand your risks.
Last Visit: 31-Dec-99 18:00 Last Update: 23-Aug-17 17:10