<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Camille Fournier on Medium]]></title>
        <description><![CDATA[Stories by Camille Fournier on Medium]]></description>
        <link>https://medium.com/@skamille?source=rss-12421a4f856------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*J2fWNTyPbgEhIyvVIjHAXg.jpeg</url>
            <title>Stories by Camille Fournier on Medium</title>
            <link>https://medium.com/@skamille?source=rss-12421a4f856------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:41:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@skamille/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[A sidebar on Code Review]]></title>
            <link>https://skamille.medium.com/a-sidebar-on-code-review-e75438fdfa5d?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/e75438fdfa5d</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Fri, 30 Oct 2026 22:40:18 GMT</pubDate>
            <atom:updated>2026-10-31T16:57:21.096Z</atom:updated>
            <content:encoded><![CDATA[<p>My favorite way to troll some of my friends is to talk about how much I hate code review. Some of my colleagues might be surprised to hear this, because I’m often tasked with making sure that we are doing it “correctly”, but I have never been a huge fan and worked without mandatory code review for many years early in my career, with no particular ill effects.</p><p>The obsession with code review post late 2000s is in my opinion a confluence of several factors:</p><ol><li>Microsoft+Google cultures influencing the tech industry</li><li>Github and OSS culture influencing the tech industry</li><li>Sarbanes-Oxley and other regulations requiring certain guardrails that are most trivially satisfied via code review (nb: I think that at least SOX might be nearly impossible to satisfy without code review, but I’m willing to be proven wrong!)</li></ol><p>Everyone carbon copied big tech and/or OSS, and then layered on just-so stories about how code review is good for teams, whether for cultural cohesion, knowledge sharing, preventing bugs, or what have you (my pet theory is that this mostly satisifes the control freak urges in many engineers to protect themselves from the mistakes of others, as I have used it for this very purpose). I have never felt motivated to fight this perception other than trolling my friends, so for years it’s just been a sign of my old age that I even remembered working professionally in the days before.</p><p>Until now.</p><p>Now, everyone hates code review. We’re producing code faster than we can review it, and so at best people are giving cursory glances to changes, more thoughtful inspection of the weirder ones, and other than that, “LGTM.” We all know that we can’t sustain this, so what now?</p><p>I expect that anyone trying to (safely) do no-human code review is already performing some amount of agentic code review on the changes. Those who are trying to someday pass a bar that includes SOC2 auditors are creating in more rigorous checks that roughly mirror what we did back in the bad old days. That is to say, we have to put some judgement into the system to know when to require review. That judgement might look like:</p><p>Is this person on the team or are they drive-by committing?</p><p>Is this person a solid senior engineer trusted with the code?</p><p>Is this a particularly sensitive area of the codebase?</p><p>Does the author think they should have more eyes on the change?</p><p>The first two areas still hold. Drive-by commits are more dangerous (especially if the person driving the agent that wrote the code doesn’t have to be on-call for the consequences!). Newer people to the code base and earlier career engineers are arguably also more likely to make mistakes they can’t catch themselves. These should immediately create higher risk scores, even though they may not always trigger manadory review.</p><p>Additional risk scoring agents can trigger human code review even when a trusted, senior person is driving the change. The risk agents can ask questions like, is this in SOX scope? Do not pass go, do not LGTM. Is this in critical performance section, and do we feel the testing regresses it appropriately? If not, flag to review. Over time, you can perhaps use signals like “changes to this section have caused many outages in the past, so it’s risky.” Creating more systematic judgement that can be applied to all changes will let us flag the right things for human eyes.</p><p>Of course, there should always be the option for the human to know that they want and need more human eyes on the code. I’m not yet ready to give up on human intuition entirely, and a change that is otherwise deemed likely-safe that the human driver flags as needing review is a signal worth following up on.</p><p>People in startups are probably rolling their eyes at me right now, of course, you’re already doing this. Not all of us have the luxury of starting from scratch, and undertaking this transformation in a non-startup environment is going to be a change management exercise. This may feel painfully slow to the engineers eager to get the bottleneck removed, but then again, if you’re at a non-startup, you may have more to lose by getting it wrong. Bringing the people from security, compliance, audit, etc, along is part of the job at this stage.</p><p>Take inspiriation from the startup of 20 people, but have patience; making this work for a team of hundreds or thousands will be worth the effort. And please share what you learn along the way, because we’re all figuring this out as an industry, together, and I want to hear about it! And remember: auditors have no sense of humor, so don’t think you can pass an audit through cleverness alone.</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e75438fdfa5d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Manager’s Path in the Age of AI]]></title>
            <link>https://skamille.medium.com/the-managers-path-in-the-age-of-ai-279cb6611d66?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/279cb6611d66</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Sat, 19 Sep 2026 18:12:33 GMT</pubDate>
            <atom:updated>2026-09-21T02:22:23.994Z</atom:updated>
            <content:encoded><![CDATA[<p>This week, I gave a talk at <a href="https://leaddev.com/leaddev-new-york/">LDX3 New York</a>. When they asked me to speak and asked me for a topic, I said that it was probably time I finally give a talk on what AI means for management. Of course, this was back in April, when I figured surely I’d have it all figured out by September. Then the conference organizers did me an unexpected favor: they wrote the title of the talk, forcing me into a framing that narrowed the scope enough to write something coherent. Below is not exactly a transcript of what I said.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*32LP8iirLzUIZrJJrQS7lA.png" /></figure><h3>Framing: A lot of people want management dead</h3><p>The talk started with 3 quotes from tech CEOs that have proclaimed the massive reduction and likely end of “management.”</p><blockquote>“There is no need for a permanent middle management layer.” — <a href="https://block.xyz/inside/from-hierarchy-to-intelligence">Jack Dorsey</a></blockquote><blockquote>“I don’t think people managers will have any value in the future.” — <a href="https://podcasts.apple.com/us/podcast/brian-chesky-ai-founder-mode/id1154105909?i=1000766196703">Brian Cheskey</a></blockquote><blockquote>“No pure managers: Every leader at Coinbase must also be a strong and active individual contributor.” — <a href="https://x.com/brian_armstrong/status/2051616759145185723">Brian Armstrong</a></blockquote><p>To me, these are ideas from sci-fi futures. They don’t represent a realistic understanding of the world we live in today. There are many sci-fi futures people are thinking about: massive reduction of people employed by the tech industry, the death of knowledge work overall, cybernetic AI panopticon overlords, post-scarcity, data centers in spaaaccee, and of course, AI literally and completely replacing the need for any human managers.</p><p>I can’t write a talk about sci-fi futures, because I’m not a futurist, and there is no manager’s path if management is dead anyway, so instead, I will focus on the actual work of 2026.</p><h3>The Manager’s Path in 2026</h3><p>I don’t think I’ve ever given a talk that is just about “The Manager’s Path”, partly because there’s a lot of stuff in the book, and partly because, well, I started a new job right after it was published and stopped speaking for a bit. This talk forced me to boil the book down to a few recurring themes of focus areas for managers; namely, Technical Skills, Signal Processing, and People Skills. What are these things and how have they started changing with the current state of AI?</p><h4>Technical Skills</h4><p>Why do we care about technical skills in management? Because a lot of what we call “management” is in fact a risk management function. The manager is responsible for, among other things, making sure the work gets done, at reasonable quality, in reasonable timeframe, without causing so much personnel strain that people constantly quit. When building software systems, it’s hard to really know how long something should take, and what good looks like, if you don’t have any experience building this sort of system yourself. It’s not impossible, sure, but it’s hard. It’s easier for someone with background to manage a lot of the risks than it is for someone who has to delegate that judgement entirely.</p><p>But of course the act of creating software has changed a lot, very quickly. Nowadays engineers increasingly direct agents to produce the software rather than directly writing it line by line themselves. And the speed at which you can end up with a seemingly-complete piece of software is consequently significantly increased. This has led to a lot of weird outcomes that we’re trying to manage:</p><ol><li>People are really obsessed with productivity, and not just CEOs/Execs; individual engineers are also really addicted to the new speed and impatient to make it work for them</li><li>The amount one person can do by themselves is a lot higher, so we have to completely revisit our intuitions about how to break up work to account for this increased capacity per individual</li><li>Other risks are looming thanks to this, some related to speed, others related to the technical capabilities of AI: security risks is a big one, but also the question of managing the quality of the systems being built this way over time to ensure they are maintainable.</li></ol><p>This change is the most obvious and the one that I suspect the industry is most well-equipped to figure out over time, even though it will be bumpy in the interim. A lot of the conference was dedicated to people sharing lessons about managing some of this transition, and I suspect most people reading this are thinking about this actively. Sorry, I don’t have magical solutions to offer here except that we all need to keep experimenting and sharing what we learn through the transition.</p><h4>Signal Processing</h4><p>Ok so this is a big one. First of all, what do I mean? I mean things like diagnosing problems, debugging teams, making decisions in the face of ambiguity. How good are you at not just getting information but getting the right information in order to make the best decisions?¹</p><p>We start with another Jack Dorsey quote:</p><blockquote>Companies move faster or slower based on information flow. Hierarchy and middle management impede information flow.</blockquote><p>The idea that many of these management doomsayers are building on is that AI can provide essentially a cybernetic mechanism for overseeing organizations that allows information to pass through computers, create signals, and inform far fewer decision-makers than current organizations because (waves hands).</p><p>And it is true that in some ways AI is a leap forward in visibility. If you produce digital artifacts of your work (aka stuff that can be consumed by the AI), someone with access to those artifacts can ask “what has Jane been working on the past week” and get a reasonable starting point answer. <em>(Aside: I urge you all to turn your favorite internal AI on yourself and review the answer, to level set in the quality of the response.)</em> I can believe that this visibility helps managers of individual contributors get a valuable starting point for their 1–1s that could allow them to spend less time on pure status updates and more time going deeper into what is happening.</p><p>But how well does it actually improve understanding? My experience is that when you ask these questions about things that span more than an individual, the answers start to get less useful, to the point that they lead to questions and clarifications with individuals that take as long as it would’ve taken to ask the humans for updates in the first place. And while perhaps those who try harder can make this work better than I have, I also know that my asking the leaders is training them to think about what is important, and focus their own attention on understanding the work of their teams and the justifications for that work. This is quite important in keeping a well-running and well-aligned organization.</p><p>Furthermore, we have a problem that reliance on AI tooling may be inhibiting the development of <strong>situational awareness</strong>. You know, your ability to read the room? A lot of information is carried in non-text formats. Body language, tone of voice, camera on, camera off, the things said and the things left unsaid. Maybe AI will read our minds someday (creepy), but I suspect many of us are starting to lose those subtle situational awareness signals because we are tuning out in meetings where we are relying on AI to do all of the note taking and transcription for us. Similarly, relying on summaries even of digital artifacts means that we are trusting that the algorithm has highlighted the important details we have to know, but it is necessarily stripping out some amount of information that might actually encode useful signals we might want to be aware of.</p><p>All of this culminates in the challenge of AI and <strong>decision-making</strong>. You can use AI to get visibility to assist decision making; when writing a performance review, giving the AI a competency matrix and a person’s name and asking for work they’ve done over a time period against this matrix can be useful in reminding you of things you may have forgotten, combatting recency bias. But the minute the AI starts to write that performance review, it’s starting to decide for you whether you think it is or not. AI writing is compelling, it draws your thinking in a direction, and it’s hard to fight that pull. And this undertow is dangerous.</p><p>Why? Machines cannot be held accountable, so they cannot make management decisions, to paraphrase the immortal words of IBM circa 1979. I once got a performance review from a boss who basically just copy-pasted my own self review in and called it a day. Now, I wrote myself a nice review, I got a good score on this review, but was I happy? No! I was terribly disappointed that my boss showed I was worth so little time and attention, that he had basically nothing to add. It made me lose trust in him immediately. When you make management decisions, and yes, your performance reviews are management decisions, you need to be able to stand firmly behind them and own their consequences. Could you defend every word the AI wrote in the review? If so, ok. But for most of us, to get to that point of certainty, we need to do the writing ourselves, to force the thinking, analysis, and decision-making.</p><h4>People</h4><p>Finally, we come to people. This one is just depressing. Has AI made anything easier about the people management/people skills era? If it has, it has been swamped by all of the new interpersonal challenges we’re hitting thanks to AI.</p><p>To start, there’s the increased expectations. Many companies think that that increased visibility and <em>waves hands</em> AI productivity means managers can start to manage far larger teams, with no help coming as we reduce managers and don’t hire new ones. And of course, some companies are also expecting managers to write code because that is apparently the only individual contribution that matters (the idea that managers don’t make valuable individual contributions to companies is so mind-boggling I could write a whole additional piece on it). And while you’re doing this, you have to manage the AI transition: make sure your team is using AI enough, not too much, and soothe their anxiety, and deal with their impatience, and you too have to use it but no one is bothering to teach you how to use it well or soothe your anxiety, you are just expected to figure it the f* out.</p><p>So is it any wonder 1 in 3 managers are considering going back to individual contribution roles? Hell, if you’re going to ask me to write code and manage a huge team of people, I might just prefer to say, thanks, writing code is enough for me so I’ll go back to doing that.</p><p>And these are not all the people challenges! Have we mentioned the politics? Oh my god, the politics. Who is supposed to build what? Do organizational boundaries matter? “Working code wins” was a useful mantra for a long time; if someone wrote code to solve a problem, it was a sign they were really willing to put in some elbow grease and effort, they cared a lot, they had a strong opinion. This didn’t always lead to great outcomes, but it was a useful signal that whoever wrote that code cared. Nowadays? Code is cheap. Someone gets slightly annoyed that they might have to think about another pre-existing system they didn’t build and decides to just build their own, and btw, now this should be our team’s responsibility and ownership. Managing through these politics, bad feelings, and frustrations is no fun at all.</p><p>AI has corrupted the cultural channel at work. When humans write code, they think about who owns what, where the systems they want to use reside. Conway’s Law is both an observation and something useful for humans: I know that if I work on a team, I work on certain systems, and I work closely with teams nearer to me in the org chart, and if I want to do something with work from teams farther away that may require more thought, conversation, etc. AI cares nothing for this cultural information. AI will take dependencies on anything it can see, and can quickly misuse those dependencies, without the initiating team realizing they are doing anything wrong.</p><p>And worse, AI undermines the small day to day activities that help build trust across organizations. It’s great that AI can quickly answer simple questions, and I would never suggest taking that away. But when you talk to glean, slackbot, claude, chatgpt, you aren’t talking to your colleagues. You aren’t asking them for help, and exchanging the kind of low-stakes favors that form connections; you aren’t learning their personalities and building your network.</p><h3>Depressing Interlude About The Future</h3><p>I worry that all of this gets worse before it gets better.</p><p>That our productivity obsession will combine with our general habit of rewarding performative “first to do a new thing” behavior and lack of communication.</p><p>This will cause a lot of “almost real” 80% systems to pop up everywhere.</p><p>And let’s not even talk about the potential chaos of Citizen Developers.</p><p>We’re heading towards a chaos of ungovernable fragmented systems and logic that is missed by overburdened managers, driven by the cult of productivity and the inability to differentiate visibility from understanding.</p><h3>So What Do We Do?</h3><p>If you still want to stick with management despite all of these challenges what do you do?</p><h4>Don’t regress to easy</h4><p>It’s my favorite cliche, stay outside your comfort zone, but in this era it is truer than ever. For some of you this means that you need to stop spending all of your time playing around with new ways of coding and using AI to “manage” your teams. It’s fun to learn this new stuff but your job is as much with your people as it is with the new tools, and you do no one any favors by forgetting that.</p><p>For some of you this means get your head out of the sand and get engaged. You can’t just hold this back through sheer inertia. If your company is using AI, you need to get comfortable with it so that you can help your team navigate the transition, and to avoid becoming irrelevant.</p><h4>What should we be doing?</h4><p>The important work is, of course, to make AI work with and for our teams. A lot of attention is going into the changes to workflows and processes that will make AI more successful: fixing code review, thinking about evals and new ways of testing, etc. And that’s certainly one of the most interesting technical things to spend time on and pay attention to.</p><p>But a lot of other things need to change as well, and managers need to remember that the cultural changes around policies and standards are just as important. An example of this is the <a href="https://skamille.medium.com/guidelines-for-respectful-use-of-ai-affcc85d7072">Respectful AI Policy</a> work I wrote about a few months ago. Teams need guidance on how they will work together with AI, and show up to work when they have AI available, and this is something that managers and leaders should provide.</p><p>I mentioned earlier that I’m concerned with our ability to develop situational awareness in the face of all of these note takers and summarizers that encourage us to tune out and favor getting the cliff notes over the details. The way to combat this is the same as it always was: you have to follow up on surprises. Writing that <a href="https://skamille.medium.com/guidelines-for-respectful-use-of-ai-affcc85d7072">Respectful AI Policy</a> came from me talking to leaders in one of my teams and hearing their frustrations. I will admit I was surprised! I figured surely people wouldn’t just send slop over to their colleagues or tune out all the time, but of course that was me overestimating human nature a little bit. No one catches every important detail, and you may risk missing more if you rely on AI, but if you follow up on the surprises that come out of this you have the chance to both fix the mistakes and identify areas to follow details more closely.</p><h4>Remember the Goal</h4><p>My final idea for managers navigating this new world is to remember that we’re trying to take advantage of tools that provide incredible individual productivity while maintaining and even improving team coherence. This means cooperation and trust matters; how can we help pre-empt and navigate the inevitable turf wars coming from cheap code everywhere?</p><p>My suggestion is one that I suspect some will dislike: I think you actually need to spend <em>more</em> time talking to people. You’ve got all of these productivity enhancers, and they are driving everyone in the organization to move very fast. It was never easy to keep up with the pace of work, but now, one person on the team can produce as much code as several people, in a very short timeframe. When you have multiple people you’re trying to keep track of (let alone multiple teams!) I am not sure that even the best summarizations are going to catch the ways these individuals and groups can drift off in different directions and start to lose alignment and coherence.</p><p>We should be spending some of our productivity gains on things that seem like slowing down: meetings, design reviews, conversations. These ways of maintaining alignment, sharing knowledge, and creating human connections are, in my opinion, more important than ever to creating good outcomes at scale.</p><h3>Coming Back to 2026 and Concluding</h3><p>Back in 2026, what’s happened recently?</p><p>Well, Meta just (as of ~9/13/26) rolled back some of its most aggressive management reductions, recognizing that there were a lot of bad outcomes that came from going to a normal number of managers to ratios of 40:1 or 50:1.² So I think that perhaps we are not in fact ready to drastically reduce management and maintain high performing organizations.</p><p>I wanted to end the talk with a different quote, from my friend <a href="https://harper.blog/2026/08/15/fugue-state-love/">Harper Reed</a> who spoke recently to a group of high school students and among other things said this:</p><blockquote>Always ask: “Who has power in this system?”</blockquote><p>When someone tells you how a system works, ask who benefits from you believing that version.</p><p>Now, the quotes I started this talk with were from incredibly successful tech CEOs, and they clearly are trying to sell us a future where management doesn’t matter, where many of us may even basically work for computers. There are many powerful people in the world who want to sell us the idea that humans don’t matter in the future, not really. But I want everyone listening to this talk to remember this:</p><p><strong><em>You have power too. You are part of the system, you are building the system, you can make things better or worse based on your choices and your behaviors and how you show up as a leader.</em></strong></p><p>You must reject the hopeless messaging that paints the demise of you role as inevitable, that paints us as powerless to shape the future.</p><p>And, importantly: this will only work if you talk to humans more than you talk to Claude.</p><p>So I hope that everyone listening to this talk will join me in staying curious, engaged, and committed to making AI work for humans. Working together, we will chart the next path.</p><p>Thank you.</p><p>¹There’s a lot I didn’t say here; I really wanted to quote a lot of things from <a href="https://knightcolumbia.org/content/ai-as-social-technology">AI as Social Technology</a> by Henry Farrell and Cosma Shalizi, various bits of wisdom from Peter Drucker’s writing, and a few things from my friend and occasional collaborator <a href="https://medium.com/@arthegall">Tim Danford.</a> Somehow only Tim made it to the final edit, contributing the ideas about AI corrupting the cultural channel, and even that was me indulging myself a little bit.</p><p>²<a href="https://laughingmeme.org/2026/09/14/managers-are-catalysts.html">https://laughingmeme.org/2026/09/14/managers-are-catalysts.html</a> for more tidbits and related good ideas</p><p>I’d be remiss not to thank a laundry list of people for contributing indirectly to this talk, but it’s literally so long I fear leaving too many people out. If I talked to you about AI and management in the past 6 months, know that you were in my mind as I was writing, and I genuinely appreciate it.</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=279cb6611d66" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Guidelines for Respectful Use of AI]]></title>
            <link>https://skamille.medium.com/guidelines-for-respectful-use-of-ai-affcc85d7072?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/affcc85d7072</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Sun, 31 May 2026 16:34:01 GMT</pubDate>
            <atom:updated>2026-05-31T16:39:50.759Z</atom:updated>
            <content:encoded><![CDATA[<p>As companies adopt AI tools, a lot of time is spent on thinking about AI policies from a security, compliance, or even cost-focused angle. But many leaders are neglecting to address how their teams should work with AI in the context of the team as a whole. This creates a lot of unresolved tension, and it’s time for leaders to step up and set some guidelines not just for how to use AI in an “approved” sense, but how to use it respectfully.</p><p>When I say respectfully, I am not talking about the baseline appropriate workplace behavior (bullying, abuse, harassment, etc). Instead, I’m concerned that many of us haven’t considered that the ways AI can make an individual more productive (literally enabling them to produce more outputs) can have an overall negative impact on the team’s productivity. Leaders can’t just sit around and expect that their teams will know that they can’t just produce slop and send it to others; if you haven’t set up a thorough <a href="https://rfd.shared.oxide.computer/rfd/0576">policy</a> yet, here are some suggestions on what to cover.</p><h3>Elements of Respectful AI Use</h3><h4>Don’t ask someone to read/review what you haven’t read or reviewed yourself.</h4><p>This is one of the most common frustrations I hear amongst people working on AI-heavy teams. Whether it’s code that the owner didn’t really bother to understand before submitting for review, or documents that they generated and didn’t bother to read, too often people try to steal productivity from their colleagues by streamlining their production of work while asking their colleagues to do all of the quality control themselves. It’s great to have a loop of AI code generation -&gt; AI code review -&gt; AI fixes -&gt; final human review, but if the person prompting the AI doesn’t bother to review that code first, they’re putting a huge validation tax onto their teammate, who has to trust both that you prompted well AND that the AI understood the context and problem well enough to get a sustainable solution.</p><p>Documents are an even bigger temptation than code, because AI is so verbose and most of us hate writing and editing. It’s easy to get into a loop where you ask the AI some questions, skim the answers, output a document and send it to others. I’m guilty of this myself! But what makes sense when you’re skimming one answer at a time may not make for a good overall document, and there is a big difference between answering individual questions and writing for a human reader. In particular, the context that you have in your own head as you are talking to the AI may not come out at all in the document; if you don’t bother to read it thoroughly before sending it out, you won’t catch the gap in framing.</p><p>Even worse, sometimes people don’t even understand what the document they prompted is trying to say. Can you describe this document, and have a conversation about the concepts it presents with others and why it makes sense? If not, you have no business sending it along without at minimum the huge caveat <em>this is AI-generated and I still don’t really understand this space, please help me.</em></p><p>Many people have reached the point where they won’t read something a person didn’t bother to write themselves, and who can blame them when so many don’t even bother to read their output before sending it on?</p><h4>Shorter is better.</h4><p>Part of the annoyance of reviewing AI-generated work is that the AI can be painfully long-winded. AI code often looks like tutorial code, with much more verbosity than human developers would bother with. Add in the temptation to one-shot big changes rather than thinking about how to break the code down into pieces, and you can end up with stacks of thousand line pull requests. The documents AI produces are so thorough that something that should be 3 pages turns into 10 or 20. And for those who have fully embraced AI for all of their text-based interactions, you start to see the LLM-generated wall of text chat messages or emails.</p><p>This is, frankly, just rude. It goes hand in hand with not bothering to review your own work, but even if for some reason you convince yourself that you really did read and edit that giant PR/document/message, you’re still asking so much more of the audience than you probably put into the exercise in the first place. When it comes to code, I encourage you to honestly ask yourself: if this broke at 3am and none of the AI tools were working, would you be able to look at the PR context and the change and debug it? If not, it is probably too much. When it comes to a big document, at a minimum, have you at least summarized the important points up-front? If someone is just going to ask an AI to summarize the document themselves, you should probably do more work to provide that value before handing it off.</p><p>Finally, if you’re writing long-winded emails or chat messages with AI-assistance in order to painstakingly try to explain something, perhaps you actually need to have a meeting or call instead. Increasingly long text exchanges have always been a sign that people need to stop and talk face-to-face, and AI logorrhea hasn’t changed that.</p><h4>AI is not an excuse to turn off your brain, or your heart.</h4><p>Signs we’ve switched off our brains and our hearts include: not reviewing the AI-generated work, not taking the time to do human editing, not breaking the changes down into chunks, and avoiding real conversations through AI-mediated text exchange. This guidance is about respectful use of AI because if you have empathy for your colleagues and respect for their time and skills, you will show them the courtesy of giving them work that you are proud of, that you stand behind, that you have thought through and can explain. The AI may have produced a lot of the output, but you thought about all of the pieces that needed to be done, and used the extra productivity to make something better: more reliable, simpler, well tested, whatever. If you find yourself not thinking at all and just mindlessly prompting, accepting output, and moving forward, it’s a warning sign that something is wrong. Perhaps take some advice from <a href="https://vickiboykis.com/2026/05/28/we-should-be-more-tired-than-the-model/">Vicki Boykis</a> on adding friction to your development process (or whatever the equivalent is of your day to day work).</p><h3>Framing these guidelines</h3><p>If you decide to do this, one final tip from me: assuming your company has some sort of company values, it’s always a good idea to call back to these values when you create policies and guidelines like this. It’s one thing to abstractly say that shorter is better, but if you can tie that to a value for your company, it will resonate more strongly. As an example, if I were at Amazon I might consider tying “shorter is better” to the leadership principle <strong>Invent and Simplify</strong>. And since shorter is better and this is already too long, I leave you here.</p><p><em>This post is 100% human-generated except that I needed a spell-checker to spell logorrhea. Maybe I should’ve used an AI editor, feel free to tell me if you think so!</em></p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=affcc85d7072" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Revisiting Manager READMEs]]></title>
            <link>https://skamille.medium.com/revisiting-manager-readmes-b9a59167c226?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/b9a59167c226</guid>
            <category><![CDATA[readme]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[process]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Sat, 22 Nov 2025 19:02:58 GMT</pubDate>
            <atom:updated>2025-11-22T19:02:58.101Z</atom:updated>
            <content:encoded><![CDATA[<p>Several years ago, I published a critique of <a href="https://medium.com/@skamille/i-hate-manager-readmes-20a0dd9a70d0">manager READMEs</a> that succeeded in stirring up a lot of feelings, pro and con. I’d like to believe it prompted some people to reconsider whether these are actually effective tools.</p><p>Today, I want to revisit this. Not to encourage you to write a manager README, but to suggest other ways forward that I have learned in the years since writing the first post.</p><figure><img alt="readme" src="https://cdn-images-1.medium.com/max/225/0*8URkz_l2YKxEqADi" /></figure><h3>The Problem</h3><p>When you become a senior manager or an executive, you face new challenges. Your job involves directing work across many people with different approaches, styles, and opinions. Left to their own devices, each person will develop a slightly different way of communicating with you, one that works for them and that they believe works for you.</p><p>With a broad scope of work to oversee, you need to quickly grasp what matters and should be shared upward, outward, and down into different parts of your organization. Now, at most companies, this is a known problem and inevitably someone has already tried to solve it by means of standardized tooling and reporting. Everyone uses Jira for a reason and it’s not that Jira is the best tool ever, but it is malleable to many types of standardization. Companies implement OKR tools and Tableau dashboards, they institute various program management processes, they run quarterly business reviews, and all of these are done in the name of standardizing the information that is passed upward and outward so that people can make better decisions.</p><p>Unfortunately, this is typically the lowest common denominator of usefulness to any senior manager. Reporting generated in this way obscures as much as it reveals, and it rarely addresses the things that you really care about¹. So senior managers need other mechanisms for imparting what they want to hear about and see. The README can sometimes be an attempt to impart that cultural overlay: a way of saying, “I care about X, and want you to focus on that when you communicate to me; I don’t care much about Y and Z, and by the way, it’s best if you communicate with me in these ways.”</p><p>I remain steadfast that this is not a good approach. It creates a focus on you as the person to be managed up to. Your personality must be accommodated, your preferences honored. I get the desire for this, and I’m certainly not immune to being managed up to, but my preference is to avoid major blind spots. I want to hear what I care about, yes, but I don’t want to live in an information bubble either.</p><p>READMEs are also rather lazy. There’s a kernel of truth in their purpose: we want people to focus certain types of communication on what we believe is most valuable. However, doing it in the form of a general README isn’t actually the most effective approach.</p><p>So if not READMEs, what then?</p><h4>The Solution: Appropriate Templates and Ceremonies</h4><p>Instead of one doc that attempts to communicate all of your preferences and warts and creates a you-focused mindset, it’s time to level up and recognize that a big part of the job of senior/executive management is setting standards for doing certain types of work. The best way to set those standards, in my experience, is lightweight templates and ceremonies for information sharing, discussion, and decision-making.</p><p>I think that every good senior manager should have some toolkit of these. You aren’t just going to operate against the lowest common denominator of pre-existing reports and processes in your company, you have to establish a few processes that exist to show what you care about and where you want the organization to focus. One of mine is Wins and Challenges (discussed in my <a href="https://amzn.to/3MwcgGo">recent book</a>), which I’ve brought from startups to giant teams and everything in-between. Is it extra work on top of whatever people might be doing in Jira or other tools? Possibly. Does it create far more valuable conversation across my leadership team than those tools? Yes. Does it help me specifically understand things and do my job better? Absolutely.</p><p>There is a very lightweight template to follow for my Wins and Challenges, and the process details are owned by the team gathering the information (although I specify opinions about how it should be done, I only check the outcomes). I find that the best templates and processes are lightweight in a way that they show what information should be collected but don’t dictate exactly the process to collect that information.</p><p>Developing templates that expose the right useful information is hard. You will both over-do and under-do this as you’re figuring it out, whether it’s your first time in the job, you’ve moved to a different company or team, or your team has just evolved past the usefulness of the old methods. My advice is to start simple and add on new details or processes only when it’s clear you have a widespread gap. A good rhythm for a new job/team is to learn for 90 days, then introduce what you need, and evolve from there with enough time to learn from each iteration (usually, 1-2 quarters).</p><h4>Don’t Try To Template/Processify Everything</h4><p>I recently asked an experienced CPO about good product processes, and what they looked like from his perspective. One piece of advice was that not everything should have a fixed process or template. When you need to leave room for discussion, it’s often best to limit the structure; a walkthrough of a prototype might be better done as an open-ended exploration and discussion rather than a formal set of steps.</p><p>It’s important not to give into the temptation (or external pressure) to create processes for everything. I personally do not have a fixed format for my 1-1s, and dislike even the expectation of coming with a set of written and shared topics. I don’t want to feel rushed to finish everything on an agenda, and the temptation to immediately jump to conclusions about a topic based on an agenda item often increases miscommunication. Sometimes there’s a need to pre-read and prepare, but sometimes we just need to talk and see where the exploration of current top-of-mind concerns and information takes us.</p><p>So, senior leaders, you can tell people how you want them to work with you, but don’t do it via the crude mechanism of a manager README. Drive clarity through templates and processes where needed, resist the urge to create them everywhere, and lead your organization by showing them where to spend their time and focus as a collective good, not just good for you.</p><p>¹ Think of it this way, if you could easily see the problems via the pre-existing dashboards, they’d already be on their way to being solved. Dashboards are like alerts and tests in this way, they tend to catch what you know could go wrong, but rarely the surprise problems that lead to big incidents. Necessary, but insufficient.</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9a59167c226" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dude, Where’s My Strategy?]]></title>
            <link>https://skamille.medium.com/dude-wheres-my-strategy-8c86aa01729c?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c86aa01729c</guid>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[strategy]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 13:16:53 GMT</pubDate>
            <atom:updated>2025-06-05T14:26:36.871Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m working on a talk about rewriting platforms for <a href="https://leaddev.com/leaddev-london/agenda/">LDX3</a> later this month. Spoiler alert: a lot of the talk centers around why rewriting platforms is almost always a very bad idea. For more on that you can read the rearchitecting platforms chapter of my <a href="https://amzn.to/3MwcgGo">latest book</a>.</p><p>One of the points we make in the book is that, generally speaking, platform teams are not the foci of innovation at companies. Platform innovations often come either by adopting external innovations, or absorbing and expanding platform-like work that was created by internal application engineering teams for their own purposes. I won’t say that it’s impossible for platform teams to innovate, but a lot of the innovation is much more incremental and evolutionary rather than novel and revolutionary.</p><p>But this doesn’t mean that there’s no need for strategy in your platform team; on the contrary, platform teams are often the fulcrum that drives important architectural evolution across companies. Pretty much every major change in technology that I have lived through has needed platform-level support: containerization, microservices, event-driven systems, big data, continuous delivery, observability, the cloud, elastic scaling. Many build on one another through the platform, such as containerization making it easier to move to the cloud and moving to the cloud making elastic scaling more realistic.</p><p>This is what strategy starts to look like as a platform leader. You’re watching where the state of the art is going, and thinking about what makes sense to introduce or evolve so that you can take advantage of that over time. You’re not forcing everyone to move from bare metal hardware to kubernetes overnight, but you’re making the tools to support bare metal to virtualization/containers available, easy to use, and cost-effective, to encourage the natural evolution to happen. The larger the company, the longer these timelines will run, and the more that you’re going to have a number of leading and lagging strategies running, but this is the engine of baseline modernization that needs constant feeding to keep your technology stack from stagnating.</p><p>“Strategy” and “Vision” are so often conflated in peoples’ minds that this kind of boring but reliable forward progress is overlooked as strategic. But when leaders can execute in this way over years, the application/product teams have that much more flexibility and power to innovate and do interesting things without having to completely go out on their own. So, platform leaders, don’t feel bad if you’re not at the forefront of innovation! You don’t have to drive the next innovation to be strategic, you just need to make it easy for others to get there.</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c86aa01729c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Things I Currently Believe About AI and Tech Employment]]></title>
            <link>https://skamille.medium.com/things-i-currently-believe-about-ai-and-tech-employment-3e712df1dc51?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e712df1dc51</guid>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Tue, 13 May 2025 13:48:01 GMT</pubDate>
            <atom:updated>2025-05-13T13:54:36.900Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hey, I could be wrong!</h4><p>People love to ask me what I think is going to change about engineering management and technology careers given the current AI innovation boom. I am flattered to be asked, but I am not sure I have a good answer. Things keep changing so much in the space, both from real innovations (like Claude Code) and promises of near-miracles (like 90% of all code being written by AI sometime this year), it’s hard to keep up or know what’s true. So, while I have some direct experience, and I continue to collect a lot of interesting anecdotes, I think we’re still in the realm of “futurism” when trying to guess what will happen.</p><p>So, with that out of the way, here is one of my current best guesses. This is not based much on the current state of innovation, except to take as a given that AI is proving to be measurably supportive of building software. It&#39;s instead based on my understanding of economics, human nature, and the skills of people working in tech.</p><h3>So long as there are software engineers, there will still be a range of junior — mid — senior engineers.</h3><p>Some people say that AI will get rid of the need for “junior” engineers, generally taken to mean “people with some training but no full-time software engineering work experience.” Others say that AI will get rid of the middle-tier engineers, those with a few years of experience but who aren’t yet senior. And there’s probably some who think they make even very talented senior engineers obsolete, but more who just really want them to make very talented senior engineers cheaper to hire. But will either of these come to pass?</p><h4>Mostly Junior?</h4><p>It’s clear that AI has been a massive accelerator of what has been called “low-code” or even “no-code.” I know of startups that are hiring nothing but junior people to act as prompt coders, with the senior experienced tech founders overseeing. But these are very early-stage companies, with greenfield codebases. Clearly AI is making it much easier and cheaper for them to get started, and you can now build some types of software early-stage businesses without mid-career engineers. But are you going to keep these “junior” engineers junior forever? Churn them out and hire new ones the minute they develop the context understanding of your business that makes them a) more productive and b) want more money/promotion?</p><p>If you believe “junior engineer” is now in a category other than “knowledge work”, one that has a workforce that can be staffed with a lot people who need minimal training to do the job and far fewer above them to oversee the work, maybe this is true. But it doesn’t sound like we’re at the cusp of turning this job into a largely lower-skill position yet. I’d sooner believe that prompt/vibe coding becomes a skill that other knowledge workers need to have and we just have much smaller engineering teams overall than engineering shifts to primarily juniorization.</p><h4>Mostly Senior?</h4><p>Others say this means you don’t need junior engineers. By most accounts I’ve heard, AI coding tools are making a huge difference in productivity of senior engineers, which naturally slows down the demand for hiring at all. And it’s tempting to delay hiring of junior engineers, the ones that you have to invest in before they become productive, in order to take full advantage of that AI boost for the existing employees. But over time, if the jobs continue to exist, we need new entrants to our talent pool to replace leavers. Not to mention all of the other positive effects bringing new talent into a team creates. <a href="https://medium.com/@skamille/the-senior-shortcut-fadffe5503fd">I’ve written about this already, and I stand my ground</a>: if you think you will continue to need to hire engineers into the future, you should really keep hiring junior ones.</p><h4>What about engineers in-between “Junior” and “Senior”?</h4><p>So long as there are junior engineers, and senior engineers, there will be career paths with midpoint levels. The description of skills might change, the compensation potential might change, the total employment might change, but I am skeptical that one role will disappear but the other two will remain. The only alternate future I can imagine is one where you may start people as a junior engineer but then everyone specializes above that; you hire them as “analysts” and they figure out a business specialization that provides the career path rather than the technical career path. My skepticism about this “full stack business person” is that, well, most people just aren’t good at everything. We tried to get rid of just developer specialization with “full stack” roles, but at scale, this has yet to be widely successful. It turns out, specialization is valuable, and can be more valuable than being a middling generalist.</p><h4>Corollary: Will Efficiencies Kill Demand?</h4><p>So now we have to talk about what this will do to the overall demand for engineers. Will it plummet? Is the job category of “people who build software-based products” going to have the same massive decline as, say, manufacturing? It helps to know why manufacturing employment declined in the way it did. While there were many factors, we know that manufacturing got both much more efficient, and the demand for manufactured goods slowed.</p><p>Taking it as a given that AI will meaningfully improve the productivity of producing software-based products, do we think we will also saturate the demand for those products? Or will the demand continue to grow? Time will tell. The biggest AI proponents predict that efficiencies will reach some point that the AI satisfies them completely, so I guess demand doesn’t matter in that case. But I’m skeptical.</p><h4>Engineering is changing, but probably not going away</h4><p>I am not a futurist. I don’t believe yet that we are going to achieve “AGI” (whatever that means). I do believe you can, and people do, “write” a lot more code now via prompting, which is a step beyond the elaborate auto-complete copilots of even a year or so ago. How will this work over time, with many people, in increasingly complex systems? No one knows for sure, but my current bet is that specialization still matters, it still produces marginal utility, and thus the specialization of software engineering, while changing, will stick around.</p><p>No AI was used to write this post (unless you count spell check!)</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a>, <em>available on Amazon and Safari Online,</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e712df1dc51" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some Tips for Moderating a Successful Panel]]></title>
            <link>https://skamille.medium.com/some-tips-for-moderating-a-successful-panel-5ce10599623b?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ce10599623b</guid>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Tue, 06 May 2025 01:23:14 GMT</pubDate>
            <atom:updated>2025-05-06T01:23:14.851Z</atom:updated>
            <content:encoded><![CDATA[<ol><li>Write separate questions for each participant. Don’t just ask everyone the same question! It’s ok if you have one-two “lightning round”-type questions that are the same for each person, but each panelist answering the same question is boring, even when they give different answers.</li><li>Research the participants enough to tailor questions to them. Send them the questions in advance, so they can prepare; even if it’s just a few hours before the panel it’s better than springing them on them in the moment. Especially if you don’t know the panelists well! There is nothing more awkward than asking a question the person can’t answer (either because they don’t know, or worse, because they can’t talk about the topic due to non-disclosure or other limitations).</li><li>Think about the themes you want to address. It can just be 1–2, for a 4 person panel, you can probably do one question each participant/theme, for two total themes; with introductions, panelist back-and-forth, and audience questions, that usually will fill 45 minutes.</li><li>If you give them good questions, panelists will talk for a while. You don’t need a lot of questions to fill a lot of time. Do not overwhelm yourself or the panelists with long lists of possible questions.</li><li>It is tempting to talk a lot yourself. Sometimes it’s true that you are both a moderator and panelist, but make sure that’s the role you should be playing before you give an extended monologue on the topic when everyone in the audience is there to hear from the assembled panelists.</li><li>Pay active attention. Good moderators can make connections on the fly and call out interesting themes that the audience may or may not detect. You may also need to gently interrupt and move the discussion along if one panelist has gone on for a long time, or there is an extended back-and-forth between the panelists that is not productive to the conversation.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ce10599623b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[10 Years of Engineering Ladders]]></title>
            <link>https://skamille.medium.com/10-years-of-engineering-ladders-329d309000cd?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/329d309000cd</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Wed, 26 Mar 2025 15:01:24 GMT</pubDate>
            <atom:updated>2025-03-26T15:11:00.353Z</atom:updated>
            <content:encoded><![CDATA[<p>On March 26, 2015, I posted a short blog post to the Rent the Runway engineering blog, <a href="https://dresscode.renttherunway.com/blog/ladder">Sharing Our Engineering Ladder</a>, with a quick intro to the RTR engineering career ladder and links to both <a href="https://docs.google.com/spreadsheets/d/1k4sO6pyCl_YYnf0PAXSBcX776rNcTjSOqDxZ5SDty-4/edit?usp=sharing">spreadsheet</a> and <a href="https://docs.google.com/document/d/1SxmQBrDZvj16veuc2OVO0wUX7a7vEKPM-57dNLXhuEk/edit?usp=sharing">long-text</a> versions. This was one of the first public engineering career ladders that came with a clear distinction between management and IC levels, and meaningful details about the requirements and expectations at each level.</p><p>I published these resources because, at that point, most of the companies that were writing ladders were either a) getting some consultant like Radford to help them bootstrap something, b) copying a big company that they had worked for in the past, or c) stealing a template from a friend’s company and modifying it. For teams without the resources to hire consultants, prior big company experience to draft on, or friends to copy, they were basically stuck. I knew that what we had created at RTR was special, because it had many different sources of inspiration, contribution from a smart team of tech leads and managers, and a lot of care behind it. And as an open source person, I believe in the value of sharing not only ideas but actual work for others to use, build upon, and expand, for the greater benefit of the tech community. Publishing the ladders for widespread use was an easy decision, and one that has had an impact on the industry: I still get occasional thank-yous from people who have used it as a baseline all these years later.</p><p>These days, this sort of thing is almost passé. Almost every company has done this work, many inspired by the very ladders we published, but <a href="https://github.com/bmoeskau/engineering-ladders?tab=readme-ov-file">others</a> inspired by <a href="https://github.com/Medium/snowflake">far</a> <a href="https://www.engineeringladders.com/EngineeringManager.html">different</a> <a href="https://engineering.atspotify.com/2016/02/spotify-technology-career-steps/">approaches</a> published over the years. I am proud to have stoked a simmering conversation among leaders in the tech industry. It proved what I always knew: most people want a starting point to play off of when designing organizational processes as much as they want one for technical work. Even if all the starting point inspires is “ew, not this!”, it gives you something to riff off of.</p><h4>Advice For Writing</h4><p>I’ve done this exercise again at least twice over at different companies in the past decade, and it’s always a challenge. So here’s some brief advice for those embarking on this process.</p><ol><li>Don’t let (or make!) HR do all of the work. It’s really not their job to define expertise in your functions.</li><li>Details matter. Your ladder should be more prescriptive than a horoscope; it’s impossible to avoid all subjective language like “increasing complexity”, “large systems”, “high impact”, but pay attention to where you use that and try to provide ways of roughly measuring this where possible.</li><li>One great way to flesh out details is writing long-form text to accompany the spreadsheet-style ladder. I think it’s a shame people don’t do this more, even if they don’t publish it, because it helps you envision the work and catch things you might miss when writing bullet points.</li><li>You should not try to create a ladder that functions as a pure checklist or scorecard that guarantees promotion if people check enough boxes; promotions are as much about the needs of the organization as the skills of the employees.</li><li>Be honest: not every job family has ladders that start at the bottom and go to the top. Some should start in the middle and go up; some may start at the bottom and only go to somewhere in the middle. Don’t promise people that they can become the VP of X just because some people do job X, and don’t pretend that you should hire people straight out of school into jobs that are specializations that you only take on after years of working as a generalist.</li><li>Also, maybe you don’t need to create a job ladder for literally every job. There’s something to be said for the finance company catch-all analyst/associate/VP/MD scale to cover everyone, with ladders for large population jobs (such as engineering) where it makes sense.</li><li>Err on the side of more early-career levels rather than later-career ones. Assuming you are still hiring junior engineers (you really should be even in this AI era), the good ones will learn quickly and want to see career progress in their first few years of working. Once the path splits IC/management, just match the management levels and you’ll be fine.</li></ol><h4>Are Ladders Passé?</h4><p>Even as I write this, I’m not sure anyone will care. The industry is in backlash mode, and I wouldn’t be surprised to see many companies try again to make the “flat” organization work. But even with the aid of AI, I’m not convinced that we’ll overcome the human instinct to gather in groups and create leaders of those groups, and fight one another for power of those groups. <a href="https://www.jofreeman.com/joreen/tyranny.htm">The Tyranny of Structurelessness</a> has yet to be overcome, and for those who still care about creating strong, transparent, equitable organizations, this work matters. Just please don’t make me personally write them again!</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, available on Amazon and Safari Online, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a><em>, available now!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=329d309000cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Senior Shortcut]]></title>
            <link>https://skamille.medium.com/the-senior-shortcut-fadffe5503fd?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/fadffe5503fd</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 15:59:47 GMT</pubDate>
            <atom:updated>2024-10-11T16:20:52.663Z</atom:updated>
            <content:encoded><![CDATA[<p>Many have predicted the death of the “junior engineer” thanks to AI; after all, if AI can do all of the simple tasks, we don’t need to hire people who are only capable of handling those tasks anymore. And indeed, I was at a dinner of director+-level engineering leaders recently where many said they had turned all of their hiring to solely focus on “senior engineers” in lieu of anyone else.</p><p>Anyone who has thought about this for a moment sees the obvious problems. How do people ever become “senior engineers” if they don’t start out as junior ones?</p><p>One possible answer can be found by observing a recent terminology shift in the way we talk about engineers. During the last 5 years I got away from differentiating between engineers by “senior” or “junior” and started referring to the latter as “early career.” Call it excessive wokeness, perhaps, but in a time when people were moving into tech from other professions, calling everyone who was just starting out in engineering “junior” felt awkward and wrong. Since <em>everyone </em>has to go through “early career” at some point, perhaps the answer is not that we aren’t hiring <em>early career</em> so much as we expect those folks to be more skilled, senior, independent from the jump? Better get busy with those side projects and internships, college students! Of course, why would we ever hire interns if we aren’t even hiring new grads?</p><p>But people mean more than skills when they talk about hiring only senior engineers; many times they also want independence of work habits, and the judgement that comes from having experienced different successes and failures. That is much harder to shortcut. I have seen many college students come through my teams over my career, and even ones with extremely strong programming skills and good work experience were rarely capable of reaching their potential without mentoring and management, and usually lacked the ability to reliably differentiate between ideas that sounded good but wouldn’t work in the context of the team/company/technology, and ideas that were a good fit given these constraints.</p><p>We could leave all of the training of early career people to big companies; they may be hiring fewer early career engineers but they’re still hiring them, and big companies have always been a good place for engineers to cut their teeth. But here I would argue we get to a different problem. As my friend <a href="https://x.com/theccoder/status/1844741140412502067">Shanti said on twitter</a>:</p><blockquote>Seniority isn’t a particular space, it’s just a label for what the particular organization values. Many Senior engineers are products of the incentive structures of their orgs, and part of that is, unfortunately, calcified Opinions.</blockquote><p>When you leave all training of early career engineers to big companies, you’re going to get a lot of big company Opinions coming out. One of the nice things about senior engineers trained at smaller companies and startups is that they are comfortable in ambiguity, they are comfortable in a mess, and they don’t necessarily bring quite as many Opinions, having been exposed to more varied technology in their formative years. I would guess that most startups want senior engineers who are not only technically solid and independent, but capable of adapting to the environment, and the best training for that comes from startups. You don’t absolutely have to work your early career in startups to have this flexibility (after all, I spent my early career in finance and managed to stay flexible enough), but it certainly helps.</p><p>At this stage of my career, I recognize that I define “senior” somewhat more strictly than many people. When I talk about senior hiring, I am not talking about people with 3–7 years of experience who can be trusted to write good code independently and own projects; I’m thinking about the people who can act as the technical leaders for that group. And if this is what you are hoping to hire, those magic 10Xers who can really take on the nasty projects and untangle them for you, I have bad news about relying on external senior hiring to do the job. Because the more senior you are hiring, the higher the likelihood that they will be quite brilliant but incapable of adapting to the culture of your company and engineering team enough to do the non-technical work that has to happen for these types of projects to succeed.</p><p>However, if you hire strong early career engineers, some percentage of them will turn out to have the potential to become those 10Xers. If you can retain them over time, they will grow to lead the game-changing initiatives of your company, being both technically capable and fully embedded in your company’s culture. Those years growing up with you give them an internal network and high baseline of trust that is so critical for success when you’re talking about big technology projects. Sure, not every early career hire will turn out this way: many will leave within the first three years, some that never found their footing, and others that were great but itchy to try new things. But I’ve yet to see a perfect shortcut; you’re going to hire the wrong people whether you hire only junior or only senior, and you’re inevitably going to lose some of the right ones either way.</p><p>If you’re thinking about the long game, and hoping to build a company that will last, you probably want to invest in at least some early career hiring during periods of growth. The truth is we’re in a prisoner’s dilemma here; you can try to be the company that defects and wins because of it, but if too many of us defect, we’re all going to pay. Given the uncertain nature of what you “win” by only hiring senior people in the first place, I would question the value of this bet. If you are working in a niche area, with a very small company that you expect to remain small, go nuts: hire and fire senior people until you get the right mix. But if you have aspirations to not just build a company, but to grow to a point where you can influence the industry, you may want to reconsider your all-senior stance. Don’t underestimate the value early career engineers can bring to a team; unless we’re a dying profession, their continued existance and success is the basis for our future.</p><p>PS: If you are hoping to hire only senior people so you can avoid having to manage them, you’re delusional. Enjoy your house of cards and pray there are no stiff breezes in your future.</p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, available on Amazon and Safari Online, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a><em>, available now as ebook and shipping physical copies in November!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fadffe5503fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Platform Engineering Beyond CFEngine]]></title>
            <link>https://skamille.medium.com/platform-engineering-beyond-cfengine-daa9268c9c5b?source=rss-12421a4f856------2</link>
            <guid isPermaLink="false">https://medium.com/p/daa9268c9c5b</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[platform]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Camille Fournier]]></dc:creator>
            <pubDate>Tue, 01 Oct 2024 17:58:15 GMT</pubDate>
            <atom:updated>2024-10-01T17:58:15.953Z</atom:updated>
            <content:encoded><![CDATA[<h4>Notes on Sustainable Platform Engineering</h4><p>Readers of a certain age and heritage will remember CFEngine, one of the early popular <a href="https://en.wikipedia.org/wiki/CFEngine">configuration management</a> systems (still in use today!). It provides a powerful way for administrators to manage system configuration across heterogenous clusters of machines, and ushered in the age of automated configuration management, a key component of the modern technology ecosystem. I’ve worked with and managed teams responsible for cfengine infrastructure, and have seen first-hand the value and challenge of managing and operating these systems. But I have also seen the limitations of approaching platform engineering from this mindset.</p><p>Configuration management, infrastructure provisioning, and the orchestration thereof is a devilish problem for organizations. Significant innovation has been poured into this area, from advances in “Infrastructure as Code” offerings like terraform, to orchestration platforms like kubernetes. The problem of maintaining heterogenous environments, especially as these environments grow in dimensions of complexity (eg, all of the pieces that need to exist for you to deploy an application onto the cloud using a multitude of cloud services), is neverending. While we may have moved beyond cfengine, many modern platform engineering teams focus on this part of the stack, making it easy for application teams to select their appropriate archetype or blueprint to provision the cloud resources their application needs to run.</p><p>I happen to also think that this practice, particularly when it is the main focus of your platform team, is misguided. It comes from walking down a path that seems logical:</p><ol><li>Terraform sucks. Especially when you’re in a company that is moving to the cloud from an old datacenter model, and your initial approach is to make every app team write its own terraform to provision things, you quickly see that every team is spending a ton of time figuring this out. And a lot of the time they’re figuring out the same things! So why not save them some effort, centralize that terraform writing, and create some patterns for everyone to adopt. That makes sense, right? This gets “day 0” (initial deployment) quickly.</li><li>Then you start to think, well, there’s a lot of other things we could configure too! We could configure observability so they’re set up for appropriate logging and alerts. We could allow them to specify the level of availability they need and provision them into multiple zones or regions. All of this is great, and useful; it gives application teams better deployments. So why not keep going down this path?</li><li>(sometimes) Even though terraform sucks, and we think we should centralize it, we don’t want to hide it from the app teams completely either, because that is restrictive. So we don’t completely hide it away from them: the code our blueprints generate is checked in nicely to a repo that application teams can access and tweak as needed. We want to be <em>helpful</em> but not <em>limiting.</em></li></ol><p>You can spend a good long time building this way; indeed, keeping up with the changes in cloud offerings and application team needs means you can probably do it forever. So, why not take this approach? It isn’t a stupid thing to do, many teams have used it to reasonable success. But it also relies on a few assumptions, sometimes spoken, sometimes not.</p><ul><li>Assumption #1: While there are enough similarities in the infrastructure needed to provision that we can create these “blueprints” and have them be useful for many applications, there aren’t any better abstractions that we could create for these similar groups of applications. We really don’t want to have much if any production software that we (the platform team) are operating that application teams rely on beyond deployment stages, because that puts us on a critical path that we’re not sure we can handle.</li><li>Assumption #2: The cloud provider operates all of the underlying systems in such a way that they rarely perturb the application teams, and the app teams can rely on themselves or their SREs to manage it all when they do. We can be there to help debug but we don’t need to be part of critical production support.</li><li>Assumption #3: The biggest bottleneck that we can solve for application teams is getting the stack that their application needs provisioned and running in the cloud. This seems totally obvious at the beginning of a cloud journey where the whole company is trying to figure out how to do this stuff in the first place, and very few people are operating meaningful applications in the cloud.</li></ul><p>Now that I have extrapolated these assumptions, you may see where I am going. If you agree with all of these, I wish you the best; you may very well be correct for your organization that this is the right approach! But there are some major limitations that fall out of these assumptions.</p><h4>Limitation #1: We don’t want to be on the hook for operations, so we don’t want to build software we have to operate, especially on the production critical path.</h4><p>Avoiding operations is, generally speaking, a bad idea for platform teams. The value of a platform team is often commensurate with how much operational burden they are able to remove from application teams, and you undermine your value by shying away from it. When there is a budget crunch, teams that are doing “enablement” are cut long before those that are responsible for running critical systems; one is viewed as optional, but the other is known to be essential.</p><p>Understandably, sometimes application teams don’t want you in the middle of their operations, especially if you aren’t very good at them in the first place. But it’s very hard for you to be half-in and half-out of ownership when you’re the experts in all of the configuration and infrastructure provisioning; it’s hard to know how to do that without knowing the underlying infrastructure well from an operational perspective, which means you’re likely to be needed during incidents to help debug what is happening; or, the app team knows enough that they don’t need you and then…. what are they really getting from using your blueprints at that point? Maybe it helped them bootstrap initially, but now it’s probably just a pain for their experts to translate your definitions to their own mental models and feel comfortably in control of what is happening.</p><p>Application teams that want to own everything themselves, should; the ones that need it will do it well, the ones that don’t do it well will have a clearer idea of the cost/benefit tradeoff of owning everything themselves.</p><p>For everyone else, I would argue that if you can find enough similar blueprints, you should consider whether you can build a platform that they deploy their application on top of, rather than just maintaining configuration for them. To be clear, this is <em>tricky. </em>It’s tempting to jump to “trying to build Heroku for the company” and many of us have seen that fail. At the same time, if there is meaningful work to be done to combine a bunch of parts together so that a common group of applications can be deployed into the cloud, I think it’s likely that there is something you could be operating. It might be a thin shim of software that takes hosted kubernetes with some company-specific controllers and integration with company-specific entitlements and finops support, and allows your application teams to specify a much simpler subset of configuration parameters and deploy their applications into that platform. Ask yourself, what could you build and operate yourself that would meaningfully free application teams from having to understand and maintain so much of the underlying infrastructure stack?</p><p>It’s important to note that this may not apply to a small company that can use a few select cloud provider platforms directly to do what they need (the aforementioned Heroku, Vercel, AppEngine, etc). I would in fact not advise trying to spend a lot of developer time building your own platforms if out-of-the-box vendor offerings will do! But for larger companies or certain types of complexity, writing some (not too much) custom software to make something that does what your company needs and hides the bare cloud complexity from the application teams can be worthwhile.</p><h4>Limitation #2: We don’t actually want to write our own software.</h4><p>Our bespoke kubernetes platform is an example of a real type of platform that I’ve seen built and operated by a platform engineering team. It works because kubernetes allows you to write your own code to modify its behavior; and while this is the kind of tricky work you may not want to do too often, it is very useful for taking a powerful general-purpose system and focusing it on specific usecases that you can then offer as a service.</p><p>You may be thinking, surely if this is useful someone else will build it, or the cloud provider will offer it, but there’s no reason that I should really need to write software myself. But there is a wide gulf between building a platform that is so generally useful that it can be sold to many types of companies with diverse usecases (very very hard), and building something useful within a very specific environment. In particular, the integration of the generally useful components with the quirks of your company (often relating to identity/entitlements, corporate hierarchy/department codes for billing, and other such company-specific details) is a fruitful place to look to balance writing just enough code to create a valuable platform.</p><h4>Limitation #3: We don’t want to become a bottleneck.</h4><p>The appeal of the blueprint idea is that it has the escape hatch; anything that could be done in terraform is at least theoretically fair game, the application teams can work to enable more cloud things themselves, and you haven’t created any real restrictions, just nice paved paths that make certain patterns easier. And I am very sympathetic to giving teams a way out of your choices so that you don’t limit the company’s innovation through the capabilities of your platforms.</p><p>Unfortunately, leaving the wide world of possibilities open retains all of the downsides of the wide world of possibilities. Choice is always appealing in the beginning and often limiting over time as every bespoke choice must be supported indefinitely. If you allow every team to independently choose what they want all the time, you get what we call the <em>over-general swamp. </em>Each different choice requires its own glue (one-off code for integration, automation, configuration, etc), and while glue is quick to create, it is painful to change.</p><p>Taking a product approach to platforms doesn’t mean making everyone happy all the time and building exactly what they ask you to build. It means taking the time to understand what is actually making your application teams less efficient, and doing hard work yourself so they don’t have to. Sometimes that hard work is making curatorial choices about what is supported and what is not, and making some niche group unhappy. As any product manager will tell you, it’s stressful bearing the burden of setting strategy and making bets that don’t always pay off.</p><h4>Products, not Scripts</h4><p>To wrap this up, Platform Engineering done well is more than configuration management and infrastructure provisioning. It is doing the hard work to identify, build, and operate abstractions that allow application teams spend less time on the underlying technology and more on solving problems for their business. Instead of thinking about how you can support the scripting and automation of infinite variations, think about the products you can build to cover the most common archetypes in a way that goes beyond the act of provisioning and deployment.</p><p><em>This is the first in a series of articles where I attempt to work through some thoughts on how to differentiate platform engineering teams and create meaningful value through platform engineering. In that sense, these notes are seeking audience resonance, and I am curious to hear your questions and reactions! Thanks to James Turnbull and Pete Miron for their early comments.</em></p><p><em>Enjoy this post? You might like my books: </em><a href="http://amzn.to/2nw1QN5"><em>The Manager’s Path</em></a><em>, available on Amazon and Safari Online, and </em><a href="https://amzn.to/3MwcgGo"><em>Platform Engineering: A Guide for Technical, Product, and People Leaders</em></a><em>, coming out fall 2024 and available in early release on </em><a href="https://learning.oreilly.com/library/view/platform-engineering/9781098153632/"><em>O’Reilly Learning</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=daa9268c9c5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>