Wanna be anArchitect?

Imagine. Invent. Involve.

henryjacob.com

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

Do we needArchitects?

DIY

Team

Engineer

Why we needArchitects?

Design Decisions

Design Decisions

Software development is almost like building one of these buildings

Different ProblemsUnique SolutionsRight Design Decisions

What kind of

Design Decisionsinvolved 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 DesignApplication FrameworkDomain 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 Architectdecides “what to build”

CustomerUserBusiness AnalystUI DesignerProgrammer

are not very effective in deciding “what to build”

Customer

UserBusinessAnalyst/Subject Expert

UI/GraphicsDesigner

Programmer

TechnicalArchitect

InfrastructureArchitect

Manager

Someone to connect, every views

VisionarySee the future beyond the problem boundaries Visualise the solutions Versatilistsable to apply a depth of skill to a progressively widening scope of situations and experiencesAppreciate BeautyDesign Trends, Colors, Experience, Look and FeelBusiness Side of TechnologiesBusiness benefits, ROIInnovator New line of thinking, Beyond the technical limitations

Technical Architect

Technical Architectdecides “how to build”

Perception of management

Reality of software development

We need true leaders, to be in the field

Guruwho has authority because of his or her perceived knowledge or skillsTechnology evangelistwho enthusiastically promotes or supports technology Pragmatic ProgrammerEarly adopter / fast adapter, Inquisitive, Critical Thinker, Realistic, Care About Your Craft LeaderLead by example, Take responsibility, Care and protect their team, Mentor, Courage

InfrastructureArchitect

Infrastructure Architectdecides “how to scale”

How to become anArchitect?

How to become aSuperstar?

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 FundamentalsJava/C#/HTML/SQL/JavaScript/Simple Programs

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

More coding/more projectsCode Quality/Less Defects

Start feeling the designNot 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 technologyRead Books/Write Articles/Blog/Learn New

Frameworks/New Languages on your own/Appreciate Good Design/ Attend Conferences/Speak/

Become an evangelist

http://www.henryjacob.com/2005/04/am_i_a_rare_int.htmlhttp://www.henryjacob.com/2005/12/wanna_be_a_solu.html

What to read? Which technology to learn?Where is time?

Start creating your ownFramework/Architecture/Language/Book

Architect

Is it worth theEffort?

Is it worth theEffort?

karma

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

Imagine. Invent. Involve.

henryjacob.com

www.designdrivendevelopment.org