Matthias Endler·42wHow To Review Code
A comprehensive guide to effective code reviewing based on two decades of experience. Emphasizes focusing on big picture design over syntax, the critical importance of good naming, being decisive when rejecting changes, and treating reviews as iterative communication processes. Key principles include running code locally when possible, asking clarifying questions, avoiding nitpicking on formatting, and continuously learning from the review process.
Dev Squad·1yI'm the CTO now
This post humorously narrates the author's unexpected rise to CTO amidst chaos in a failing startup. With most of the team quitting, the author becomes the CTO not out of ambition but exhaustion. They struggle with managing an inherited mess of tech and responsibilities, highlighting the burnout and absurdity in the tech industry. The narrative illustrates the often unplanned path to leadership and the challenges that come with sustaining a sinking ship.
David Heinemeier Hansson·33wPay yourself first
Prioritizing meaningful work over endless administrative tasks is essential for maintaining motivation and developing competency. By dedicating time to programming, experimentation, and research that genuinely interests you—even when responsibilities pile up—you create a virtuous cycle where growing skills lead to more autonomy. The key is treating personal development and intellectually fulfilling work as non-negotiable priorities rather than items at the bottom of an endless to-do list.
Hacker News·1yStartup-CTO-Handbook/StartupCTOHandbook.md at main · ZachGoldberg/Startup-CTO-Handbook
The Startup CTO Handbook by Zach Goldberg is a comprehensive guide for technical leaders, focusing on leadership, management, and technical topics crucial for leading engineering teams in startups. It emphasizes continuous learning, adapting to change, and the importance of people leadership alongside technical skills. The book offers practical advice on team management, building company culture, and developing decision-making skills, making it an invaluable resource for both current and aspiring CTOs.
Tech Lead Digest·23wTraits of a good Tech Lead
Tech Leads are responsible for technical direction across three pillars: architecture (defining decisions, managing technical debt), quality (maintaining standards), and mentorship (enabling team growth). Good Tech Leads use written artifacts like RFCs and PoCs to structure decisions, actively negotiate technical scope with product stakeholders, and establish operating principles that enable autonomous decision-making. They generate team velocity through clarity, reduce ambiguity, and influence without authority. Key anti-patterns include making improvised decisions without documentation, overdesigning solutions, and centralizing knowledge instead of distributing it across the team.
InfoWorld·34wWhy we need junior developers
Companies are increasingly avoiding hiring junior developers and relying on AI for basic coding tasks, but this creates long-term problems. Junior developers are essential for the future pipeline of senior talent, bring fresh perspectives to established teams, and provide necessary balance in team dynamics. Teams with only senior developers risk becoming siloed and lacking the collaborative knowledge transfer that occurs through mentoring relationships.
David Heinemeier Hansson·1yAge is a problem at Apple
Apple's board and executive team have a high average age, with board members averaging 68 years old and executives around 60. The post argues that this older leadership might be out of touch with current trends and technologies, as illustrated by recent issues with AI features. In comparison, Meta's board has a younger average age, highlighting a potential difference in leadership dynamics.
Tech World With Milan·43w5 books that changed my engineering career forever
A CTO shares five transformative books that shaped his engineering career: The Pragmatic Programmer for professional development principles, Designing Data-Intensive Applications for systems architecture understanding, A Philosophy of Software Design for managing code complexity, Thinking Fast and Slow for decision-making improvement, and The 7 Habits of Highly Effective People for leadership foundations. Each book contributed beyond technical knowledge by challenging assumptions, introducing mental models, and changing approaches to coding, team leadership, and career growth.
David Heinemeier Hansson·35wThe great falls of Boeing, Intel, and Apple
A critical analysis of how major tech companies like Boeing, Intel, and Apple have declined after appointing CEOs without engineering or product backgrounds. The author argues that it takes approximately ten years for company culture to deteriorate under non-technical leadership, citing specific examples of failed products and strategic missteps at each company. The piece advocates for technical leaders who understand the products they oversee rather than purely business-focused executives.
Manager.dev·33wBuild your engineering team like a dungeon party
A framework for building balanced engineering teams using RPG dungeon party roles as a metaphor. The approach advocates for complementary skills over hiring only top performers, suggesting five archetypes: the warrior (senior problem-solver), the tank (reliable junior executor), the healer (people-focused and business-oriented), the wizard (architect/designer), and the rogue (versatile full-stack developer). Engineering managers should identify team gaps and adapt their own contributions to fill missing roles, whether that's handling small tasks, stakeholder management, or hands-on coding.
DEV·22wTechnical Debt Is a Myth Created By Bad Managers
The term "technical debt" is a fundamentally broken metaphor that shifts blame from management decisions to engineers. Most code quality issues stem from impossible deadlines, resource constraints, and business pressures rather than deliberate shortcuts. Code naturally ages as requirements evolve and platforms change, which isn't debt but normal software evolution. The metaphor obscures that engineering decisions are trade-offs made under specific constraints, not moral failures. Better alternatives include "maintenance cost," "context shift," or "technical consequences of business decisions" to accurately reflect accountability and enable realistic planning.
swizec.com·44wWhat makes a senior engineer
Senior engineers are expected to go beyond just implementing requirements - they must push back on product decisions, own OKRs and roadmaps, work directly with stakeholders to solve business problems, and champion long-term technical vision. The role involves setting strategic direction, managing multi-month or multi-year projects, and ensuring all team efforts align with the overall technical vision. Engineers who only execute tasks without questioning or strategic thinking typically don't advance beyond mid-level positions.
Tech Lead Digest·1yHow To Get Good at Strategy
The post emphasizes the importance of developing effective strategic thinking by understanding the core challenges in a situation and designing coordinated actions to address them. It highlights principles such as simplicity, coordination, specific challenge identification, and working with obstacles. Additionally, it warns against common strategy pitfalls like mistaking goals for strategy, analysis paralysis, and ignoring implementation.
ITNEXT·1yWhat does a Technical Lead do?
The post explores the role of a Technical Lead, highlighting their responsibilities in guiding the technical direction of projects, mentoring team members, and ensuring alignment with business goals. It discusses the importance of technical ownership, project execution, cross-team communication, and quality oversight. Additionally, it touches on the concept of an Uber Tech Lead, who oversees multiple projects or teams and contributes to strategic decision-making.
UX Planet·50wStop trying to be Steve Jobs and start learning from the losers
Many companies blindly copy organizational models and practices from successful tech giants like Spotify, Google, and Netflix, but this approach often fails because these practices are context-dependent. The Spotify model, for example, has been abandoned even by Spotify itself. Instead of learning from winners who represent survivorship bias, teams should study failures to understand what actually breaks. Success stories are incomplete and don't prove causation - just because successful companies do something doesn't mean it made them successful. Organizations should think from first principles and adapt practices to their specific context rather than treating tech giant approaches as gospel.
Atlassian·1yHow to apologize for a mistake professionally (with examples)
Apologizing for mistakes at work is essential for maintaining trust, strong relationships, and a positive team culture. A professional apology includes expressing regret, explaining what happened, taking responsibility, being clear and succinct, suggesting next steps, and asking for forgiveness. Whether delivered in person, via email, or remote communication tools, the key is to be genuine and take actionable steps to prevent future mistakes.
Work Chronicles·1y(comic) Inside-the-box Brainstorming
A comic explores the concept of 'inside-the-box' brainstorming, focusing on workplace humor and the dynamics of team meetings. It is a light-hearted take designed to entertain and perhaps provide a fresh perspective on traditional brainstorming sessions.
bonnycode·36wWork Hard, Have Fun, Go Home
Hustle culture prioritizes the appearance of hard work over actual results, creating toxic workplace dynamics that harm both individuals and organizations. The author shares personal experiences showing how strategic thinking and sustainable work practices lead to better outcomes than grinding through long hours. Key warning signs include employees who never take real vacations, single points of failure in critical systems, and leadership that emphasizes effort over results when facing challenges. The most effective teams focus on innovation and value creation rather than time spent at desks.
Stay SaaSy·51wYour Manager Is Not Your Best Friend
Managers should avoid commiserating with their direct reports as it creates organizational toxicity, builds factions, and prevents other teams from improving. Instead of providing unconditional sympathy like a best friend would, effective managers need to ask clarifying questions, seek truth, provide perspective, and focus on constructive solutions. The key is to validate feelings without validating facts, remove disparaging language, and redirect conversations toward productive outcomes rather than allowing negative venting sessions.
Manager.dev·1yThe victim trap of engineering managers
Engineering managers often fall into the drama triangle during conflicts or stressful situations, taking roles such as victim, villain, and hero. This mindset can prevent effective problem-solving and keep teams in reactive loops. To avoid this, managers should recognize when they are in a victim mindset, try to understand the perspective of others involved, and focus on outcomes rather than problems. Shifting from a victim to a creator mindset can lead to proactive improvements and better overall team performance.
Manager.dev·1y5 Powerful Persuasion Methods for Engineering Managers
The post details five persuasive methods for engineering managers to enhance decision-making and consensus-building: Nemawashi, Decoy Pricing, Reverse Psychology, LMDTFY (Let Me Decide That For You), and Engineered Serendipity. It provides real-life examples from a former Google Engineering Director showcasing how these techniques can be applied in managerial roles to influence stakeholders, optimize resource allocations, and improve collaboration within teams.
Work Chronicles·47w(comic) Build vs Buy
A comic exploring the classic dilemma faced by development teams when deciding whether to build custom solutions internally or purchase existing third-party tools and services. The comic likely illustrates the common considerations, trade-offs, and decision-making process that engineers and managers encounter in this fundamental software development choice.