ziffusion

I fully get that a lot of less experienced software engineers are likely extremely smart and capable. So no offense intended.

Some of you may agree that some of the more subtle nuances of software architecture, structure and development take some time to get a handle on.

Given that, how do you best utilize inexperienced software engineers? How do you control architecture, structure and software quality without stifling individual creativeness or creating a perception of oppressiveness?

How do you guys pull off your magic as team leaders and managers?

I got burnt really badly on a recent gig because I couldn't manage up too well.

It turned out that my manager (and up) had very little insight into software concepts and software development process.

They seemed happy to see all the architecture and design details we shared with them. But their trust and confidence didn't come from actual comprehension of these. Minute anything went off track a bit, they would start to question everything. They would want to change tracks and change people. Needless to say this was VERY disruptive and wasted a lot of time and energy over and over again.

What are some of your war stories? How do you handle this?

It can become very hard to converge with such a person. They may argue too much for ideas that are not that good. They may not understand the alternatives too well. Their scope of knowledge may be limited.

Trying to converge "politely" can take way too long. And even so, they may end up accepting the alternatives grudgingly.

Just in case I sound condescending - I realize that in some contexts I myself may be this person.

How do you folks handle this?