By raykoz
via kingtaipan.blogspot.com
Published: Jul 09 2007 / 02:58
There seem to be more and more confusion over the role of a Software Architect, it seems the definition can change day to day from person to person. So what I am going attempt to do in this posting and some followup posting is define what I believe the role is from my own experience and research.
To kick things off I have to say that 70% of the 'Architects' I have met should not have the title, they are doing things in which they have no interest or skill, a better title for some of these folks would be 'fellow software engineer', or just 'Red Hot Developer'.
-
Morph Labs Expands Its Cloud Services to Support PHP Applications
-
MythBusting — Rails is not a monolith
-
Getting Started with 3D in Flash
-
Reactive programming (I.) - First class events in F#
-
Microsoft vs. Google Web-based office battle heats up again
-
Repetitive Calls to Find the Same Element Using document.getElementById and Performance
Comments
nothingHappens replied ago:
I seriously don't get it. Sounds like just a lot of architecture-astronaut smoke-and-mirrors talk. I mean seriously, what the fuck is "it is a quadratic equation with concepts and many shades of gray" supposed to mean? Voted down as useless. The site says "fresh links for DEVELOPERS" not "fresh links for management-speak-spewing tools"
Voters For This Link (17)
Voters Against This Link (1)