I wouldn’t say my article has even covered the role of an architect as I’m currently a touch too inexperienced to assume that role. That said, I have to disagree with the sentiment that developers below an architect or lead level should not be asking questions regarding the approach and technological solution to a problem.

Each developer, through a combination of personal interests and experience, will have consequently gained knowledge of certain esoteric areas of their domain; this information, as well as one’s more general skills, is important when making a decision or shaping a project.

Of course, architects and leads find themselves within the most knowledgable and experienced echelons of our industry, but it’s impossible that they know everything, thus acknowledging the opinions of most skill levels will close these gaps and result in a potentially sounder solution.

The worst case scenario will be that a suggestion is not applicable or that this has already been considered by the lead; if a potential hinderance could be avoided due to another thought, then I’m willing to incur that cost.

It’s important that everyone works towards the vision of the architect or lead in order to deliver high-quality software, but that vision needs to result from some collaboration. If I wanted to have my work dictated to me without any intelligent thought, then I wouldn’t have become a developer.

Perhaps our experience is different; I’d love to work in a startup but I’ve only found myself in larger organisations thus far. Nonetheless, ruling with an iron fist results in a reduced pool of information and even demotivation.

Thanks for your feedback. I love that quote at the end; I can attest to that!