The article argues that technical brilliance alone won’t propel a technologist to the CIO role; instead, mastering management, earning company-wide trust, and communicating business value are essential, and it outlines three concrete capabilities and a career path to achieve them.
The author recounts a 16‑year IT journey—from unproductive early jobs and frequent moves, through a pivotal switch to a major internet firm, to successive roles as tech lead, manager, and backend head—highlighting the challenges, decisions, and lessons that shaped a successful technical leadership path.
This article outlines five common flaws of ineffective technical managers—ranging from clueless direction‑setting and superficial reporting to credit‑stealing and information silos—and explains what qualities define a good tech leader who respects expertise and supports the team.
This article explores four fundamental thinking patterns—control mindset, leverage mindset, endgame mindset, and closed‑loop mindset—that technical managers should adopt to lead teams effectively, make strategic decisions, and continuously improve both themselves and their organizations.
The article shares a senior engineer’s experience designing and implementing comprehensive R&D standards across multiple departments, explaining the underlying logic, key value drivers, a five‑part framework, and practical tips for tailoring standards to organizational context while fostering efficiency and knowledge retention.
This article explains how the author used the AI model DeepSeek to generate a curated 24‑book reading list—12 essential software architecture classics and 12 must‑read technical management titles—while sharing prompts, insights, and a recommended guide to mastering DeepSeek itself.
The article explores the core challenges faced by junior technical managers, emphasizing the shift from hands‑on implementation to strategic domain oversight through frameworks like PESTEL and Porter’s value chain, and offers practical guidance for aligning with senior leadership while building expert teams.
This article outlines a practical, step‑by‑step framework for technical managers to assess, develop, and continuously coach fresh graduates and junior staff, linking clear management objectives with concrete measures such as BOK creation, capability models, and the GROW coaching cycle.
This article explains what upward communication is, outlines its four core components, describes the roles of senior leaders, and provides practical preparation steps, strategic principles, and communication techniques for middle‑level technical managers to convey information effectively and gain support.
The article explains how SaaS companies can design and implement a comprehensive metric system that aligns business and technical indicators, supports data‑driven decision‑making, improves resource allocation, and drives continuous improvement across all organizational levels.
The article presents an interview with Tubi Tech Leads, exploring why many would choose the role again, the unique incentives and difficulties of technical management, the importance of data‑driven culture, cross‑regional collaboration, and current hiring for a Big Data Platform Lead.
This article outlines a three‑level problem‑solving methodology—emergency response, deep analysis, and pursuit of excellence—providing technical managers with concrete steps, communication templates, and real‑world SaaS examples to boost team performance and drive continuous improvement.
The author recounts a 14‑year progression from a wandering junior developer to a backend technology leader, sharing concrete lessons on early stagnation, strategic job changes, team leadership, large‑scale system refactoring, and the mindset required to grow into senior technical management roles.
This article explains the history and principles of OKRs, outlines a step‑by‑step process for defining a technical department’s purpose, identifying internal customers and their needs, reviewing past OKRs, and establishing practical guidelines for drafting, iterating, and communicating new OKRs.
The article uses thermodynamic analogies to argue that without continuous system optimization teams face entropy, then outlines how managers can find a leverage point, avoid cognitive biases, and adopt three concrete performance metrics—startup time, transaction latency, and issue‑resolution quality—while establishing daily technical‑management habits.
In this article, a tech leader shares ten concrete practices—from delegating authority to group leads and building personal trust, to handling on‑call releases and protecting subordinates—that have helped him effectively manage a diverse 100‑plus‑person engineering organization.
The article critiques traditional software architects as bottlenecks, shares personal experiences at eBay and Alibaba, argues that dedicated architecture departments often cause more harm than good, and advocates that every engineer develop architectural thinking, offering guidance for engineers, team leads, and CTOs.
The article shares five practical lessons from a senior engineer on how to manage upstream product interactions, run projects, coordinate testing, lead teams, and communicate with super‑iors, emphasizing early bug prevention, clear reporting, and empowering team members.
The author reflects on a recent departmental restructure that changed his direct manager, analyzes how a new leader reshapes career growth, decision‑making authority, and team dynamics, and shares a 3P1T framework and three practical steps for gaining trust, decision resources, and feedback.
In this personal essay the author recounts eight years of tech‑industry experience, from early salary stagnation at Amazon to multiple promotions, startup failures, mentorship, and finally senior leadership at a unicorn, highlighting the mindset shifts and proactive strategies needed to break through the career ceiling.
The article reflects on how most members of technical teams are passively driven, examines the unsustainable management practices that try to force active drive, draws parallels with education and economic sustainability, and proposes a more balanced, sustainable team culture that respects individual differences and long‑term growth.
The article shares a senior front‑end engineer’s journey at Alibaba, defining growth, change and breakthrough, outlining how personal development intertwines with business goals, and offering practical steps—market insight, KPI alignment, problem definition, and mentorship—to turn individual effort into measurable team results.
This article presents 30 practical guidelines for technical leaders, covering team structuring, agile practices, communication, performance tracking, and cultural initiatives to enhance productivity and morale within engineering groups while also warning against common pitfalls and emphasizing the importance of empathy and continuous improvement.
This article shares practical insights on the three typical misconceptions faced by technical R&D leaders, explains why they hinder team productivity, and offers concrete strategies—including balanced time allocation, effective delegation, and talent development—to transform personal expertise into high‑leverage leadership impact.
This article outlines the typical career progression in software development, describing the duties and expectations of programmers, senior programmers, architects, technical managers, directors, and CTOs, and provides insight into how responsibilities evolve from coding to system design and organizational leadership.
The article explains that promotion depends more on trust and reliability than pure ability, outlining owner‑mindset, timely feedback, attention to detail, and the core responsibilities of technical managers—including managing tasks, people, direction, and results—to support business goals and personal growth.
This article outlines the responsibilities of frontline technical managers, detailing project release stages, technical review and documentation standards, code style and development conventions, code management practices, and a comprehensive CodeReview process to ensure quality and efficiency across software projects.
This reflective guide shares personal insights and practical steps for newly appointed technical team leads, exploring why they choose the role, how to act before overthinking, and ways to break mental barriers to foster growth, authenticity, and impactful leadership.
In a candid coffee‑shop dialogue, a startup founder and a senior engineering leader explore the essential abilities of technical managers, revealing that technical judgment—not just coding—drives effective decision‑making, risk assessment, and strategic leadership across evolving team sizes and product stages.
The author shares personal insights on transitioning from hands‑on technical work to managing technical teams, covering career progression, skill development, effective hiring, team integration, leadership mindset, and strategies for sustainable growth and collaborative success in security‑focused projects.
Management, like technology, blends technical rigor—task execution, business assurance, and strategic OKR alignment—with artistic sensibility—trust-building, talent nurturing, and self-development—so leaders must master both mind and heart to drive results, foster collaboration, and continuously refine objectives through iterative reviews.
This article explores the core responsibilities of a technical team lead, covering team building, management styles, culture cultivation, communication, hiring, and dismissal strategies, and offers practical advice and real‑world examples to help leaders create high‑performing engineering teams.
This article explores how a frontline technical manager can shift from a traditional top‑down approach to proactive, upward management, emphasizing non‑complaining culture, effective task prioritization, and empowering team members to drive both business and technical growth.
Two short stories illustrate how a tech lead’s choice of helping style—either giving direct solutions or guiding thoughtful discussion—affects team autonomy, risk awareness, and long‑term growth, highlighting the importance of empowering engineers rather than merely providing quick fixes.
In this talk, the CTO shares practical insights on transitioning from a technical expert to a manager, outlines the dos and don’ts of technical leadership, and offers personal growth strategies to stay hungry and foolish while building effective, purpose‑driven teams.
Ren Dengjun, a Meituan Dianping tech leader, recounts her shift from NLP research at Northeastern to industry roles at Toshiba, Alibaba, and Youyi, now heading Meituan’s location‑based advertising platform, while sharing insights on leadership, gender bias, and balancing technical and managerial challenges.
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.
This article presents a practical 90‑day roadmap for engineers stepping into their first technical management role, covering why a plan is essential, the three phases of knowledge building, rhythm finding, and self‑assessment, plus concrete advice on communication, mentorship, meeting management, and evaluating personal fit.
This article shares practical advice from a former development director on how technical managers can excel by connecting with their teams, managing tasks effectively, mastering time and resources, respecting individuals, and representing their team’s interests to drive success.
This article explores why technical experts often lack management experience, outlines the typical career stages of a developer, and provides practical guidance on shifting mindset, setting team goals, allocating resources, improving communication, and fostering empowerment to become successful technical managers.
