permaculture playing cards*
The moose likes Design and the fly likes Software Architecture for Developers - Question Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Design
Bookmark "Software Architecture for Developers - Question" Watch "Software Architecture for Developers - Question" New topic
Author

Software Architecture for Developers - Question

Paulo Rezende
Ranch Hand

Joined: May 13, 2008
Posts: 33

Simon,

Why so many senior developers think that being a senior developer is enough for a self-proclaiming as software architect?


SCJP, SCWCD, OCBCD
Junilu Lacar
Bartender

Joined: Feb 26, 2001
Posts: 4462
    
    6

Paulo Rezende wrote:Why so many senior developers think that being a senior developer is enough for a self-proclaiming as software architect?

Seems like there's quite a bit of cynicism in that question... On the other hand, if someone has a title of "senior developer" and they actually do the kind of work that an architect should/would do, does that mean that they're not doing "architecture"?


Junilu - [How to Ask Questions] [How to Answer Questions]
Paulo Rezende
Ranch Hand

Joined: May 13, 2008
Posts: 33

Junilu,

There's no cynicism in my question. There's criticism, a strong and deep criticism.

Answer your question: A senior developer doing what an architect do, is doing - for sure - architecture.

My problem is: doing architecture is not writting code. You cannot get a developer who knows a lot of software development and make him architect a software without knowing anything about software architecture. Development is one "science", architecture is another one. Each one demans different kind of knowledge.

I hope I explained myself despite my poor english :-)
Junilu Lacar
Bartender

Joined: Feb 26, 2001
Posts: 4462
    
    6

Paulo Rezende wrote:There's no cynicism in my question. There's criticism, a strong and deep criticism.

Cynicism - An attitude of scornful or jaded negativity, especially a general distrust of the integrity or professed motives of others

Sorry, but the phrase "self-proclaiming as software architect" is loaded with it "scorn, negativity, and distrust of integrity" and your intended criticism of anyone acting that way is only off-handed/implied.

My problem is: doing architecture is not writting code. You cannot get a developer who knows a lot of software development and make him architect a software without knowing anything about software architecture. Development is one "science", architecture is another one. Each one demans different kind of knowledge.


Again, I must go back to my martial arts analogies. You can't swing a sword a thousand times without implicitly learning how to do it properly. Swinging the sword ten or twenty times may not give you any insights into proper sword handling but a normal person just can't complete thousands of sword swings without learning how to do it efficiently. By the same token, a *good* software developer who has "lots of development" cannot write *good* software without also gaining some insight about good architecture practices. The line between development and architecture is just not as clearly drawn as you represent it to be. Sure, there are lousy developers out there who, solely by virtue of their "length of experience," arrogantly declare that they are also qualified to "architect" but that shouldn't cloud your judgement or opinion of others who are not of the same ilk. Not all developers with good, solid experience are like that and many do deserve to be recognized as architects, despite their actual titles.
Paulo Rezende
Ranch Hand

Joined: May 13, 2008
Posts: 33

Let me clarify something. Sometimes people do wrong thing just because they are unconscious that it's wrong. Someone can self-proclaim himself a software architect without having specific and necessary skills, experience or knowledge without being a necessarily a malevolent person. Sometimes people just make mistake.

But... I don't care too much about titles, maybe you Junilu also do not care, but a lot of people care. Most of people care. For a lot of possible reasons.

Maybe a person can think: "Oh my god, I've been called 'developer' for the last ten years. I need a new title." Why? A doctor is called doctor for the whole life and he is proud of it.

Maybe a person wish to feel more important or wish to earn more and thinks that the way is to change from developer to architect. It's not really necessary. Make your self a better developer, learn a new foreign language, learn a new programming language, keep up-to-date, there are lots of ways of become more important or earn more as a developer.

Finishing my point. It doesn't matter if you got your Skills-Experience-Knowledge about software architecture via an academic-formal way or a self-learning-empirical way. It's the same. It doesn't matter if you're called this or that by others. But, please, just stop a minute before call yourself a software architect and ask for yourself the question: Do I really have S-E-K about software architecture or are my S-E-K about software development?
 
 
subject: Software Architecture for Developers - Question