This article outlines seven essential habits—rapid high‑quality decision making, knowing when to code, building trust, effective delegation, upward management, setting expectations with measurable progress, and timely feedback—that empower CTOs to lead teams confidently and drive organizational success.
Tech lead Tang Qiao shares his journey from iOS developer to product‑tech manager, explaining why engineers should consider management, debunking common misconceptions, and offering practical advice on time management, communication, mentorship, and upward management to help technical professionals transition into effective leadership roles.
The article recounts Joel Spolsky’s Yale talk, highlighting his key takeaways about focusing on real problems, avoiding in‑house programmer roles, the importance of aligning business with technical expertise, and how strong communication separates ordinary staff from leaders.
This article chronicles Ma Huateng's journey from a shy programmer to Tencent's founder, highlighting the company's pivotal milestones, product decisions, talent policies, and the relentless sense of crisis that shaped its evolution into a global internet powerhouse.
This article explores the real day‑to‑day responsibilities of a startup CTO, debunking myths and outlining five concrete skills—from platform selection to fostering technical leaders—that enable technology strategy to align with business goals.
The article shares a real‑world workplace story about a disruptive employee, then outlines seven practical principles—respecting superiors, keeping them informed, giving proper feedback, avoiding incitement, not creating trouble, responding to ad‑hoc tasks promptly, and helping leaders succeed—to guide professionals in building effective, harmonious teams.
The article critiques conventional performance evaluations, argues that goals should improve organizations rather than judge individuals, explores the pitfalls of KPI, and shows how OKR, when properly applied, can foster transparent, purpose‑driven work while encouraging personal growth.
The article discusses how expert programmers must continuously learn and balance humility with confidence, explores the end‑to‑end design principle, examines complexity, layering, and componentization in large systems, and highlights performance considerations, distributed‑system realities, and management lessons for building robust software.
After a decade in software development, the author reflects on common career pitfalls—frequent platform switching, chasing management roles, neglecting breaks, stopping coding, avoiding community, and over‑relying on job boards—offering practical advice to build a sustainable, rewarding developer path.
The article examines common pitfalls in corporate communication—such as proving others wrong, ego‑driven talks, blame‑shifting, suppressed grievances, and poor leadership styles—and proposes three principles for healthy dialogue: removing emotion, practicing empathy, and co‑creating solutions, while linking communication to decision‑making mechanisms.
The article introduces classic management tools such as the 80/20 rule, SWOT, 5M, PDCA, 5W2H and SMART, explaining how they help architects and product designers efficiently plan and execute work, with a detailed breakdown of the SMART criteria for actionable goal setting.
The article examines the paradox of having many developers but little output, identifying causes such as misaligned roles, poor code quality, communication overhead, mistrust, unclear requirements, and outdated architectures, and offers practical suggestions to improve efficiency in software projects.
The article outlines five common causes of tension between software architects and developers—including misassigned roles, cowboy programmers, detached "ivory‑tower" architects, perpetual complainers, and unclear authority—while offering practical solutions for fostering a more collaborative relationship.
This article shares six practical stories—from a broken Mac repair dilemma to project reporting, vendor selection, and daily work habits—illustrating how leaders prioritize speed and efficiency, the importance of clear communication, and the standards for doing work well while fostering teamwork and personal growth.
This article shares a fictional CTO’s hard‑earned lessons on navigating the cultural, managerial, and technical challenges that traditional firms face when transforming into Internet‑centric businesses, offering practical advice on compensation, boss profiling, cross‑departmental relationships, and team leadership.
The article outlines four career stages for engineers—newcomer, mature, development, and career—explains why growth often slows after three years, and offers concrete learning, work, and mindset strategies to transition from passive to proactive growth and prevent mediocrity.
This article shares practical insights on recruiting for R&D teams, covering the importance of top talent, the role of founders and technical leads, effective sourcing channels like schools and resume mining, and the impact of personal influence on quickly assembling a high‑performing team.
In this extensive interview, Huawei founder Ren Zhengfei explains how political reforms, tax incentives, a relentless single‑focus strategy, continuous learning from the West, strong intellectual‑property protection, and a culture that values ideals over profit have driven Huawei’s growth and shaped his views on innovation, management, and China’s future industrial landscape.
The article shares practical insights for engineers transitioning to management, emphasizing the shift from doing to delegating, prioritizing important over urgent tasks, establishing clear rules, fostering team communication, and mastering strategic thinking to drive both personal and team growth.
This article analyzes whether enterprises should adopt Active Directory domains by presenting a survey of 110 companies, highlighting the reasons for and against domain integration, and sharing expert opinions on the benefits, risks, and management considerations involved.
Through a collection of fifteen timeless fables—from Achilles' heel to the tortoise‑hare rematch—this article illustrates how hidden weaknesses, complacent vigilance, strategic planning, opportunity preparation, risk awareness, and fair mechanisms shape effective management and leadership in organizations.
Huawei’s success stems from a long‑standing profit‑sharing system that treats knowledge as capital, distributes value through employee stock ownership, and aligns incentives with a culture of collective effort, driving the company from six founders to over 170,000 staff and billions in revenue.
The article argues that a successful development team always includes a less‑skilled member, and how treating that person with respect and support reflects the team’s culture, improves morale, and ultimately enhances overall project quality.
Wang Xing, the CEO of Meituan, shares hard‑earned startup lessons, arguing that relentless growth often outweighs strict focus, while also highlighting counter‑examples and ancient Chinese principles that can guide modern entrepreneurs in building and scaling a company.
This article recounts a career experiment where a senior software engineer named Bill reshaped his résumé to emphasize managerial experience, navigated two contrasting interview processes, and analyzes how social status and perceived leadership affect hiring outcomes in the tech industry.
The article explains why a software project requires a Team Leader, discusses the limits of self‑organized teams, highlights the responsibilities and challenges of leadership, and uses a stone‑soup fable to illustrate the importance of shared effort and management beyond coding.
Effective management hinges on three intertwined challenges—clear responsibility, seamless collaboration, and motivating incentives—each requiring distinct strategies such as fostering a partnership mindset, streamlining processes, and implementing fair performance evaluations to align individual actions with organizational goals.
Julie Zhuo, Facebook’s product design director, explains how great leaders use Simon Sinek’s Golden Circle to inspire teams, contrasts ordinary and excellent managers across five real‑world scenarios, and shares ten practical management rules for building effective, purpose‑driven organizations.
This article explores Peter Drucker's insights on managerial effectiveness, emphasizing self‑management, optimal use of limited time, contribution awareness, leveraging strengths, prioritizing important tasks, and making informed decisions to transform knowledge into tangible organizational outcomes.
The article uses three vivid workplace anecdotes to illustrate why clear goals, feasible methods, solid communication, rational processes, proper incentives, and effective assessment are essential for turning strategy into successful execution.
This article explores the dilemma faced by seasoned IT professionals of choosing between a technical track and a managerial path, examining personal reflections, survey insights, economic considerations, and practical advice to help decide which direction aligns with one's skills, goals, and lifestyle.
This guide walks software engineers through six career phases—from college student to tech director—offering practical advice on goal setting, choosing employers, early‑career pitfalls, management fears, and how to keep growing while avoiding common regrets.
This article explains decision execution models, defining the concept, outlining its ideal assumptions, comparing it to mathematical induction, and discussing why real‑world constraints make the model impractical while still offering valuable insights for improving decision‑making processes.
The article presents Uber engineering leader Raffi Krikorian’s twelve practical rules for planning, executing, and managing software architecture refactoring, emphasizing clear purpose, measurable goals, incremental delivery, data‑driven decisions, technical debt control, realistic technology choices, and stakeholder communication.
This article offers goal‑oriented, data‑driven advice and checklists for architecture refactoring, emphasizing realistic technology selection, pressure management, business understanding, handling non‑technical influences, code‑quality practices, and team readiness to ensure effective, sustainable redesigns.
This article outlines the concept of efficient operations, analyzes why it is difficult to achieve, and presents practical strategies—including clear responsibilities, technical specialization, management professionalism, and good customer interaction—to improve operational efficiency in technology teams.
This guide explains how to set the system name, configure the Ethernet management interface, assign an IP address, and enable Telnet with privileged access and AAA authentication on Quidway network equipment, including notes on chassis versus box port differences.
An analysis of software release delays reveals that uniform developer productivity, vague or changing requirements, and disruptive task handoffs—rather than programmer slowness—are the primary culprits, and offers practical steps for managers to improve workflow.
Meituan’s rapid O2O expansion hinges on a disciplined, data‑driven ground‑sales force that first conquers suburban districts before encircling city centers, leveraging aggressive incentives, real‑time IT tools, and strategic partnerships to wrest market share from rivals like Dianping while building a comprehensive ecosystem.
This article examines the multiple administrative, commercial, technical, and market reasons that force IT professionals into chronic overtime, discusses the habit‑forming nature of overwork, and proposes realistic boundaries to protect employee health while maintaining productivity.
