Best of Leadership — January 2026

1
Article
Tech World With Milan·16w
You can code only 4 hours per day. Here’s why.
Research shows developers can only sustain 3-4 hours of deep, focused coding per day due to cognitive limits. Studies reveal the median developer codes just 52 minutes daily, with 11+ hours weekly consumed by meetings. Interruptions cost 23+ minutes to recover from, and achieving flow state requires 15-25 uninterrupted minutes. Practical strategies include time-blocking, eliminating context switching, protecting morning hours, and setting no-meeting days. AI coding assistants don't extend deep work capacity but can handle shallow tasks. Engineering managers should prioritize removing meetings over adding processes to maximize team productivity.
420
25
2
Article
Stack Overflow Blog·20w
Documents: The architect’s programming language
Software architects distinguish themselves from senior developers by mastering the deployment of ideas through documentation rather than just code. The architect role requires organizing people and consensus through written documents like architecture overviews, dev designs, project proposals, developer forecasts, technology menus, problem statements, and postmortems. Effective technical documentation relies on bullet points for information density, headers for organization, and chronological rather than topical filing. Documents should be treated as point-in-time artifacts that serve specific purposes rather than continuously maintained resources. The key insight is that the biggest bottlenecks in software development are people problems around communication and decision-making, not technical ones.
131
3
3
Article
Josh Hornby·18w
What is a Tech Lead?
The tech lead role varies significantly across companies. At larger organizations, it typically focuses on technical direction without people management. At smaller companies, tech leads handle both technical leadership and people development. The hybrid role encompasses three core areas: setting technical direction and architecture standards, helping engineers grow through mentoring and code reviews, and ensuring delivery by unblocking teams and managing scope. Success means becoming less essential over time by building team capability rather than being a bottleneck. The role requires balancing competing demands between coding, mentoring, and delivery.
96
5
4
Article
UX Planet·18w
Why remote work stopped working for me
Remote work initially seemed ideal for an introvert, eliminating commutes and office noise. However, over time, subtle trade-offs emerged: fewer interruptions led to weaker relationships with colleagues, increased focus came with more frequent blockers waiting for async responses, and comfort at home reduced creative energy and motivation. Tracking mood revealed that office days, despite feeling draining, resulted in better satisfaction and sleep. The author now works from the office at least three days per week, finding that in-person presence accelerates decision-making, learning, and connection, even though it requires more effort than staying home.
80
23
5
Article
Tech Lead Digest·17w
How I Bankrupted Two Companies
A first-time president's paralysis in decision-making led to the bankruptcy of two tech companies despite having revolutionary processor technology. The fear of making wrong decisions resulted in making no decisions at all, causing the company to miss market opportunities while engineers waited for direction. After seven months of unemployment, the author learned that the cost of indecision is almost always worse than deciding wrong, and that most decisions are reversible two-way doors that don't require 100% certainty.
50
4
6
Video
The Serious CTO·19w
7 Career Mistakes I’d Avoid If I Started Coding Again (CTO Advice)
A CTO with 40 years of experience shares seven career mistakes to avoid: being too helpful instead of strategic, failing to document and communicate achievements, not speaking the language of business metrics, avoiding organizational politics, staying too long in toxic cultures, focusing solely on technical skills over positioning, and not building external credibility. The advice emphasizes that career advancement requires strategic thinking, visibility management, business acumen, and deliberate self-promotion rather than just technical excellence.
41
2
7
Video
The Serious CTO·17w
12 Commandments for Devs
A provocative manifesto arguing that developers need to shift from being "ticket checkers" to value-focused leaders. Emphasizes efficiency over motion, questioning requirements over blind obedience, building maintainable systems over quick MVPs, automating repetitive work, choosing appropriate architecture over hype, documenting decisions, understanding business context, avoiding tool worship, and protecting work-life boundaries to prevent burnout. The core message: stop treating software development as pure execution and start treating it as strategic value creation.
40
1
8
Article
The Developing Dev·20w
Anthropic Eng Leader and Ex-Senior Director at Meta on Advice That Changed Her Career
Fiona Fung, engineering leader at Anthropic and former Senior Director at Meta, shares career insights on managing managers, mentorship approaches, and company culture differences. Key themes include the importance of dogfooding products, building trust with direct reports through transparent communication, balancing impact with team health during high-pressure periods, and working effectively across engineering and product partnerships. She emphasizes mission-driven work, kindness in engineering culture, and receiving feedback gracefully as career-changing practices.
39
9
Article
Stay SaaSy·18w
The Most Important Teams in Tech
In B2B software companies, engineering and sales are the only truly critical functions because they directly build and sell the product. All other roles, including product management, design, and marketing, exist to support these two core teams. This reality has important implications: non-engineering/sales teams must recognize their supporting role and prioritize these functions' needs, sales and engineering leaders face intense pressure to continuously improve or risk replacement, and adjacent roles should deeply understand these disciplines to be effective. The prominence of engineering and sales explains why tech CEOs often come from these backgrounds, why product-led growth can succeed by eliminating sales risk, and why investors like Y Combinator require engineering expertise on founding teams.
37
2
10
Article
Manager.dev·18w
Who does what and how to support them
Engineering managers must balance three competing needs when assigning work: company efficiency (using the most capable person), engineer advancement (providing growth opportunities and challenges), and team durability (avoiding single points of failure through knowledge distribution). A knowledge map helps visualize team capabilities and identify gaps. Support should be based on task-relevant maturity rather than seniority, adjusting management style based on an engineer's experience with the specific task rather than their overall level.
30
1
11
Video
EO·18w
How I Rebuilt a $1.3B Giant with an AI Agent While Facing My Own Death | Intercom, Eoghan McCabe
Intercom's founder shares his journey of returning as CEO during a health crisis to rebuild the $1.3B company. He implemented aggressive cultural changes, performance management reforms, and bet heavily on AI agents (Finn), sacrificing $60M in revenue to pivot the business. The story covers lessons on founder mentality, authentic leadership, willingness to make unilateral decisions, and the necessity of constant reinvention in tech companies, especially with AI disruption.
27
4
12
Article
swizec.com·19w
Small projects, clear scope
Planning before coding saves significant time and reduces stress. A simple project brief answering five key questions—what problem you're solving, how you'll solve it, how you'll know it's done, what's explicitly out of scope, and who benefits—provides enough structure for teams to work effectively. The entire team should collaborate on the execution plan, with managers defining goals. Explicitly documenting what's NOT included prevents scope creep, and vague project names like "Make X better" should be avoided. Experienced engineers often do this intuitively, but adding structure helps others.
22
1
13
Article
sean goedecke·17w
You have to know how to drive the car
Understanding how tech companies operate is essential for software engineers regardless of their career goals. Whether pursuing promotions, maintaining work-life balance, or driving specific initiatives like accessibility, engineers need to navigate organizational politics effectively. Ambitious engineers should focus on project leadership and results rather than ticket completion. Those seeking work-life balance should strategically manage their reputation while minimizing effort. Engineers with specific value-driven goals need to build organizational capital to pursue unsanctioned work. Ignoring these organizational dynamics leads to frustration, missed opportunities, or being pushed out, while mastering them enables leveraging the scale of large companies to create meaningful impact.
16
14
Article
bonnycode·18w
Where feedback goes to die
Feedback often gets politely acknowledged but never acted upon, stored away like unwanted gifts. The real value of feedback lies in its ability to reveal when we're wrong—but only if we're willing to define what being wrong would look like beforehand. Effective feedback reception requires moving beyond judging whether criticism is "accurate" to understanding what it reveals about how others experience our work. Upward feedback is particularly easy to dismiss, yet it provides irreplaceable perspective from those affected by our decisions. Genuine, honest feedback from people who care isn't freely given—it's earned through consistently responding with curiosity and visible change rather than defensiveness.
16
1
15
Article
The Architect Elevator·17w
The Mighty Metaphor
Metaphors are essential tools for architects to translate complex technical concepts into language that business stakeholders can understand and reason about. Effective metaphors enable audiences to grasp trade-offs and constraints without technical jargon, transforming one-way explanations into collaborative thinking sessions. The best metaphors come from domains familiar to the audience—finance, business operations, or everyday items like cars—and should hold up to logical scrutiny rather than serving as mere decoration. When audiences embrace and extend a metaphor beyond its original scope, it becomes a powerful amplifier of mutual understanding. Finding good metaphors requires patience, testing with friendly audiences, and avoiding pitfalls like broken logic, cultural insensitivity, or frivolous imagery that doesn't connect to the core message.
12
1

See all Leadership archives