1 views collected around this technical thread.
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 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.
This article explains how technical managers and developers can adopt a problem‑solver mindset, apply a structured methodology for diagnosing and resolving issues, and act as clear “voice‑pipes” to convey information responsibly, thereby improving team efficiency, cohesion, and information security.
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 how technical managers and developers can become effective problem solvers and reliable communicators by understanding problem types, applying a structured resolution methodology, and mastering clear information transfer while respecting privacy and security.
The article outlines four fundamental mindsets—Control, Leverage, Endgame, and Closed‑Loop—that technical managers should adopt to take responsibility, leverage team efficiency, plan with future goals, and ensure complete feedback loops, while also offering practical habits like learning, self‑reflection, planning, and integrating knowledge into daily practice.
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.
This article explains how technical managers can improve ROI by systematically collecting information, defining clear goals, prioritizing tasks, evaluating alternatives, avoiding common cognitive biases, and using tools such as RACI matrices and continuous process control to execute and refine decisions.
This guide outlines a four‑step process for new technical managers—identifying people, defining work, linking people to tasks, and setting clear goals—supported by six practical tables such as member information, talent ladder, development plans, RASCI matrix, and OKR tracking.
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.
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 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.
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.
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.