<?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 Cameron Rose Fleming on Medium]]></title>
        <description><![CDATA[Stories by Cameron Rose Fleming on Medium]]></description>
        <link>https://medium.com/@cameron.fleming?source=rss-1a626d4a4be5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*fy05YpkZgA7gZ0G12sMAEA.png</url>
            <title>Stories by Cameron Rose Fleming on Medium</title>
            <link>https://medium.com/@cameron.fleming?source=rss-1a626d4a4be5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 16:05:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cameron.fleming/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[The Holidays at Bluecore: Helping Santa Deliver an Unprecedented Volume of Gifts, One Email at a…]]></title>
            <link>https://medium.com/bluecore-engineering/the-holidays-at-bluecore-helping-santa-deliver-an-unprecedented-volume-of-gifts-one-email-at-a-73b1f6a7c20e?source=rss-1a626d4a4be5------2</link>
            <guid isPermaLink="false">https://medium.com/p/73b1f6a7c20e</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[bluecore]]></category>
            <category><![CDATA[site-reliability]]></category>
            <category><![CDATA[load-testing]]></category>
            <dc:creator><![CDATA[Cameron Rose Fleming]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 13:01:01 GMT</pubDate>
            <atom:updated>2019-01-07T13:01:01.082Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Holidays at Bluecore: Helping Santa Deliver an Unprecedented Volume of Gifts, One Email at a Time</h3><p>The holiday shopping season in November and December produces the highest revenue for Bluecore’s customers: retailers and brands. The peak of the season is Black Friday and Cyber Monday. With large spikes in traffic, retailers’ websites are pushed to new extremes. Each year there are reports of retailers’ sites experiencing outages because of the increased site activity. Every minute offline can mean large losses in revenue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FroqL45YTSsMhj4t" /></figure><p>Retailers depend on Bluecore to drive revenue from highly personalized email campaigns during this time of year. The volume of data we ingest follows that of our customers, and so we expect and prepare for a massive spike in activity. In addition, the amount of traffic leaving our system is greatly increased. We need to build a resilient system to support our customers while avoiding the costly implications of too much over provisioning of resources.</p><p>In order to prepare for higher traffic during the holidays we’ve found that reviewing prior year results, forecasting traffic changes, load testing, and fixing issues or coming up with “creative” short term solutions have been highly effective!</p><h3>Planning</h3><p>The Engineering team kicks off preparations 3 months before Thanksgiving. The technical leads for each team meet for a high-level review of last year’s planning process and brainstorm specific technical investments that we know are necessary for this year. This year we came up with a list that we knew required some kind of work or investigation including:</p><ul><li>Checking if our load testing tools from last year can simulate the expected load for this year.</li><li>Coordinating with 3rd parties that we have partnerships with that could be affected by additional load.</li><li>Determining if we will need to provision additional resources from our underlying cloud computing provider, Google Cloud Platform.</li><li>Auditing the new features have we built this year that could be affected by higher load.</li></ul><p>After this kickoff meeting, we met every other week to prioritize what we needed to do to be holiday ready and to prepare for and review results of load tests of our system.</p><h3>Prioritization</h3><p>These meetings provide us with LOTS of ideas and issues. In order to prioritize what to focus on first we go through the following questions:</p><ul><li>How likely is this? Has this ever happened before?</li><li>What is the impact if it does happen?</li><li>Is there a workaround if it does happen? (e.g. can we pause something or turn it off?)</li></ul><p>When we find high priority issues that need pre-holiday fixes but may need time consuming or high risk changes, we try to see if we can implement some of the following “creative” solutions for the short term:</p><ul><li>Over-provisioning: Throw money and computing resources to avoid spending engineering time.</li><li>Documentation/runbooks: Test and document how to turn something off or implement a workaround.</li><li>Just disable/turn something off that isn’t needed right now.</li></ul><h3>Gamedays</h3><p>Our main concerns when it comes to the holidays are:</p><ol><li>The volume of events ingested from shoppers on our clients’ websites.</li><li>The number of emails leaving our system.</li></ol><p>Based on previous years, we estimated that our event ingestion volume this year would be about 4x our peak load on a normal day. Our outgoing emails are less predictable as we have increased the ability of our clients to set up their own batch emails. However, we used previous years as well as our understanding of how clients use email during the holiday season to say that we would get at most 10x peak load.</p><p>We wanted to ensure we were prepared to handle the increase in traffic — the only way that we could demonstrate to ourselves, our leadership and, most importantly, our customers that we could handle the increased volumes was to simulate the volume in question.</p><p>A well-known tool in resilience engineering is the <a href="https://blog.newrelic.com/2016/09/30/game-day-testing/">Gameday</a>: an exercise that tests the response of a system to some simulated event (failures, extreme volume shifts, degradation of system resources). At Bluecore, we use this to simulate a situation (e.g. 4x peak traffic in event ingestion) over the course of a few hours. In order to get a meaningful understanding of our system, we break our simulation into progressive steps (e.g. 2x, 3x, 4x peak traffic). As part of our simulation, we take a step, validate our assumptions on how the system would respond, note any irregularities, and if nothing is broken, we take the next step.</p><p>For each of our holiday readiness gamedays, we held a brainstorming session for customer-impacting questions we wanted to answer and then figured out how to monitor and test the question. Some examples were:</p><ul><li>Can we handle 8x event ingestion traffic (2x more than peak expectancy, to allow for some margin of error)?</li><li>Can we handle 10x email sending volume for highly personalized emails?</li><li>Will the added load cause our analytics pipelines to slow down?</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/754/0*p9O1BpLu_DoG0f_1" /><figcaption>Stats from a gameday ramping event ingestion up to 7x requests</figcaption></figure><p>We then identified conditions that the system needed to meet in the situation:</p><ul><li>Event ingestion processing throughput stays high.</li><li>Throughput of personalized email campaigns stays high.</li><li>Analytics data stays up-to-date.</li></ul><p>Finally, we identified any tools we would need in order to test our system. These tools were configurable to allow turning the test on and off as well as making the test criteria change.</p><p>For the event ingestion scenario we created two tools:</p><ul><li>A load testing tool that took real event data, stripped out personal information and replayed it to our test client endpoint.</li><li>A stubbed customer service that would mimic whether customers opened/clicked emails.</li></ul><p>For the email sending scenario we created the following tool:</p><ul><li>A tool that took real event data, stripped out personal information and added it to a fake client. This enabled us to set up email campaigns using the fake data to make sure it could make it through our system.</li></ul><p>With these questions, conditions, and tools we began our gamedays. After each gameday we would take the results fix any issues that we saw, then rinse and repeat!</p><h3>How we did</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*FenuOmhqMSUO9v3T" /><figcaption>Sent emails in November — aggregation over 12 hour intervals</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TifvyEo53I12dosz" /><figcaption>Events ingested in November — aggregation over 12 hour intervals</figcaption></figure><p>We made it through the 2018 holidays without any outages! Our preparations allowed us to see where we had weak points and fix them when we could or work around them as we plan longer term fixes that will allow us to continue to scale in the coming year. It was a massive group effort across not only our Engineering team but also the entire company!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=73b1f6a7c20e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluecore-engineering/the-holidays-at-bluecore-helping-santa-deliver-an-unprecedented-volume-of-gifts-one-email-at-a-73b1f6a7c20e">The Holidays at Bluecore: Helping Santa Deliver an Unprecedented Volume of Gifts, One Email at a…</a> was originally published in <a href="https://medium.com/bluecore-engineering">Bluecore Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Importance of a Well-Defined API Interface in Building a UI]]></title>
            <link>https://medium.com/bluecore-engineering/the-importance-of-a-well-defined-api-interface-in-building-a-ui-1029058e21a4?source=rss-1a626d4a4be5------2</link>
            <guid isPermaLink="false">https://medium.com/p/1029058e21a4</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[bluecore]]></category>
            <category><![CDATA[user-interface]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Cameron Rose Fleming]]></dc:creator>
            <pubDate>Tue, 02 Oct 2018 12:01:01 GMT</pubDate>
            <atom:updated>2018-10-02T12:01:01.500Z</atom:updated>
            <content:encoded><![CDATA[<p>Bluecore started with a proof of concept product that could be quickly iterated upon. We used Github as our “UI” where we could make updates to structured configuration files that would be used to determine the who, what, and when of our emails. Our customer success team needed to be fairly technical because they needed to update these files. This worked well in the beginning while we found product-market fit. However, as our customer base grew, this process no longer worked for 2 reasons:</p><ol><li>Our customers wanted to have more control over and visibility into the emails they were sending out.</li><li>We would have to scale our customer success team linearly with the size of our customer base, which would be very expensive.</li></ol><p>It was time to build a self-serve product with a UI! We made a few mistakes along the way, and through the process of fixing mistakes and creating new products, we’ve improved how we design and iterate.</p><p>One of our biggest mistakes in building our web application was not creating well-defined interfaces between our frontend and backend. Without these interfaces, our frontend engineers had to understand how the backend engineers stored the data. This allowed backend engineers to push more business logic to the frontend to handle. This further broke the principle of separation of concerns.</p><h3>Why was this problem such a pain?</h3><ol><li>Changes to the frontend required a deep understanding of both frontend and backend code, which caused changes to be very error-prone and reduced the iteration speed.</li><li>The only way to really mitigate errors was to have thorough integration tests, which were hard to maintain because they also required a deep understanding of both frontend and backend code.</li><li>Changing how the underlying data was stored on the backend would mean lots of changes to the frontend as well.</li></ol><h3>Why did this problem happen in the first place?</h3><ol><li>Our engineers hadn’t really built a UI like this before.</li><li>We were trying to reuse as much of our backend code as possible.</li><li>The initial design didn’t take into account all the necessary features and so new things had to be added later on.</li></ol><p>These issues could be overcome. However, most importantly, <strong>we were on a time crunch</strong> and therefore we <strong>didn’t spend enough time planning</strong> out what actually needed to be accomplished and how it should be done before diving in. In addition, we didn’t plan for the unexpected. There will always be surprises when building something big and new, so it’s important to build in time to rethink the design when these issues come up rather than hacking these additional features on later.</p><blockquote>Note: As a startup, sometimes things just have to get done and you don’t always have the time and resources to plan as thoroughly as you want. BUT it can really help in the long run for maintainability and extensibility, so definitely try to allocate time for planning!</blockquote><h3>How do we avoid this in the future?</h3><p>Over time we’ve come up with a process that we’ve used to define better interfaces for API endpoints. This involves a bit more planning upfront and has enabled us to build more maintainable features. We will go through the steps of this process and illustrate how it works using the example of building our campaign flow. This project involved deciding how to store the data, how to send the data to the UI, and how to lay out the UI.</p><ol><li><strong>Schedule a meeting with the frontend engineer, backend engineer, product manager, and designer.</strong> Go over the requirements and design. Start the conversation about what should be handled by the frontend and what should be handled by the backend.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*hfi-i2EKAtKrym5i" /><figcaption>Design mock of the campaign flow.</figcaption></figure><p>2. <strong>Work on the frontend and backend technical design separately.</strong> Decide on how you would ideally structure and store your data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/890/0*q-DqIOd_TA_mgy9F" /><figcaption><em>Each box represents the objects that the frontend and backend would ideally have.</em></figcaption></figure><p>3. <strong>Bring the technical designs together.</strong> You can be a full stack engineer deciding this yourself; however, this coordination is especially important when you have separate frontend and backend engineers. In this discussion, be sure to go over the requirements and any UX designs for the end product again. This will allow you to make sure that you have accounted for all possibilities.</p><p>4. <strong>Find the commonalities between the designs.</strong> This is likely to be an iterative process. It is possible that you will find that there aren’t enough commonalities between the designs. In our experience, this often occurs because the backend is not handling enough of the business logic. This forces the frontend to implement this logic. Remember that keeping as much logic on the backend as possible can allow you to change how you store, process, and compute your data down the road, giving you more flexibility in the long run.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*4mgMeypkTwEgy8lO" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*5PYnpzUwLQpHcDf2" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*T6HRoCtt9AvZCsxb" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*PkM_c3-XMsxgPiCc" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*xBu8ctYx-efV_r6W" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*ozFkrNWkO-cQt1Hx" /><figcaption>We look for commonalities between the data presented. Initially, it seems like we will have a few separate objects. However, we end up having to go back to the drawing board and create a unified object that will be used for our entire flow. This allows our backend and frontend to have different data models with a common interface.</figcaption></figure><p>5. <strong>Make your API spec.</strong> This doesn’t need to be as formal as Swagger/Open API; it could simply be a shared document. Make sure that it is easy to iterate and update as it is likely that there will be changes needed as you write the code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*G7tAhdF5B-7p-LhV" /></figure><p>6. <strong>Have regular meetings to discuss unexpected complexities. </strong>These meetings should include the frontend engineer, backend engineer, product manager, and designer. This will allow you to make sure that you aren’t making design decisions in a vacuum that could negatively affect other engineers or the outcome of the project.</p><p>Over the past couple of years, we have had the opportunity to learn the hard way how important a well-defined interface is to testing, maintenance, and extensibility. Learning from our early missteps has allowed us to iterate more quickly and build high impact products for our customers!</p><p><em>Interested in working with us? Check out our careers page here: </em><a href="https://www.bluecore.com/careers"><em>https://www.bluecore.com/careers</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1029058e21a4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluecore-engineering/the-importance-of-a-well-defined-api-interface-in-building-a-ui-1029058e21a4">The Importance of a Well-Defined API Interface in Building a UI</a> was originally published in <a href="https://medium.com/bluecore-engineering">Bluecore Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Highlights from the Women in Technology Leadership Panel]]></title>
            <link>https://medium.com/@cameron.fleming/highlights-from-the-women-in-technology-leadership-panel-7a526fe8ec9a?source=rss-1a626d4a4be5------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a526fe8ec9a</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[technical-leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Cameron Rose Fleming]]></dc:creator>
            <pubDate>Tue, 25 Sep 2018 11:49:43 GMT</pubDate>
            <atom:updated>2018-09-25T21:24:30.655Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/885/1*GGtGooiyDgfsXkeutqlBwQ.png" /></figure><p>Last week I attended a <a href="https://www.eventbrite.com/e/women-in-technology-leadership-panel-tickets-48543035526">Women in Technology Leadership Panel</a> put on by Women Who Go and hosted by Datadog. Every time I attend an event for women in tech, I am excited by how many women I get to meet that code and have positions in technical leadership! I think I get so caught up in the day to day of being in a field that is so male dominated that I forget that there are women in leadership in software. The panel included the following women:</p><ul><li>Michelle Alexander, Senior Engineering Manager at Spotify</li><li>Lena Krug, VP Platform Engineering at Meetup</li><li>Arylee McSweaney, Senior Manager of Test Engineering &amp; Strategy at Etsy</li><li>Julie Sommerville, VP Engineering at Capsule</li><li>Sha-Mayn Teh, Tech Advisor at Teachers Pay Teachers</li><li>Chrys Wu, Cofounder of Write/Speak/Code</li><li>Jenna Zeigen, Senior Frontend Engineer at Slack</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mQMvL1HGLKkj3Ef4ISr_bw.jpeg" /></figure><p>The women on the panel entered management for a diverse set of reasons from wanting to do better than current management, to enjoying understanding how people work together, to wanting to have a say in what the company is doing. The panel focused on how these women became managers, the difficulties they had transitioning into management, and advice they have for people that are interested in management. As a tech lead deciding whether I am ready to pursue management or whether I want to stay a (mostly) individual contributor for now, it was incredibly helpful to get some advice from these women.</p><h4>Difficulties transitioning to management</h4><p>It can be hard to go back to being a beginner at something. Usually you get promoted to management because you are doing well at your job, but being an engineer and being a manager are very different.</p><ul><li>It’s not always easy to trust the people you manage to do their job. This is especially true if you haven’t worked with them before. It can be hard knowing that you are ultimately responsible for the work that they do.</li><li>You can’t just take on their problems as your own. You have to learn to coach and mentor them to solve their problems rather than solving them yourself, otherwise you will have WAY too many problems to solve.</li><li>It can be emotionally draining. You are responsible for the technical output as well as the happiness of the team. Note: Stacking one on ones can be great from a scheduling perspective but can be difficult from an emotional perspective.</li><li>Colleagues and friends aren’t the same once you are their manager. Find a network outside of this group. Find a work peer that can help you navigate the transition. Make sure to find someone that can be there to help you when you have problems as well as simply listen to you when you have a bad day.</li><li>You don’t get the immediate feedback/high of fixing a bug.</li><li>It’s important to have empathy, but at the end of the day you are responsible for the whole team so sometimes you do have to make hard decisions that not everyone will like.</li></ul><h4>Strategies for supporting your team</h4><p>It’s important to build trust with your team and make sure that they are progressing properly.</p><ul><li>Set expectations early on with respect to promotions and where your report is in that process. Make sure to discuss it regularly. If someone asks for a promotion, figure out if it’s the right time collaboratively: you should each use the leveling matrix to fill out how you think the person is doing and come together to discuss.</li><li>Hold strategic 1 on 1s. Make sure they aren’t just tactical. Be sure to ask your report about their goals. Make sure to give timely feedback. Try <a href="https://www.beplucky.com/shop/">https://www.beplucky.com/shop/</a> for 1 on 1 inspiration.</li><li>Clarify what stakeholders want before going back to your team with what the team will be working on. This will enable you to build trust with your team and build the right solution.</li><li>Make a list of good things that coworkers said about your report that you can give to them. They can then reference this when they are having a bad day.</li></ul><h4>Strategies for your career</h4><p>Make sure to think about what you want out of your career and plan how to get there.</p><ul><li>Treat your career like a marketing/PR campaign. You are selling yourself. Make sure that you keep track of what you do. Think about how to get known for what you are doing. It’s important to find things you enjoy, but also think about how to use it to sell yourself.</li><li>Find teams where there are managers and leaders that will sponsor you and help you to grow.</li><li>When interviewing, call out the business impact of what you have worked on, not just the technical details.</li><li>Remember that getting promoted is a process. It doesn’t happen overnight. You need to plant the seed and water it over time.</li><li>Find people that you want to emulate.</li></ul><h4>Mentorship/Sponsorship</h4><p>It is really helpful to have mentors and sponsors to help you along in your career. Building these relationships takes time and looks different for everyone.</p><ul><li>You don’t have to have one “mentor”. You can have multiple people that help you with different facets of your life and career.</li><li>When looking for a mentor, have a specific ask. Don’t just ask someone to be your mentor. Know what your goal is in getting a mentor and what are you looking for out of this relationship.</li><li>Your sponsors don’t have to be people that are above you in the management chain. They can also be your peers. You can speak on each other’s behalf.</li></ul><h4>Dealing with feelings of inadequacy</h4><p>No matter what point you are at in your career and how much you have accomplished, feelings of inadequacy may happen from time to time or all the time.</p><ul><li>Just because you have failed at something doesn’t mean that you are a failure.</li><li>When you feel like you are falling apart, remember that others feel like this too. It’s okay to have these emotions, and you will get through them.</li><li>If you don’t understand something initially and are panicked, take some time away to calm down and come back with fresh eyes.</li><li>For women, remember that men are much more likely than women to apply to things where they don’t meet all the criteria. Just go for it.</li></ul><h4>Resources</h4><ul><li>Being an engineering manager and taking care of yourself — <a href="https://medium.com/@kellan">https://medium.com/@kellan</a></li><li>Becoming a good manager — The Manager’s Path and <a href="https://larahogan.me/">https://larahogan.me/</a></li><li>Career levels — <a href="http://dresscode.renttherunway.com/blog/ladder">http://dresscode.renttherunway.com/blog/ladder</a> and <a href="https://medium.com/s/engineering-growth-framework/engineering-growth-introduction-8ba7b78c8d6c">https://medium.com/s/engineering-growth-framework/engineering-growth-introduction-8ba7b78c8d6c</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a526fe8ec9a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>