<?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 Chris Anderson on Medium]]></title>
        <description><![CDATA[Stories by Chris Anderson on Medium]]></description>
        <link>https://medium.com/@chrisan?source=rss-46c61143d834------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*WP89qAF9p2S0Vowk.jpg</url>
            <title>Stories by Chris Anderson on Medium</title>
            <link>https://medium.com/@chrisan?source=rss-46c61143d834------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 18:01:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@chrisan/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[1/3 in, 1% done]]></title>
            <link>https://medium.com/@chrisan/1-3-in-1-done-ef4eb22c6ddc?source=rss-46c61143d834------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef4eb22c6ddc</guid>
            <category><![CDATA[facebook]]></category>
            <dc:creator><![CDATA[Chris Anderson]]></dc:creator>
            <pubDate>Wed, 08 Jan 2020 15:30:02 GMT</pubDate>
            <atom:updated>2020-01-08T15:30:02.950Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sHw8Bj7Lu6EyIBEC0Px5YA.png" /></figure><p>Disclaimer: I am not the right person to speak to any larger debates around Facebook advertising, fact checking, or broader integrity efforts. There are plenty of people inside and outside of the company that will happily give you their hot take, I’m focusing my discussions around what it is like to join the company and have impact.<br> <br> <br> Follow up to <a href="https://medium.com/@chrisan/week-10-fb-quick-checkpoint-3be70999b4b6">https://medium.com/@chrisan/week-10-fb-quick-checkpoint-3be70999b4b6</a><br> <br> Facebook has no public levels for individual contributors, and really only has one seniority metric — what percentage of the company is newer than you. As of now, I have been at Facebook longer than about 1/3 of all employees.<br> <br> That is crazy to me.<br> <br> I think of what impact I’ve already had, and it’s also kinda insane. With a daily ship cycle, and fast moving culture, you have the ability to hypothesize, experiment, learn, and iterate — you have so much opportunity for impact.<br> <br> There is a saying at Facebook “This journey is 1% finished”, to imply that even at more than 2B people using the platform, we are still 1% done. The unfinished aesthetic of the building even reinforces this, we are always iterating, always learning… the journey is always 1% done.</p><h3>Product autonomy</h3><p>Facebook has pushed down cross functional product ownership much deeper into the organization than I have seen before. Consumer marketing, developer marketing, partnerships, data science, design, engineering, product, content strategy, user research, public relations… all have a seat at the table at a pretty low level in the organization (~250 person org size will often have all of this, sometimes even smaller groups!), and we directly connect into Global Marketing and Sales.<br> <br> What does this mean? We have a small group (&lt;10 people) that can really make product decisions about global launch, marketing budget, different regional strategies for product, technical implementation, and product roadmap. This allows us to have direct control over the product from inception, design, building, deploying, marketing, growth, and (sometimes) shutdown. Being able to have line of sight to the PR associated with something, from the original product design, can create radically better features.<br> <br> This also means the team can have real accountability on metrics. You can’t say “well, marketing ran a bad campaign” to shirk responsibilities for a bad launch, nor can you say “well, engineering didn’t build the features that users wanted”… with everyone at the table, you really have complete accountability. It’s quite invigorating.<br> <br> My favorite example of this, we continued to release a “Facebook Gaming” app in new markets this past year. The team decided what markets, in what order to release. We looked at the metrics for success, determined when to move onto new markets. When we got positive signal, we were poised to accelerate (the app is currently available in all Latin American markets, in addition to several South East Asia markets). The team made the calls, and was held accountable for the retention, growth, and spending on marketing for the app. That is just incredible!</p><h3>6 month PSC (review) in a metrics driven culture</h3><p>Facebook famously had a “Move fast and break things” culture (now “Move fast with stable infra”). Often misconstrued as causal (“move fast and it’s ok to break things”) rather than 2 distinct goals — move fast, and be willing to break expected behavior.<br> <br> On of the interesting aspects of this, I’ve learned, is the reinforcement that the HR systems, product metrics, and culture all have around this. By having a 6 month review cycle, with a strong emphasis on feedback and mid-point checkins, you end up in a model where every 3 months you are evaluating how you are doing against product metrics to understand your impact on the product. This leads to a operational model of constant planning, executing, evaluating, and adjusting… every couple months you determine if the bets are paying off how to adjust them, and how your personal impact is.<br> <br> The up side — bias towards iteration, responding quickly to the market, ruthless prioritization, and fast actionable feedback.<br> <br> The down side — it can be hard to do longer term projects, sometimes “deep” quality can be sacrificed for speed, and it can be too easy to give up on an idea because it doesn’t show promise in the half.<br> <br> Overall this is fantastic, and I wouldn’t trade it. There are mitigations for some of the downside (more later), and getting 2x-4x the number feedback cycles forces more rapid experimentation and growth of yourself, the team, and the product. Aligning all of those is even better!</p><h3>Level and career progression</h3><p>With Facebook’s focus on mentoring, metrics as a tool to crisp up the definition of impact, and bottoms up execution, we have an amazing pipeline to get engineers from college hire to senior engineer. The ability to learn internal systems and build features out is quite incredible. The bench of tech leads and line level managers is strong.<br> <br> The challenge can come with the shift from senior roles to what Microsoft would have called “principal” roles. What successful engineers do from college to senior, is not the same as we want from principals. We need more product focus and breadth engineering. We need people to advocate for longer term projects, quality, and provide technical vision. We need deeper experts in domains.<br> <br> I’ve watched several engineers hit this wall pretty hard, and getting people to transition from personal impact to team and product impact is really the shift. Principal should be about having a team of people following your technical agenda, rather than only using the “lead by doing” muscle. You need to have other tools for influence at your disposal. I find I rely less on raw coding and design, and more on communication. You end up writing posts and slide decks to get people to buy in on your vision. You use design meetings and exec reviews to get alignment with sometimes arbitrary deadlines (never waste a good crisis).<br> <br> I can’t say enough how much I think that Facebook is incredibly strong for college grads, it should absolutely be on the top of your list to join.<br> <br> When I came on board, I was pretty concerned about my ability to have influence after having lost much of my professional network at Microsoft as well as a significant technology stack reset. What I’ve found is that having a focus on the people using software, be willing to learn from anyone and everyone, and having a desire to have real product impact has made it a very welcoming environment.<br> <br> Coming to Facebook from an industry perspective, the only limit appears to be on your desire to learn, work in a sometimes ambiguous (but empowering) environment, and have an idea of what impact you want to have.</p><h3>In closing</h3><p>I think that my biggest learning is really a reinforcement of what I’ve heard before. Yes, Facebook is a move fast company. Yes, we have strong product autonomy and are very metrics driven. And yet we still need senior technical people to hold the “move fast this half” and “have a long term plan” in their head at the same time. This cognitive dissonance is required to keep pace while moving towards the long term future.<br> <br> The learning is continuing. I’m more excited about the next half than I was about last half.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef4eb22c6ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week 10 @ FB, quick checkpoint]]></title>
            <link>https://medium.com/@chrisan/week-10-fb-quick-checkpoint-3be70999b4b6?source=rss-46c61143d834------2</link>
            <guid isPermaLink="false">https://medium.com/p/3be70999b4b6</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[facebook]]></category>
            <dc:creator><![CDATA[Chris Anderson]]></dc:creator>
            <pubDate>Wed, 08 May 2019 15:57:47 GMT</pubDate>
            <atom:updated>2019-05-08T15:57:47.325Z</atom:updated>
            <content:encoded><![CDATA[<h3>10 weeks at Facebook</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kVcFbXKwv-XTDg-ONJUNYA.jpeg" /><figcaption>The view from my desk</figcaption></figure><p>This was originally written on March 25, 2019… I wanted to capture some quick notes on my starting at Facebook while I still have (somewhat) fresh eyes.</p><h3>Bootcamp</h3><p>I spent 5 weeks in bootcamp, 1 of which was vacation… Bootcamp was incredibly interesting. After a small hiccup on the logistics, I had a good 1.5 days at Menlo Park, got hardware, connected to my accounts, had some great company level presentations, and then headed back. Bootcamp in Seattle consisted of a bunch of in person talks, some self-paced videos, and then bootcamp tasks. The coolest part of this whole thing was that within 4 or 5 working days I had deployed a (small) change to the Facebook site. The bootcamp tasks are well selected and over my whole bootcamp time I was able to make changes to Instagram, Facebook web, Facebook iOS, and the intranet/internal content (one of our internal tools).<br> <br> My takeaways from this first chunk…</p><ul><li>Since I was pre-allocated, I missed out on the “dating game” aspect of bootcamp interviewing other teams. There was definitely a comfort aspect of knowing where I was going, but I do think I missed some of the adventure of figuring it out. Granted, Seattle has a smaller set of teams, so choices will always be somewhat limited here if I don’t want the remote thing…</li><li>The investment in internal tooling is amazing. So many of the tools have optimizations to our specific use case. An internal IDE (Nuclide) which connects seamlessly to dynamically created developer VMs… the diff review tool which can automatically connect to the IDE… the automated testing, build, deployment systems all connect together… it just works so smoothly and efficiently.</li><li>Facebook is such a rapidly growing and evolving company, and they have done a great job learning from other industry leaders. With Microsoft’s transformation over the past 5 years, it is interesting to see the number of places that we have parallel but independent evolution. I have been pleasantly surprised at the places that things feel familiar (although different), and places that I can take recent learnings at the “new” Microsoft and apply them to my Facebook experience.</li><li>Bootcamp faces a tough pacing problem, needing to get everyone up to a baseline level of competence across a wide variety of programming languages, internal tools &amp; processes, and product design. I’m guessing everyone going through the program ends up with a chunk of stuff that was slow/too easy and another set that felt fast/too hard. Not sure I have great guidance here, other than it is an interesting problem to design that curriculum</li></ul><h3>On the team</h3><p>I’ve been on the Games team now for 4 weeks, just starting my 5th. For me, I feel like my ramp has been a bit slower than I’d expect. I felt reasonably prepared from bootcamp on how to acquire new knowledge, and what the “nouns and verbs” at Facebook are. I picked up an initial task and started working on an experiment.<br> <br>Having worked on line of business data visualization applications, I had thought it wouldn’t have much overlap with Facebook. Much of Facebook, however, feels like one of these line of business apps. Taking signals from people to show them what would have the most relevancy to them. As such, it feels like a big chunk of feature design is to started with the signals you need; sometimes they exist (like people “like”ing a page) other other times you need to generate it (aggregating information to have new insight). There is a huge stream of signals coming in from over 2B people, and each team understands the pieces necessary for their business, so you end up needing to talk with employees on these teams to get stitch together what you need to build features.<br> <br>In 4 weeks I completed 1 end to end task, data pipeline, memcache (laser) integration, graphql end point, www user experience, integrated into a multi-treatment experiment… this included multiple false starts and a ton of learning about the practical execution of the systems that I learned in bootcamp. Of course, as the experiment result comes in it looks like we are red across the board and the feature won’t ship; although the team is encouraging and suggests some new treatments to see if we can eke out a win.<br> <br>I spent several weeks working on a second feature, which we were able to validate that there was no strong correlation between the data and the metric we wanted to affect. This task was a bit more frustrating as the result analysis was slow and a struggle to find the right correlations (turns out they didn’t exists).<br> <br>For both of these tasks, it became clear that my drive to push through things and make progress without randomizing other people cost me several days. Coming off bootcamp I had the view that I should learn and become proficient in most of the systems, while it seems that the expertise around various areas has the depth knowledge spread out — data engineers vs. data scientists, team A vs. team B, Android vs. iOS engineers, etc.<br> <br>While planning the next sprint, I ended up with some down time, so I picked up several engineering quality tasks and pushed through a handful of diffs across the www, iOS, and Android code for the games team. These gave me a bit better experience with the diff flow and getting a regular pipeline of changes. There is a rhythm to the flow of code here, bounce ideas off people, make a pass at something, publish a diff, get feedback, iterate… start an experiment, move onto something else while it “bakes”… I can’t yet anticipate the beats, but I can at least start to feel it.<br> <br>In parallel to these coding tasks, I’ve been looking into the games strategy and ramping on the broader context of our work. With our significant ad tech backend (both the core FB ads and the Facebook Audience Network features), there is a lot to absorb in how an ad funded (and tech producing) company runs. Coming from a largely enterprise and subscription focused business, getting my head around the terminology and physics of the business is taking some time. It’s very interesting to come from a world where you have to earn every purchase, to one where you have this delicate balance between value to people and value to businesses… it’s incredibly interesting.<br> <br>Facebook, it seems, is about building software for everyone, which means you have to build out for people with very limited money. If your addressable market is 100% of the worlds population (with internet), then you need to think how to ensure every feature is in every language, every affordance for accessibility, and is always free for the user. This idea of advertising as an enabler of global access, as opposed to an efficient business model for micro-transactions, definitely changed my view.<br> <br>I’ve been reading all the team diffs (our diff tool is a form of social network, so participating is key to understanding the heartbeat of the team), not yet feeling competent enough to add valuable commentary, but it’s helpful to get a feel for the types of changes happening to the code. Our team has a great social culture around lunch, there is a giant table in our space and organically 10–20 people will show up for lunch, no arranged time or anything. Everyone seems welcome and the topics range from a tough bug people are working on to what is the weirdest question you use to break the ice (“Do you regret having children?”, hands down the winner for most awkward first question).<br> <br> My takeaways from this second chunk of time…</p><ul><li><strong>Have two or more features in parallel</strong>… both to keep busy when one is blocked or waiting for results, and because you are likely to have one (or more) not pan out. Having a portfolio of investments will make you more efficient and likely to have successful impact. (in hindsight… duh!)</li><li><strong>Advertising is the life blood at Facebook</strong>, not because it provides us with profits, but <strong>because it allows us to have a service for everyone</strong>. Pay services are exclusive to the realm of the people that can afford it. By limiting our focus to broadly available services, services for literally everyone on the planet with an internet connection, we had to align with a business model that gives everyone access.</li><li><strong>Have a queue of tasks to fill up any down time</strong>… it helps learn the code and develop those skills you lack across the codebase. Targeting a couple small tasks a week in addition to feature work will keep the flow going. It’s a tough balance, I ended up kinda doing a surge of feature work then bug work, but I think it would have been better to flow on both in parallel.</li><li><strong>Lean more on others</strong>… while it’s good to know how to find things, the wins of asking someone if a table exists that does X or if we already have a tool to do Y is just too huge. I’ve ramped down from 1 hour of self investigation to probably 15 minutes of self investigation before I ask.</li><li><strong>Don’t skip the social</strong>… having lunch with the team is important. Getting coffee with folks is important. I’ve been slow to connect with the broader team in Seattle, and I think I need to spend some more dedicated time getting to know more people. Too many people I recognize, but can’t remember their name and have no idea what part of the product they work on.</li><li><strong>This is an engineer’s paradise</strong>, great tools (sometimes flakey), autonomy, great support from management, huge problem space, unlimited scope… Facebook as a platform for an engineer to have impact seems limitless. My biggest takeaway is that I need to ramp faster to start having broader impact. Keep the flow going around features and bugs, but accelerating into bigger areas for impact is crucial.</li></ul><p>A hackathon is starting up this week, and I’ve heard — everyone hacks for their first hackathon… so onto the next adventure!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3be70999b4b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>