Find resources to solve your technical leadership challenges
Lullabot's six engineering values prioritizing people, inclusivity, learning, balance, future-thinking, and joy
Medium's engineering values emphasizing personal growth, mentorship, diversity, and pursuit of greatness
Amazon's 16 leadership principles that guide decision-making and define company culture
Why solving cultural problems with technology makes dysfunction worse, not better
HubSpot's culture deck outlining seven core principles for building a company people love
Analysis of brilliant but toxic engineers and their destructive impact on team dynamics and productivity
Why fundamental principles outlast tools and processes for sustainable professional growth
Key practices and behaviors that enable teams to perform at their highest potential
Why organizational culture is more fundamental to success than strategic planning
Design patterns for managing up and professional communication in challenging workplace situations
Successful engineering cultures share clear mission, psychological safety, data-driven decisions, and relentless learning-key habits leaders can adopt to boost performance.
Six proven strategies for engineering managers to maintain technical credibility and combat skill decay
Curated collection of research that provides evidence-based perspectives on overhyped topics in technology
Spotify's proven strategies for successful large-scale technology migrations using carrots, not sticks
Balancing the benefits of using multiple programming languages with the costs of complexity in resource-constrained startup teams
Warning signs that your system rewrite is doomed including lack of clear success metrics, underestimating migration complexity, and stakeholder misalignment
Warren Buffett's annual letters to Berkshire Hathaway shareholders containing investment philosophy and management principles
Amazon forced a company-wide service-oriented architecture exposing scaling, ops, and communication pain points, showing why platform thinking matters and why Google still lags.
Doug Turnbull: juniors force knowledge sharing, bring fresh perspectives, improve psychological safety, and prevent organizational stagnation
Will Larson on extracting actionable insights from cultural surveys: segment data, identify patterns, focus on fixable problems
Aleix Morgadas: work within existing culture to achieve goals first, then incrementally shift toward 'adjacent possible' changes
Will Larson argues strategy always exists even if unwritten - writing it down enables debate, evolution, and organizational learning
Essential soft skills for tech leaders: emotional intelligence, active listening, empathy, and mastering your own psychology first
Fly.io's humorous take on SOC2: it's essentially 'a series of screenshots' proving compliance - weak signal but customer requirement
Brian Krebs explains security.txt - a standard file that helps security researchers report vulnerabilities to your organization
Middle managers feel squeezed like a toothpaste tube; the article shows how to pick a single role (player or coach) for a set period, communicate it, and regain focus without burning out.
Stripe's comprehensive playbook for scaling engineering teams from startup to enterprise, based on their growth experience
Strategies for maintaining engineering culture, quality, and velocity while rapidly scaling teams and systems
Google's design doc philosophy: solve problems early, document trade-offs, achieve consensus - 10-20 pages focusing on 'why' not 'how'
A concise process for proposing and gaining consensus on design changes in Apache Geode, outlining RFC lifecycle, review deadlines, and how to handle superseded or dropped proposals.
Gergely Orosz's framework for using RFCs to increase visibility, spread knowledge, and create accountability in scaling engineering organizations
Zapier's comprehensive remote work playbook covering everything from automation to management across their 800+ person distributed company
Increment's comprehensive framework for building successful distributed teams through intentional communication, coordination, and culture
Remote teams at Zapier and beyond cut email overload, pick the right tools, flex schedules, skip commutes, cancel meetings, and think before sending to dramatically increase work speed and focus.
Apple's alternating strategy of revolutionary redesigns followed by incremental refinements in product development cycles
Google's crisis management approach where teams drop everything to intensely focus on solving existential problems through parallel solutions
Fabian Zeindl's hierarchical framework prioritizing build performance and testability as foundations for sustainable feature development
Shai Yallin's balanced perspective arguing that while estimates have limited value, some estimation practices can improve team collaboration
Hacker News community wisdom on defending estimates, managing pushback, and communicating technical complexity to non-technical stakeholders
Shubhro Saha's practical techniques for extracting more accurate estimates through informal questioning and confidence tracking
Honeycomb's approach to replacing unreliable time estimates with flexible delivery rhythms and graduated planning cycles
Gergely Orosz's pragmatic case for estimation as a tool for focus, stakeholder trust, and continuous improvement despite inherent challenges
Ben Kuhn's battle-tested approach: focus intensely (6+ hours daily), maintain detailed victory plans, run fast OODA loops, and overcommunicate
Jason Fried's guide to rescuing failing projects: reduce scope, clarify ownership, communicate honestly, and focus on shipping something valuable
Kevin Sookocheff's guide bridging the gap between engineering and project management with practical frameworks and techniques
Lucas F. Costa uses Little's Law to prove limiting work-in-progress dramatically improves cycle times and team predictability
Team autonomy and clear ownership matter more than any specific project-management framework; choosing the right workflow and empowering engineers drives faster delivery and higher satisfaction.
Arbitrary deadlines force engineers to deliver 'Something™ by the Date™' creating chaos and features nobody wants - try parallel experiments instead
The stdlib collection is a community-curated library of practical, immediately useful, battle-tested resources for technical leadership. Each resource is designed to be immediately applicable to your role. New resources are added based on community feedback and emerging best practices.