«« Next » « Previous
«« Next » « Previous

Link Details

Link 88784 thumbnail
User 220691 avatar

By ph111
via buunguyen.net
Published: Jun 20 2008 / 14:33

Description of the 5 types of software architects you feel lucky to NOT to work with.
  • 22
  • 6
  • 2482
  • 1328

Comments

Add your comment
User 282119 avatar

Rob Signorelli replied ago:

3 votes Vote down Vote up Reply

To defend the no-news-is-good-news architect, what's wrong with a proven solution that works? I'll take a developer who can provide a solid, maintainable solution that meets all of the problem space's requirements over someone who's eager to throw the "next big technology" at a problem just because it's newer. Also the reason someone is probably criticizing the no-news guy is because he's a nothing-but-nails guy eager to utilize the technology he's comfortable with anyway. Sorry but re-architecting just for the hell of it seems silly if what you've got serves your needs. Most shops don't have the time to jump from java to ruby/rails to python/django just because it's available. To use the old cliche, if it ain't broke don't fix it and in almost all cases over-engineering is bad.

User 286809 avatar

damber replied ago:

1 votes Vote down Vote up Reply


What's amusing is that most people that moan like this aren't and have never been architects, but given the chance they would jump at it. It's additionally sad how most people don't understand the difference between an Enterprise Architect, Solution Architect, Application/Software Architect and Technical Architect (not to mention the variations on those themes). Developers love to hate Architects because it's someone to take away the 'fun' part of designing a solution - or if things don't work out, someone to blame for not being hands on enough.

Don't get me wrong, there are lot's of useless architects that have no business doing that job, but careful how big you make that brush......

User 283139 avatar

ceaseoleo replied ago:

0 votes Vote down Vote up Reply

what this guy doesn't understand, that if the architect makes the wrong decisions , he's responsible. Just as Blaine Cook of twitter. What this guy doesn't write is what is the ideal architect. I guess from his description he would be describing the philosopher king from plato.
,

User 287218 avatar

sarajo replied ago:

1 votes Vote down Vote up Reply

I liked this article actually. I have seen the same symptoms in "Architects" and developers that are architecting systems. I guess the moral of the story is we need to keep an open mind to all these things and find a balance between them. There is nothing wrong with some of these things in moderation, however, I believe the author was trying to say that extreme polarization of these things leads to bad software.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.