Our focus is to help developers become successful architects (T-shaped knowledge) and if you are already an architect, provide a platform to share your learnings, tips & tricks, practices, and knowledge.

Each developer would aspire to become an architect in due course & find the path to be very challenging at times. Some people get guidance from their mentors & few learn it through training/certification, reading, social media, blogs etc.

We define AJP (Architect¬†Journey Path) for a developer so that you don’t get lost in the process & achieve your goal to be a successful architect.

Developer to Architect

Architect’s Journey

RoleResponsibilities & Skill-set
DeveloperCoding, Rule Compliance, Unit Testing, Integration Testing, Refactoring, Design Patterns Implementation, Performance Optimizations, Security Fixes
Technical LeadDevelopment Skill-set Plus   Design Patterns, Anti-patterns, Refactoring, Reviews, Performance & Security Testing/Fixes, Design/Architecture Components
Technical ArchitectTechnical Lead Skill-set Plus   Architectural Patterns, Design/Architecture Creation, Specific Technology Artifacts such as data, security, information, UML, Broader Technology Knowledge (Build & Release, DevOps, Deployment Topologies, Cloud Technologies)
Solution ArchitectSolution Mapping to Specific Technology, Impact Analysis, ROI of Technology Decisions, Broader Solution Knowledge (COTS vs. OpenSource, Solution Comparison & Recommendation)
Enterprise ArchitectAll the above plus   Enterprise framework knowledge (e.g. TOGAF), Architectural Patterns, Architecture Evaluation Skills, Roadmap Planning, Technology Vision, Future State Architecture, Gap Analysis, Stakeholder Management (Business & Key Technical)