The article introduces the Goudison Theorem, emphasizing that newly promoted technical leaders should avoid overworking themselves, delegate effectively, empower their teams, and focus on sustainable management practices to build high‑performance groups.
The article explains the distinction between part‑time and full‑time software architects, outlines the core responsibilities such as global technical planning, unified methods and standards, robust foundational construction, and practical implementation, and discusses the rights, assessment criteria, and practical ideas for establishing an effective architecture function within large organizations.
The article shares practical insights on the role of a technical leader, outlines a streamlined R&D workflow and team responsibilities for fast‑moving startups, and discusses technology selection, architecture components, and management practices to help early‑stage companies build effective engineering teams.
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.
This autobiographical article chronicles the author's journey from a struggling high‑school student with poor English scores to a senior software architect at Motorola, highlighting 24 practical career insights on self‑learning, perseverance, technical depth, documentation, and leadership across embedded, networking, and middleware development.
In this comprehensive talk, a veteran tech leader shares how to design technical leadership, create a top‑level framework, foster self‑driven teams, translate strategy into execution, productize technology, and implement talent‑focused management practices to grow a research and development organization from a few hundred to thousands of engineers while aligning with corporate strategic goals.
This article explains why engineers need business sense, defines the concept, shares product and engineering perspectives, outlines common pitfalls, and offers practical steps and real‑world examples for engineers to better understand and influence business outcomes.
The article explores how senior technical managers, from directors to CTOs, need deep technical detail awareness to succeed in fast‑growing companies, illustrating the pitfalls of neglecting details through personal anecdotes, hiring experiences, and practical advice on team structure and leadership.
The article examines the evolving technical leadership needs of a fast‑growing beauty social‑ecommerce startup, contrasting the roles of senior developer, technical manager, technical director, architect and CTO, and explains why a founder may actually need a technical manager rather than a CTO at early stages.
The article explains what a software architect does, outlines their responsibilities such as architecture design, technology selection, managing non‑functional requirements, solving technical challenges, and guiding teams, describes different types of architects, and offers advice on the skills and experience needed to become one.
Becoming a software architect requires more than high‑concurrency knowledge; it demands comprehensive abilities such as requirement analysis, system decomposition, technology selection, design, communication, and leadership across all development phases, balancing business understanding with technical expertise to deliver effective architectural solutions.
The article explains why pure coding expertise alone doesn’t make a top‑level architect, emphasizing hands‑on experience, forward‑looking design, product awareness, domain modeling, deep technical foundations, and high‑availability practices as essential for evolving robust software systems.
A reflective essay explores how a tech professional’s neglect of technical depth, hiring practices, and management details can derail careers, illustrated through personal anecdotes, headhunter experiences, and real‑world examples of directors and VPs struggling without solid technical foundations.
In a 2019 GTLC Beijing talk, Zhang Chu, Vice President of Technology at Mafengwo, explains why measuring engineers is essential, outlines five dimensions of their work, warns against common metric pitfalls, and shares practical frameworks like OGSM and OKR to create goal‑focused, balanced performance evaluations.
The article presents a step‑by‑step roadmap guiding software engineers from junior coding roles through senior engineering and technical expertise to junior, mid‑level, and senior architect positions, emphasizing mentorship, systematic study, deep experience, and the three core architect skills—judgment, execution, and innovation—underpinned by the 10,000‑hour practice rule.
This article outlines the philosophical mindset, career stages, essential knowledge, and practical habits needed to evolve from a junior programmer to a senior architect, offering concrete steps, role responsibilities, and advice on continuous learning and effective time management.
A software architect must combine strong technical expertise, deep business understanding, forward‑looking design, broad knowledge, effective communication, and systematic thinking to translate business needs into reliable, scalable systems that drive a company's success.
This article explores the definition, duties, and career development of software architects, covering their role in different company stages, system decomposition, technical selection, team collaboration, various architect specializations, essential skills, and practical advice for advancing in the field.
This article shares Alibaba infrastructure leader Bi Xuan’s reflections on how broadening technical breadth, choosing depth, and aligning personal interests with business or foundational paths shape a software engineer’s growth, leadership potential, and long‑term career success.
Software architecture defines the overall structure and components of a system, guiding design decisions, balancing performance, scalability, and maintainability, while fostering team alignment through clear standards and abstractions, and the article outlines its purpose, best practices, evaluation criteria, and a path to becoming an architect.
This article shares practical insights from a Tech Connect keynote on how technical leaders can understand developer psychology, avoid conventional management pitfalls, bridge decision‑consequence gaps, and foster a culture that empowers engineers to deliver high‑quality software while meeting business goals.
This article shares practical guidance for front‑end team leaders on identifying team characteristics, uncovering planning clues, focusing on value, and executing long‑term roadmaps, while also addressing upward management, brainstorming, and effective PR for technical teams.
This article shares practical leadership lessons from a keynote delivered to over 3,000 tech decision‑makers, focusing on developers' psychology, the shortcomings of traditional management, and actionable ways to inspire high‑quality software teams.
This article explores the seven core competencies—technical expertise, abstraction, design foresight, systematic thinking, problem‑solving depth, cross‑domain knowledge, and communication—that distinguish a successful software architect and guide how to develop them.
This article explores the role of software architects, outlining their responsibilities, essential qualities, differences between internet and traditional enterprises, team dynamics, common optimization practices, and practical advice on growing into an architect and advancing your career.
Transitioning from an individual contributor to a technology manager requires abandoning static mindsets, giving team members opportunities, feedback, and support, and learning from examples at companies like Google, while reflecting on personal habits to become an effective R&D leader who fosters continuous growth.
This article explains what software architecture is, its lifecycle, why a solid architecture is crucial, how to distinguish good from bad designs, the roles and responsibilities of architects, and the skills—both technical and soft—needed to become an effective software architect.
This article explains the distinctions and progression steps from senior programmer through architect, technical manager, technical director, to CTO, offering objective guidance on required experience, core duties, and leadership skills for each role in the software engineering career ladder.
The article explores the distinction between part‑time and full‑time software architects, outlines the core responsibilities such as global technical planning, unified methods and standards, robust foundational building, and practical implementation, and discusses rights, assessment criteria, and practical ideas for effective architecture practice.
The author reflects on three major challenges—staff turnover, project‑schedule control, and software‑quality improvement—and argues that mastering software‑engineering techniques, tooling, and domain knowledge is essential for effective technical team management.
This article explores why technical experts often lack management skills, outlines the typical career stages of engineers, and provides practical guidance on developing the mindset, responsibilities, and core competencies needed to become a successful technical manager.
This article explores the blurry line between development and software architecture, outlines the responsibilities and evolution of a software architect, and provides practical guidance on defining architecture, managing non‑functional requirements, selecting technologies, evaluating designs, and leading teams toward successful releases.
This article shares practical guidance for founders and technical leaders on assembling, structuring, and managing early‑stage engineering teams, highlighting common mistakes, hiring strategies, communication practices, and the balance between speed and professionalism to ensure sustainable growth.
This guide outlines practical strategies for tech team leadership, covering people, project, technology, and culture management, recruitment, mentorship, code review, pair programming, documentation standards, automation, and workflow optimization to boost productivity and morale.
This article shares a senior technical director’s hard‑won lessons on balancing hands‑on development, non‑functional requirements, architecture design, training, and management to boost team productivity and product quality in software projects.
The article explains the definition of software architecture, the multifaceted responsibilities of architects, and eight principles of personal cultivation that help architects make better decisions, communicate effectively, and sustain high‑quality designs over time.
This article outlines the responsibilities and career progression of technical roles—from entry‑level programmers to senior engineers, architects, technical managers, directors, and CTOs—highlighting how each level adds scope, leadership, and strategic impact within an organization.
The article explains what software architecture is, defines the architect’s role as a decision‑maker and designer, and outlines eight principles of personal cultivation that help architects make sound technical choices, communicate effectively, and continuously improve their skills.
This article explains how internet companies can design and evolve technical team hierarchies—from flat, three‑level startups to large, multi‑team enterprises—by aligning roles, responsibilities, and communication flows to product scale and business goals.
The article explores why top software architects must be outstanding programmers, highlights the importance of abstract thinking, technical foresight, problem‑solving and communication, and presents interview excerpts from industry veterans such as Fred George, Randy Shoup and Liang Yuanhua, offering practical guidance for engineers aspiring to architectural roles.
The article outlines the essential qualities of a software architect—including deep core technology knowledge, product awareness, awareness of software trends, and innovative problem‑solving—while sharing personal experiences on building trust, creating reusable code, and bridging business and technical domains.
This article explores the definition, lifecycle, importance, and best practices of software architecture, compares good and bad designs, outlines the roles and responsibilities of architects, and offers guidance on the skills and mindset needed to become an effective software architect.
This article explores the critical role of a software architect, detailing the essential business understanding, abstraction, coding ability, comprehensive system thinking, global impact awareness, and trade‑off decision‑making skills required to excel in the position.
The article outlines the essential qualities, responsibilities, and decision‑making principles of a software architect, emphasizing business understanding, comprehensive system design, technical depth, global perspective, and balanced trade‑offs to ensure scalable, maintainable, and future‑proof solutions.
The article explores the evolving role of software architects in the internet era, outlining their core responsibilities, essential capabilities, and four key practices—broad information gathering, compromise, taking responsibility, and confronting conflict—to guide professionals toward effective system design and continuous growth.
The article defines a software architect as a senior engineer responsible for high‑level system design, explains the role’s core value in breaking large systems into low‑coupled modules, and outlines six essential abilities and four practical lessons for effective architectural practice.
The article explains that software architecture is a set of critical decisions made by architects, outlines their multifaceted responsibilities—from research and design to persuasion and documentation—and presents eight principles for architects to develop professional ethics and continuous self‑improvement.
The article argues that software architects must stay hands‑on—coding, pairing, reviewing, and rotating with delivery teams—to gather timely feedback, exercise effective technical leadership, and avoid the isolated "ivory tower" that hampers agile, high‑quality system development.
This article offers practical advice for aspiring lead developers, emphasizing personal responsibility, servant leadership, essential traits, leading by example, embracing accountability, fostering communication, and helping every team member succeed to create a high‑performing development team.
The article outlines six critical qualities—hands‑on programming, abstract thinking, technical foresight, problem‑driven analysis, cross‑domain knowledge, and strong communication—that distinguish an effective software architect and guide them through every phase of a project.
