
Lessons from Kellan Elliott-McCrea
Kellan Elliott-McCrea has served as CTO of Etsy, VP of Engineering at Dropbox, and an architect at Flickr. These lessons focus on his approach to engineering leadership, software systems and team culture. — Kellan Elliott-McCrea — About.
Part 1: On Engineering Culture and Organization
- On Culture as Celebration: Choose rituals deliberately: what a team celebrates signals its values. Friday wins can make shipped work and cross-functional contributions visible. — Friday Wins.
- On Modern Software Development: Treat software development as an operational task: create shared direction, support sound technical decisions, and make progress measurable. — FAQs from Coaching.
- On Misaligned Teams: Before blaming effort, check whether the team understands its goals. Unclear goals can produce micromanagement and erode ownership and trust. — FAQs from Coaching.
- On Push and Pull: A mandated process also needs demand for its output. Ask who needs the result and how they will use it. — Push and Pull.
- On Generative Culture: Build trust by sharing information and learning from failures instead of treating outages as occasions to punish people. — Five Years — Building a Culture and Handing It Off.
- On Questioning Practices: Revisit inherited practices: assumptions formed around individual programmers may not fit the collaborative work of modern software teams. — Five Years — Building a Culture and Handing It Off.
Part 2: On Management and Leadership
- On the Management Trap: Managing engineers requires deliberate work on team goals, capacity, feedback and working conditions; technical competence alone does not cover those responsibilities. — Advice for a New Manager.
- On Getting Comfortable Not Knowing: Leadership requires tolerating uncertainty. Admitting what you do not know leaves room for others’ expertise. — The Omniscience Expectation.
- On the Omniscience Expectation: Expecting leaders to know every detail can cascade through a hierarchy, rewarding trivia and discouraging honest uncertainty and learning. — The Omniscience Expectation.
- On Seagull Management: Swooping in with decisions can disempower a team. Account for your limited context and build trust before overriding its judgment. — Why Leaders Disempower Teams.
- On Leading with Curiosity: Lead with curiosity: ask how colleagues reached a conclusion, listen to their reasoning, and explore what would change their minds. — First Round — How to Supercharge Your Engineering Org.
- On Caring and Detachment: Care deeply about the work without assuming you can control the whole system. Emotional detachment can help prevent burnout and micromanagement. — First Round — How to Supercharge Your Engineering Org.
- On Annual Planning: Use planning to synchronize commitments and expose tradeoffs. Reduce complexity and attempt fewer things rather than aggregating every team’s wish list. — How to Plan.
- On the New Manager Path: Define team success, make near-term goals clear, and invest in the skills and working conditions needed to sustain delivery. — Advice for a New Manager.
- On Building the Team: Treat recruiting and developing the team as substantial ongoing work, not a small interruption to the real engineering job. — FAQs from Coaching.
Part 3: On System Architecture and Scaling
- On Sharded Architectures: In his 2012 Etsy presentation, Kellan describes distributing objects across MySQL shards by key to spread database load. — Architecting for Change — QCon New York 2012.
- On Master-Master Replication: His Etsy example uses master-master pairs, assigning objects to a side and allowing in-place schema upgrades without promoting a replica. — Architecting for Change — QCon New York 2012.
- On the Trouble with Polling: For data streams at extreme scales, Kellan and Evan Henshaw-Plath explored XMPP publish/subscribe as an alternative to repeated polling. — Beyond REST? Building Data Services with XMPP.
- On Data Federation: In Etsy’s design, an index maps objects to shards and the application’s data-access layer handles backends, rather than relying on SQL joins. — Architecting for Change — QCon New York 2012.
- On Global ID Generation: Flickr’s engineering account describes dedicated MySQL ticket servers generating globally unique IDs, with separate even and odd sequences avoiding collisions between servers. — Flickr Engineering — Ticket Servers.
- On Data Ownership: In his 2010 essay, Kellan argues users should be able to export all their data at high fidelity within a reasonable time. — Minimal Competence — Data Access and Ownership.
- On the Illusion of Correctness: Treat development as continuing learning: changing circumstances make confidence, experimentation and adaptation more useful than believing a design is permanently correct. — Five Years — Building a Culture and Handing It Off.
- On Aspirational Complexity: Avoid adopting architecture because it resembles a prestigious company’s stack. Extra components bring complexity even when they solve no immediate problem. — Software and Its Discontents — An Explosion of Complexity.
- On the Easy Part of Software: Writing code is only one part of software work; making a useful system also involves people, organizations and their ability to change. — Code Has Always Been the Easy Part.
- On Shipping and Learning: Shipping exposes assumptions to reality. Small changes and feedback make it possible to learn while developing the product. — Five Years — Building a Culture and Handing It Off.
Part 4: On Continuous Deployment and Operations
- On Blameless Post-Mortems: Use incidents to understand how the system failed and what to improve, rather than making an individual the explanation. — Five Years — Building a Culture and Handing It Off.
- On Detection over Prevention: Design for recovery as well as prevention: instrument the system and shorten the time needed to detect and respond to failure. — Architecting for Change — QCon New York 2012.
- On Continuous Deployment: Make small, frequent production changes so their effects are easier to observe, learn from and recover from. — Architecting for Change — QCon New York 2012.
- On Config Flags: Use feature flags to separate deploying code from exposing a feature, with controlled rollouts to staff, a small audience or beta users. — Architecting for Change — QCon New York 2012.
- On Global Optimization: Optimize shared tools and ways of working for the whole team, not isolated demonstrations of individual brilliance. — Five Years — Building a Culture and Handing It Off.
- On the Reality of Technical Debt: Necessary maintenance is normal work. Calling it debt can obscure the problem and unfairly disparage the people who built the system. — Towards an Understanding of Technical Debt.
- On Dependencies Resisting Change: An aging dependency can block upgrades across a stack. Diagnose the constraint without assuming the original choice was irresponsible. — Towards an Understanding of Technical Debt.
- On All Code as Liability: Kellan credits Peter Norvig’s view of code as liability: changing needs can make yesterday’s correct implementation tomorrow’s obstacle. — Towards an Understanding of Technical Debt.
Part 5: On Managing Up and Communication
- On the Myth of the Apolitical Engineer: Engineering does not sit outside human organizations. Collaboration, coordination and relationships are part of the work, not distractions from it. — InfoQ — Getting Real About Managing Up.
- On the Nature of Managing Up: Make it easier for your manager to support you: understand the relationship as a working partnership rather than a contest for control. — InfoQ — Getting Real About Managing Up.
- On Manager Skill Gaps: In his 2019 talk, Kellan argues that demand for engineering managers outstripped experience, making support from individual contributors especially valuable. — InfoQ — Getting Real About Managing Up.
- On Studying Your Manager: Understand your manager’s responsibilities, incentives and strengths. Ask how they are evaluated rather than guessing what matters to them. — InfoQ — Getting Real About Managing Up.
- On Upward Alignment: Align on priorities and prepare your manager to explain your work accurately to the people they answer to. — InfoQ — Getting Real About Managing Up.
- On Moving Past Status Updates: Go beyond a dump of status details: identify where you need help and build a relationship that supports useful two-way feedback. — InfoQ — Getting Real About Managing Up.
- On Communication as a Core Skill: Treat communication as a skill to develop. As a company grows, the approach that once created clarity may stop working. — First Round — How to Supercharge Your Engineering Org.
- On Isolation vs. Collaboration: Do not choose architecture merely to avoid colleagues. Shared understanding and willingness to collaborate still matter when work crosses team boundaries. — First Round — How to Supercharge Your Engineering Org.
- On Legibility of Work: Make your work legible: communicate what matters in a form your manager can use, not just a stream of technical detail. — InfoQ — Getting Real About Managing Up.
Part 6: On the Reality of Modern Software Development
- On the End of Cheap Money: In January 2023, he argued that abundant funding had concealed organizational inefficiencies that became harder to ignore when financing tightened. — Software and Its Discontents — Part 1.
- On Rising Standards: Higher expectations for security, accessibility and other baseline capabilities add work even as development tools improve. — Software and Its Discontents — An Explosion of Complexity.
- On the Explosion of Choices: Each additional technology brings training, maintenance and integration costs. A coherent stack of familiar tools can reduce that burden. — Software and Its Discontents — An Explosion of Complexity.
- On the Loss of Magic: In his 2023 analysis, startups faced mature technology-native competitors, making earlier forms of small-team leverage harder to repeat. — Software and Its Discontents — The Magic.
- On Rising Talent Costs: In his 2023 analysis, rising engineering costs made it harder for startups to find a path to success. — Software and Its Discontents — The Magic.
- On Changing Labor Relations: His 2023 account describes friction among executives, managers and engineers over productivity and workplace expectations, alongside pandemic-related strain. — Software and Its Discontents — Part 1.
- On Soul-Sucking Code: Unfamiliar code can create fear, confusion and exhaustion. Address that emotional burden instead of treating every complaint as a purely structural defect. — Towards an Understanding of Technical Debt.
- On Operability Choices: Unreliable releases, weak monitoring and missing operational tools can discourage change. Diagnose these as operability problems rather than one undifferentiated debt. — Towards an Understanding of Technical Debt.
- On Unnecessary Modularization: Both too little abstraction and excessive modularization can resist change. Judge the design against the work the code now needs to support. — Towards an Understanding of Technical Debt.
Part 7: On Diversity and Team Building
- On Inclusive Environments: In Kellan’s view, diverse, kind teams who care about one another are better placed to build good software. — Five Years — Building a Culture and Handing It Off.
- On Interviewing: Interviews provide limited information and are only one part of hiring. Do not mistake a polished interview process for the whole recruiting system. — FAQs from Coaching.
- On the Candidate Experience: Design interviews with the candidate’s experience in mind, recognizing how little a short evaluation can reveal. — FAQs from Coaching.
- On Culture Driving Technology: Culture shapes technical choices by giving a team shared assumptions about how to build and how to handle uncertainty. — Five Years — Building a Culture and Handing It Off.
- On the Value of Empathy: Empathy helps people understand colleagues’ perspectives and collaborate across team boundaries, especially where their work depends on one another. — First Round — How to Supercharge Your Engineering Org.
- On Building Learning Organizations: Make failure cheap enough to learn from: combine trust with measurement, testing and review of incidents. — Five Years — Building a Culture and Handing It Off.
- On Diversity as a Strategy: Etsy’s approach included longer opportunities to work with candidates and visible support for participation, rather than relying on goodwill alone. — First Round — Etsy’s Engineering Diversity Approach.
- On the Team as the Unit of Delivery: Treat the team as the unit of concurrent work. Adding parallel teams also adds communication and coordination costs between them. — First Round — How to Supercharge Your Engineering Org.
Part 8: On Artificial Intelligence and the Future of Coding
- On the Falling Cost of Code: Cheaper code generation moves pressure elsewhere in the system, with code review often becoming an early bottleneck. — Socialize the Plan.
- On the Skepticism of Code Review: He questions relying too heavily on code review for confidence, drawing on skepticism within his own circle and pointing to other safeguards. — Socialize the Plan.
- On AI-Assisted Code Review: His team was not ready to abandon code review. Discussing plans earlier can preserve shared understanding while changes are still inexpensive. — Socialize the Plan.
- On Agentic Coding: His vacation experiment showed him a workable mobile coding workflow, after a more cumbersome remote-server setup proved frustrating. — Coding and Blogging on Vacation.
- On Bushy Codebases: Generating code does not remove the work of making a codebase coherent, legible and sustainable for people who will maintain it. — Canonization and the Overhang.
- On Adapting Leadership for AI: Adapt engineering leadership to cheaper code while keeping people, agency and the wider software system in view. — Code Has Always Been the Easy Part.
- On the Illusion of AI Understanding: Working code is not the same as shared understanding. A team still needs to understand what it can reuse, modify and maintain. — Canonization and the Overhang.
- On the Velocity Shift: The person directing an agent remains responsible for the result. Plan verification before collaborators inherit a large volume of generated code. — Socialize the Plan.
- On the Future of Engineering Work: Engineering work includes turning a useful one-off solution into something other people can understand and build on, not merely producing code. — Canonization and the Overhang.