The article explains how ordinary programmers differ from architects in thinking patterns, decision making, abstraction, global perspective, communication, and continuous learning, and offers practical steps to bridge the gap and develop the mindset needed for architectural roles.
This article explores what a software architect does, the different levels of architecture, essential daily activities, key skills such as design, decision‑making, communication, estimation, and marketing, and offers practical advice on continuous learning, documentation, and influencing stakeholders.
This article provides a comprehensive guide to software architecture, detailing the three architecture levels, daily activities, ten essential skills, decision‑making techniques, communication strategies, documentation practices, and ways to balance quality, cost, and time while fostering continuous learning and community involvement.
This article outlines the role of a software architect, describing the different architectural levels, daily activities, essential skills such as design, decision‑making, communication, documentation, estimation, and how to balance technical and non‑technical responsibilities for effective system design.
Becoming a software architect requires mastering technical design, decision‑making, documentation, communication, estimation, and balancing trade‑offs across application, solution, and enterprise levels, while continuously learning new technologies, fostering community, and applying proven practices such as design patterns, quality metrics, and effective stakeholder engagement.
This article outlines the essential definitions, hierarchical layers, daily responsibilities, and ten core competencies—including design, decision‑making, simplification, programming, and documentation—that aspiring software architects need to master to advance from application‑level to enterprise‑level architecture.
This article explains what a software architect does, outlines the three levels of architecture, lists daily activities and ten essential skills—including design, decision‑making, communication, documentation, estimation, and marketing—while offering practical advice on design patterns, quality metrics, technology experimentation, documentation automation, conflict resolution, and influencing stakeholders.
The article shares a senior Alibaba engineer’s reflections on system architecture design, the evolving role of architects, essential skills such as problem discovery, definition and solution, and how continuous learning, technical breadth, and business understanding enable architects to tackle complex, high‑scale challenges like Double 11.
This article explores what a software architect does, defines the role, outlines three architectural levels, details daily responsibilities, and breaks down ten essential skills—including design, decision‑making, simplification, programming, and documentation—to help engineers become better architects.
