• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • Ron McLeod
  • Carey Brown
Bartenders:
  • Paweł Baczyński
  • Piet Souris
  • Vijitha Kumara

Journey to Enterprise Agility: Architects

 
Marshal
Posts: 14351
238
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello authors and welcome!

I noticed the book has a section about architects and the sub-heading "Architects Who Write Code." Can you give a summary of what this section is about? I'm hoping that your recommendation is that architects should code, at least enough to know how their visions are actually being realized in code. I know a group from one company I worked for that required their architects to code and that resulted in all kinds of Good Things™.

I know there are many pros to it but are there any cons about architects coding that you can point out? What other things should architects in agile organizations do that they don't normally aren't expected to do in more traditional organizations?
 
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Junilu,

Hi!  Yes, you are right, we are advocating "architects who code."  In our experiences, we've too often seen the "PowerPoint architect" who has a great ability to create architectural visions and lovely-looking diagrams, but doesn't have any appreciation for what developers really need, nor what is practical.  Then these "visions" get crammed down people's throats and we have a mess.  CORBA, data warehouses, SOA - there are so many examples of misusing these technologies in a "too big" way.

However, architects who *can* code and who also *do* code, in guest spots on teams, etc. are really valuable.  Now you have someone who has a bigger picture view, but who also has to live with their own decisions in the depths of the code. Even better, limit the number of enterprise architects in the company and allow the teams to make decisions together about standards and architectures, etc.

Daryl
 
Ranch Hand
Posts: 75
1
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I agree with both of you.

I think that, not matter of Agile or any old-fashion development process, Architecs should know how to code. The better they know the pipes and tools of everyday developers, the better architectures, standards and leadership the architect will develop.
 
There is no beard big enough to make me comfortable enough with my masculinity to wear pink. Tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!