Here is my answer for everyone, who is interested in becoming an Architect.

1. Wanna be an
Architect?

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

3. Do we need
Architects?

5. DIY

7. Team

9. Engineer

12. Why we need
Architects?

13. Design Decisions

14. Design Decisions

15. Software development is almost
like building one of these
buildings

16. Different Problems
Unique Solutions
Right Design Decisions

17. What kind of
Design Decisions
involved in Software
Development?

18. What to build?

19. How to build?

20. How to scale?

21. What to build?
Solution Design

22. How to build?
Technical Design

23. How to build?
Technical Design
Application Framework
Domain Modelling

24. How to scale?
Infrastructure Design

25. These design areas
were so diversified

26. that no single person
can take all these
design decisions

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

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

29. Solutions
Architect

30. Solutions
Architect
decides “what to build”

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

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

33. 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

34. Technical
Architect

35. Technical
Architect
decides “how to build”

36. Perception of management

37. Reality of software development

38. We need true leaders,
to be in the field

39. 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

40. Infrastructure
Architect

41. Infrastructure
Architect
decides “how to scale”

42. How to become an
Architect?

43. How to become a
Superstar?

45. Learn Fundamentals

46. Start playing/Follow the books

47. More songs/More practice

48. Start feeling the music

49. Passion for music/Play on your own

50. Start creating your own music

51. superstar

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

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

54. More coding/more projects
Code Quality/Less Defects

55. 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

56. 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

57. 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

58. Start creating your own
Framework/Architecture/Language/Book

59. Architect

60. Is it worth the
Effort?

63. Is it worth the
Effort?

64. karma

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

66. henryjacob.com
Imagine. Invent. Involve.

67. www.designdrivendevelopment.org