Wanna be an
Architect?

henryjacob.com
Imagine. Invent. Involve.
Original post: http://www.henryjacob.com/2005/12/wanna_be_a_solu.html

Do we need
Architects?

DIY

Team

Engineer

Why we need
Architects?

Design Decisions

Design Decisions

Software development is almost
like building one of these
buildings

Different Problems
Unique Solutions
Right Design Decisions

What kind of
Design Decisions
involved in Software
Development?

What to build?

How to build?

How to scale?

What to build?
Solution Design

How to build?
Technical Design

How to build?
Technical Design
Application Framework
Domain Modelling

How to scale?
Infrastructure Design

These design areas
were so diversified

that no single person
can take all these
design decisions

Each of these design
areas demands new
set of
Skills.
Experience.
Expertise.
Knowledge.
Leadership.

Depending on the decisions
they make, architects can be
grouped into following roles
Solutions Architect.
Technical Architect.
Infrastructure Architect.

Solutions
Architect

Solutions
Architect
decides “what to build”

Customer
User
Business Analyst
UI Designer
Programmer
are not very effective in
deciding “what to build”

User
Business
Customer Analyst/
Subject
Expert
Programmer UI/Graphics
Designer
Technical
Architect Manager
Someone to connect, every views
Infrastructure
Architect

Visionary
See the future beyond the
problem boundaries
Visualise the solutions
Versatilists
able to apply a depth of skill to a
progressively widening scope of
situations and experiences
Appreciate Beauty
Design Trends, Colors,
Experience, Look and Feel
Business Side of Technologies
Business benefits, ROI
Innovator
New line of thinking, Beyond the
technical limitations

Technical
Architect

Technical
Architect
decides “how to build”

Perception of management

Reality of software development

We need true leaders,
to be in the field

Guru
who has authority because of his
or her perceived knowledge or
skills
Technology evangelist
who enthusiastically promotes
or supports technology
Pragmatic Programmer
Early adopter / fast adapter,
Inquisitive, Critical Thinker,
Realistic, Care About Your Craft
Leader
Lead by example, Take
responsibility, Care and protect
their team, Mentor, Courage

Infrastructure
Architect

Infrastructure
Architect
decides “how to scale”

How to become an
Architect?

How to become a
Superstar?

Learn Fundamentals

Start playing/Follow the books

More songs/More practice

Start feeling the music

Passion for music/Play on your own

Start creating your own music

superstar

Learn Fundamentals
Java/C#/HTML/SQL/JavaScript/Simple Programs

Start coding/with Google’s support
Defects/More Defects/Less Quality

More coding/more projects
Code Quality/Less Defects

Start feeling the design
Not just write/start thinking in code/you also know
what happens inside a framework/start understanding
framework/design pattern/resolve issues/debug
fast/noticed

Passion for technology
Read Books/Write Articles/Blog/Learn New
Frameworks/New Languages on your own/Appreciate
Good Design/ Attend Conferences/Speak/
Become an evangelist

What to read? Which
technology to learn?
Where is time?
http://www.henryjacob.com/2005/12/wanna_be_a_solu.html
http://www.henryjacob.com/2005/04/am_i_a_rare_int.html

Start creating your own
Framework/Architecture/Language/Book

Architect

Is it worth the
Effort?

Is it worth the
Effort?

karma

Karma =
You don’t have an option,
stupid. Just do, otherwise
you will not survive.

henryjacob.com
Imagine. Invent. Involve.

www.designdrivendevelopment.org