Path to being a software architect

SlinkyMike said:
ARIS has long been a popular choice, I haven't used it in years but as always the tool is less important than he methodology.

Know TOGAF, the tool is incidental.
Click to expand...
TOGAF is for Enterprise Architecture though, or am I mistaken?

Either way, like Mesugga said: Enterprise Architect and Software/System Architect is not the same role, not even close.
 
Hamster said:
TOGAF is for Enterprise Architecture though, or am I mistaken?

Either way, like Mesugga said: Enterprise Architect and Software/System Architect is not the same role, not even close.
Click to expand...
No, I see that it is a "requirement" for solution design, enterprise and data architects.
 
CamiKaze said:
No, I see that it is a "requirement" for solution design, enterprise and data architects.
Click to expand...

That's the whole definition problem. Those guys do very little, if anything to do with code. They draw diagrams describing how systems integrate with each other and what functions they perform, combining to make up a solution.
 
Messugga said:
That's the whole definition problem. Those guys do very little, if anything to do with code. They draw diagrams describing how systems integrate with each other and what functions they perform, combining to make up a solution.
Click to expand...
Well If that's what they get paid for then that's what they get paid for.

Others get exploited for a lower salary where people writing a spec sheet get paid handsomely.
 
The only thing that gets exploited is the title of "architect"
 
Does anyone other than HR and employment agencies take titles seriously?
 
Hamster said:
TOGAF is for Enterprise Architecture though, or am I mistaken?

Either way, like Mesugga said: Enterprise Architect and Software/System Architect is not the same role, not even close.
Click to expand...

To be pedantic, TOGAF is a framework that one can become certified in.

For BAs there is BABOK. For PMs there is Prince2.

In all cases it'll get you an interview if that's on your CV but day to day effectiveness is down to your actual capabilities.

I'm getting very confused by the various acronyms and titles in this thread if I'm honest, so for clarity: I'm talking about 'Solution Architect' the linked article includes a section differentiating the role from Enterprise Architect.

To get back to your is TOGAF for EA question: IMO yes but Solution Architects must operate withihn the framework so it's for both really.

This is an interesting discussion, I hope some folks are getting value from it.
 
Last edited:
CamiKaze said:
Titles are linked to a salary range, so yeah.
Click to expand...

Only in banks (corporates) and one dev shop in Johannesburg (who got booted out of a bank project because their definition of a "senior developer" is something very different to the rest of the world).

Most dev shops and smaller companies, in my experience at least, don't care much for the titles internally.
 
Hamster said:
Only in banks (corporates) and one dev shop in Johannesburg (who got booted out of a bank project because their definition of a "senior developer" is something very different to the rest of the world).

Most dev shops and smaller companies, in my experience at least, don't care much for the titles internally.
Click to expand...

Is there a thread on this somewhere, who is this?
 
Hamster said:
Only in banks (corporates) and one dev shop in Johannesburg (who got booted out of a bank project because their definition of a "senior developer" is something very different to the rest of the world).
Click to expand...

Promote Junior/Intermediate.. claim they are senior to rake in R1k p/h consulting fee's.
Profit :p
 
evilskaap said:
Is there a thread on this somewhere, who is this?
Click to expand...

No thread specifically about this, no. And three years is a long time so things may have changed and therefore I'm not mentioning names...again. Last time I did that their MD climbed onto the forum :p

Point is: some companies do care about titles.
 
Hamster said:
Only in banks (corporates) and one dev shop in Johannesburg (who got booted out of a bank project because their definition of a "senior developer" is something very different to the rest of the world).

Most dev shops and smaller companies, in my experience at least, don't care much for the titles internally.
Click to expand...

The smaller companies that don't care usually expect you to do far more than what you ordinarily would. So having a clearly defined role isn't always a bad thing. If you want to take on further responsibilities to further your career, you still can. But it shouldn't be pushed on you.

Also, at some point people may want to start moving away from the grunt work (coding, analysis etc.), and start becoming more involved in the core business, especially as you get older. Architecture allows you to move in that direction...
 
I've had the "architect" title for about 7 years now. For me it means that I am responsible for the design of a few large pieces of software, and that I am also the guy who works through feature priorities with the consumers of my product. Since I am also a user of my product, I also contribute feature requests to the feature set. I also consult on the technical direction of the company, and it's overall technology strategy. I still spend 80% of my time coding - about 60% of my code is directly for the above mentioned projects, and the other 40% is quantitative coding/research (basically, interactive coding for data analysis).
 
Yeah I've been a junior dev doing junior and intermediate work, an intermediate doing intermediate and senior work, a senior dev doing architect work, an architect doing architect and management work. Titles are meaningless. What you can do and how you can contribute is all that matters.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X