Wanna Be An Architect?

Slide 1: Wanna be an Architect?

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

Slide 3: Do we need Architects?

Slide 5: DIY

Slide 7: Team

Slide 9: Engineer

Slide 12: Why we need Architects?

Slide 13: Design Decisions

Slide 14: Design Decisions

Slide 15: Software development is almost like building one of these buildings

Slide 16: Different Problems Unique Solutions Right Design Decisions

Slide 17: What kind of Design Decisions involved in Software Development?

Slide 18: What to build?

Slide 19: How to build?

Slide 20: How to scale?

Slide 21: What to build? Solution Design

Slide 22: How to build? Technical Design

Slide 23: How to build? Technical Design Application Framework Domain Modelling

Slide 24: How to scale? Infrastructure Design

Slide 25: These design areas were so diversified

Slide 26: that no single person can take all these design decisions

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

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

Slide 29: Solutions Architect

Slide 30: Solutions Architect decides “what to build”

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

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

Slide 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

Slide 34: Technical Architect

Slide 35: Technical Architect decides “how to build”

Slide 36: Perception of management

Slide 37: Reality of software development

Slide 38: We need true leaders, to be in the field

Slide 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

Slide 40: Infrastructure Architect

Slide 41: Infrastructure Architect decides “how to scale”

Slide 42: How to become an Architect?

Slide 43: How to become a Superstar?

Slide 45: Learn Fundamentals

Slide 46: Start playing/Follow the books

Slide 47: More songs/More practice

Slide 48: Start feeling the music

Slide 49: Passion for music/Play on your own

Slide 50: Start creating your own music

Slide 51: superstar

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

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

Slide 54: More coding/more projects Code Quality/Less Defects

Slide 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

Slide 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

Slide 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

Slide 58: Start creating your own Framework/Architecture/Language/Book

Slide 59: Architect

Slide 60: Is it worth the Effort?

Slide 63: Is it worth the Effort?

Slide 64: karma

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

Slide 66: henryjacob.com Imagine. Invent. Involve.

Slide 67: www.designdrivendevelopment.org