Link Details

Link 970699 thumbnail
User 298543 avatar

By joselopescruz
via blog.josedacruz.com
Published: May 20 2013 / 08:27

Why there are very few good Java Architects? Well, most people will say to me, that this isn’t true, they have Java Architects in their team. I believe, but most of them are Senior Programming Developers with some experience, but not real Architects! Sorry.
  • 5
  • 3
  • 1449
  • 1154

Comments

Add your comment
User 388907 avatar

MCII replied ago:

0 votes Vote down Vote up Reply

He is a "J2EE trainer". J2EE was superseded by Java EE in 2006.

User 161039 avatar

mheath replied ago:

3 votes Vote down Vote up Reply

The bigger problem is that there's not one true definition of what an architect is or does. If you took 10 architects from 10 different organizations and asked them what they do, you'd get 10 different answers. So, fundamentally, to say someone is not an architect and is really a senior engineer is a bit absurd to me.

User 298543 avatar

joselopescruz replied ago:

0 votes Vote down Vote up Reply

Well, there isn't a definition of what an Architect is but we could try to enumerate some of the actions and responsibilities we expect from an architect: - Management and technology responsibilities, with the goal of turning a business problem into a technical solution - Address quality requirements - Mitigate risks of the product - Making trade-off decisions considering the Quality-of-Service (Only a person with a business/technical/management vision can really do it) - Identifying the most important use cases - Work closely with project manager and the sponsor of the project (a commercial director for instance) - Recommend the technologies and possible framework to be used in the project. - Developing and guiding the construction of a prototype fo the project - Understanding the cost associated with architectural decisions (mainly technical) - Managing the communication between manager/project manager and the team (including senior developers) - Mentoring team members - Convincing stakeholders and reach agreements with them considering the risks, tradeoffs, etc. This list can go on and on, but he the big difference its related with the business understanding the architect has that most of senior developers don't have it. I have worked with architects in the past, and long time ago, one of them asked me some questions, and one of them was: "Do you know how much it costs for the customer the decisions you are taking developing this framework instead of using another?". And then he told me: "Every technical decision has a cost associated, do you know how to calculate it, or have and idea about it?". These questions are from an architect, not from a senior developer.

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.

Voters For This Link (5)



Voters Against This Link (3)



Play Framework
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Akka
  2. Design Patterns
  3. OO JS
  4. Cont. Delivery
  5. HTML5 Mobile
  1. Akka
  2. JUnit/EasyMock
  3. Java Performance
  4. REST
  5. Java