<?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[Code Carrier - Medium]]></title>
        <description><![CDATA[We’re a motley crew of shipmates: mad data scientists, musicians, software engineers, and tinkerers. These are our musings on code, culture, data, and product. - Medium]]></description>
        <link>https://medium.com/code-carrier?source=rss----ed839bb7ce09---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Code Carrier - Medium</title>
            <link>https://medium.com/code-carrier?source=rss----ed839bb7ce09---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:57:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/code-carrier" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Sailthru Values in Action]]></title>
            <link>https://medium.com/code-carrier/sailthru-values-in-action-d187da5093c3?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/d187da5093c3</guid>
            <category><![CDATA[values]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Evan O'Connor]]></dc:creator>
            <pubDate>Wed, 22 Jun 2016 15:13:53 GMT</pubDate>
            <atom:updated>2017-01-03T13:49:49.999Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v9U1H28PPA_u-XlUz6ZqZg.jpeg" /><figcaption>The unbeatable view from our HQ in downtown Manhattan</figcaption></figure><p>Though I only recently became a full-time Sailor, I have actually spent over a year working here in a few different roles. I have watched the company mature immensely through my previous roles– first as a summer intern in 2015 and then as a part-time engineer while I finished my computer science degree at Columbia. Having completed a few other internships during my undergraduate career, I expected that Sailthru would follow suit. One preconceived notion that I held was that there was a clear distinction between interns and the rest of the company. I thought interns usually could not touch production code and were given busywork. I expected that as long as I helped out with basic tasks, my coworkers would be satisfied, as it meant that they did not need to sacrifice their own work to teach me.</p><p>When I began at Sailthru, I was not entirely sure what it meant to be a software engineer. My past experiences led me to believe that I would constantly be overwhelmed by unfamiliar jargon and forced to attend regular meetings that did not make sense. I had worked in companies that claimed to use agile methodologies, though even after three years, I was not sure what that meant. I previously understood a company’s values as abstract concepts written by the CEO that everyday employees did not bother to follow.</p><p>On my first day as a Sailthru summer intern, all of my preconceived notions about a software company were reversed. My initial reaction was that my new coworkers actually cared about my personal and professional growth. At Sailthru, I see people directly embodying our values every day on every team. It doesn’t take long upon entering our SoHo office to start seeing examples of people sticking to our core values. Let me provide some examples of how I first saw and continue to see our values embodied on a daily basis.</p><h4>Passion with Purpose</h4><blockquote>In a digital world, we believe that human connections matter more than ever. This guiding principle shapes the passion and enthusiasm we bring for our teams, our customers, and our shareholders.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pjIEztlw8fATn6FWMqaWJQ.jpeg" /><figcaption>Our communal kitchen where we conduct our unique culture fit interviews</figcaption></figure><p>At the heart of Sailthru is our desire to bring back personal connections to online marketing. In this age of tech, when many customer-to-brand interactions happen online, it is difficult to get a sense of the values a company upholds. We want to change this by making the interactions between our clients and their users more personal. Not only do we create human connections via our platform, but we use this mantra to recruit new hires. Everyone who interviews in our office goes through a culture fit interview. We try to imagine what it would be like to bounce ideas off one another around a whiteboard. We want to gauge if we could have a lively conversation with this person in our communal kitchen or at our coffee bar. Not only do we strive to hire people with the best technical skills, but we want people who are driven by passion, in and out of the office. We find these people by not just asking about their technical background, but by listening to interviewees talk about their favorite hobbies and weekend activities. By looking for new hires who share our passion and warm attitude, we have cultivated an ideal atmosphere that is encouraging, enlightening, and engaging.</p><h4>Driven by Customer Success</h4><blockquote>We define Sailthru’s success by the value we create for our customers. Customer success drives our strategy, our decisions, and our investments.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sGU5VZ47yNH6pljGyxL5oA.jpeg" /><figcaption>We proudly show off the diverse logos of the companies that use our products</figcaption></figure><p>Our standard of writing value-oriented user stories for all of our tickets is a prime example of the emphasis that Sailthru places on customer success. Whenever we create a new story for the backlog, we make sure that it is clear to everyone what tangible value the user gets from that story. In our bi-weekly sprint planning meetings, we discuss each story in detail to make sure everyone understands the value to the user. This process ensures that the engineering team is prioritizing their time with work that will directly benefit our clients’ Sailthru experience. That is why multiple times a day, when we deploy code, our customers can see noticeable improvements to the Sailthru platform.</p><h4>Results Matter</h4><blockquote>We measure ourselves by what we accomplish, and how we convert our passion into impact. We recognize that getting things done requires collaboration, focus and execution.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NJa06EnrkwF2igetPNN48Q.jpeg" /><figcaption>The relaxed atmosphere of our office makes every day enjoyable</figcaption></figure><p>We cultivate what is known as a Results Based Work Environment. This means that we emphasize employee performance over face time in the office. Our employees have the freedom to choose how to customize their schedules and working styles to maximize productivity. The goal is to improve accountability and autonomy as well as decrease response times. We do not judge how people spend their time and use clearly defined goals to measure success. These goals are set with managers at weekly one-on-one meetings, which provide a private time to discuss a wide range of personal and professional matters. While we do value regular group meetings, we understand how hard it can be to get work done when our days are swamped with them. For this reason, meetings are often optional and employees can call into them and multitask at their own discretion. We aim to hire responsible, independent workers, who we can trust to best manage their own time. We don’t bother with red tape here and allow our employees to follow their preferred working style to maximize their productivity.</p><h4><strong>Integrity and respect in all interactions</strong></h4><blockquote>We are honest, fair and respectful in our behavior with fellow team members, clients, prospects, and partners. We act with integrity, only tolerating constructive engagement.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FVzc2IyoZ0zhMwxxQoE8Lg.jpeg" /><figcaption>Everyone is encouraged to speak up, regardless of how much experience they have</figcaption></figure><p>In our office, all voices are respected equally. No matter if I was an intern, part-time, or full-time, my opinions were equally valued at meetings. Even when senior leaders at the company were in the room, I never felt that I had to hold in my thoughts to let other more experienced people speak. As an intern, I was encouraged to challenge myself to my full potential. Within my first two weeks, I had already engaged in our entire development process– writing code, creating unit, integration, and quality assurance tests, presenting demos, and deploying production code. Right away, I gained a better understanding of the process of releasing high quality software. At every step of the way, my opinions were sought even by senior developers. At Sailthru, we value new perspectives and discussion over being right. As long as you are listening and engaged, it does not matter how silly an idea may seem. In the end, the more voices that speak up, the more likely we are to examine all angles of a problem to find a proper solution, avoiding unnecessary bugs and chaos.</p><h4><strong>Data to decide, courage to act</strong></h4><blockquote>Decisions come from data. We seek to avoid confrontations of opinion, and instead use the best available data to make decisions. We must have the courage to act when data lead us to make difficult choices. But we must also have the openness to admit prior mistakes and learn from them.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n5hwTJkJ1kKuY07JITLOtA.jpeg" /><figcaption>We accept that mistakes are inevitable and seek to turn them into learning experiences</figcaption></figure><p>In the center of our office, you can find huge screens full of live metrics of our system health. Our Site Reliability Engineers manage these dashboards and monitor them to prevent downtime and errors for our clients. Knowing the constantly increasing complexity of our system, we use these data to guide our day-to-day actions. Anytime we have problems with our system, we carefully document the causes of the problems and ways to prevent them. We are not ashamed to call each other out for mistakes. Our supportive work environment never seeks someone to blame. Instead, we use these moments to improve our understanding of the system and create processes to avoid mistakes. These same data analysis methods are employed by each sprint team. Each morning, we update the number of hours remaining on subtasks and track our progress on a burndown chart. We are quick to call out tickets that are at risk of falling behind. Rather than complain that a team member is not working as fast as we would like, we offer our extra time to help get tickets through the pipeline.</p><h4><strong>Grow, innovate and improve</strong></h4><blockquote>We will always innovate, challenge the status quo, and take calculated risks to move forward. We push ourselves; we try new approaches, continuously learn, and explore.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lq6LNsFy2P_4X98cjxGIrA.jpeg" /><figcaption>Every week our teams seek to improve so we can deliver more value to our customers</figcaption></figure><p>Every two weeks on the last day of our sprint, each team gathers in a room for a sprint retrospective. We begin these meetings by having each team member provide a happiness score for the sprint and name one positive and one negative experience. Then we engage in a group discussion about what we did and did not do well, as well as what we can improve on for the next sprint. In my experiences at other companies who engaged in sprint retrospectives, these meetings seemed abstract and there was little follow up for actionable items. At Sailthru, we review the retrospective document from the previous sprint to make sure that we are constantly improving and learning from our challenges. Otherwise, this meeting would not actually improve our productivity. In addition, when evaluating a new ticket, we determine its level of difficulty by comparing it with past tickets of similar complexity. This strategy allows us to increase our velocity (the number of “story points” we complete every sprint) as we becomes more comfortable with the code base and with working as a team.</p><h4>One Sailthru</h4><blockquote>We are one team that succeeds together, fails together and learns together. As One Sailthru we transcend the boundaries of geography, product, role and function, and operate as a single team, aligned for our customers’ success and the success of Sailthru.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CoN5uwZ6RH7ZKgeErfghgw.jpeg" /><figcaption>The sea of Sailthru blue throughout our office reminds us that we are one big family</figcaption></figure><p>This final Sailthru value really ties together every point I have been getting at– we are one big family. One of the reasons why we are so successful at coordinating inter- and intra-departmental tasks is that we are comfortable with one another. Our weekly Thursday catered lunches and evening happy hours provide a reserved time to get to know everyone in the office. Rather than only being comfortable asking for help from one’s own team, we are encouraged to be friendly with everyone at the office. This results in a noticeable improvement in productivity. At previous internships, I would spend hours stuck on a problem that I quickly realized I could not solve without help. At Sailthru, if I am stumped by a problem, I am not afraid to grab someone from any team if I need assistance. Our open office design–filled with communal desks and glass-walled meeting rooms– limits the time it takes to seek out a coworker. When I require help solving a problem, not only is the person I ask happy to assist, but they end up teaching me additional lessons about our system purely because they enjoy helping others. I look forward to coming into work every day, not just to learn new technologies, but to hang out with this giant group of caring and interesting people. As a twenty-something just beginning my professional life, I could not be more satisfied where I have ended up. Everyone at Sailthru knows how precious our culture is and we understand that cultivating these values is essential to maintaining this perfect balance of learning, teaching, and fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d187da5093c3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/sailthru-values-in-action-d187da5093c3">Sailthru Values in Action</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Orchestrating AWS with Ansible]]></title>
            <link>https://medium.com/code-carrier/orchestrating-aws-with-ansible-e80a3bdf027b?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/e80a3bdf027b</guid>
            <category><![CDATA[ansible]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[Taras Lipatov]]></dc:creator>
            <pubDate>Wed, 13 Apr 2016 15:33:43 GMT</pubDate>
            <atom:updated>2016-04-13T15:33:43.589Z</atom:updated>
            <content:encoded><![CDATA[<h4>Managing the entire stack</h4><p>At Sailthru, Using a single configuration management system across the board gives us the power of portability and re-usability. By managing our cloud infrastructure with Ansible, we can reuse processes, plays and roles that we use to manage our on-premise environments.</p><h3>Modeling the environments</h3><h4>Before roles and playbooks, we need data.</h4><p>Because of the dynamic nature of AWS and managing multiple environments across multiple accounts (profiles), the data representing our environments needs to be dynamic and hierarchical. Out of the box, Ansible is not geared to support such a model, even with using the the EC2 dynamic inventory, we are still limited to static host and group vars for storing data.</p><h4>Extending Ansible</h4><p>Fortunately Ansible is extremely flexible and can easily be extended with modules or plugins.</p><p>Our first step was to build a drop-in replacement for group and host vars that would allow us to represent the AWS environments as a hierarchical key/value store similar to puppets hiera.</p><p>The requirements:</p><ul><li>Name spaced hierarchies</li><li>Top down merging of hashes and lists</li><li>Pluggable back end</li><li>Multiple ways to access data: as a module, as an action or as a lookup</li><li>Process the data through Ansible’s Templar to embed lookups, variables and JINJA functions</li><li>Support vaulted yaml or json data files</li></ul><h4>Welcome Echelon</h4><p><a href="https://github.com/sailthru/ansible-oss/tree/master/tools/echelon">sailthru/ansible-oss</a></p><p>Using echelon we can layer our environment data:</p><blockquote><strong><em>echelon.yml<br></em></strong>hierarchy:<br> aws/{{ profile }}/{{ env }}/ec2-{{ region }}<br> aws/{{ profile }}/{{ env }}/default}</blockquote><p>The data:</p><blockquote><strong>aws/account1/dev/ec2-us-east-1.yml</strong><br>ami_id: ami-123456</blockquote><blockquote><strong>aws/account1/dev/default.yml</strong><br>security_groups: ssh-from-wan</blockquote><p>Echelon will resolve the hierarchy via the backend plugin(s) and return the key/values, which can then be accessed in playbooks or roles as</p><blockquote>ansible-playbook site.yml -extra-vars “region=us-east-1 profile=account1 env=dev”</blockquote><blockquote><em>- debug:<br> msg: {{ aws }}<br>-&gt; { ‘</em>ami_id’: <em>‘</em>ami-123456<em>’: , ‘</em>security_groups’: ‘ssh-from-wan’ }</blockquote><p>or as a lookup</p><blockquote>- debug:<br> msg: “{{ lookup ( ‘echelon’, ‘aws.ami_id’ ) }}”<br>-&gt; ami-123456</blockquote><p>Because Echelon has a pluggable backend, we can make our data even more portable by having Echelon perform lookups against an API or a database such as Redis</p><h3>Local artifact repositories</h3><h4>Don’t rely on 3rd parties</h4><p>It is extremely important to be in control and that means storing all your system and application packages in private repositories local to your environment. Whether its a Docker image or a CentOS rpm, if your system needs it to run, it should always live in a repository that you own or at least a proxy. Because if a 3rd party hosted package suddenly becomes unavailable, you are at their mercy. As the former Netflix C.T.O. and mentor Adrian Cockcroft taught me: “You just have to build for it”.<br>The peace of mind that you get from spending the extra effort in integrating this in to your infrastructure will be well worth it. Not to mention the gained benefit of artifact transfer speeds.</p><h3>The AMI build environment</h3><h4>Build everything ahead</h4><p>Rolling custom AMI’s is crucial to quickly scaling an environment. Pre-loading alleviates most on-the-fly configuration management and instances can start performing their intended tasks right away. When working in the cloud, time is literally money.</p><p>Just like all environments, the AMI build environment is just that, another environment represented by data that is fed to roles from a playbook.</p><p>The build process is completely handled by Ansible and kicked off from Jenkins. <br>We start by firing up a reference instance using the core ec2 module and check for its availability using our <a href="https://github.com/sailthru/ansible-oss/blob/master/modules/cloud/amazon/ec2_instance_status_checks.py">ec2_instance_status_checks.py</a> plugin. Once up, Ansible can ssh and configure it to our liking.</p><p>Ansible strips any traces of cloud-init (we don’t need it), installs all prerequisite components for our stacks and adds a simple <em>rc.local </em>script which is responsible for fetching the ssh key and boot script from user-data at boot.</p><p>After a successful play, Ansible will create the new AMI, register it and remove any old AMI’s (we like to keep last 5) using the core ec2_ami module.</p><h3>Scaling fast and reliably</h3><h4>All instances are launched in autoscale groups</h4><p>Using the core ec2_asg module we launch even a single instance in an ASG. This gives us continuous protection from the instance going down.</p><p>When launching, a userdata script is generated and passed to the autoscale group. This script is then launched by every instance that comes up. The user data script writes local facts which are used to set the instance persona, then downloads a playbook payload from S3 and launches Ansible against it. Ansible then goes ahead and configures the instance based on what was set in the local facts.</p><p>Because configurations are pre-packaged with the applications and most prerequisites are pre-baked during the AMI build process, this step mainly focuses on simply managing services.</p><p>By eliminating almost all launch-time configuration management, we ensure that instances scale up fast and reliably.</p><h3>Everything is disposable and reproducible</h3><h4>One way in to the void</h4><p>Once services are up, there is no need to continue to manage them. This is a waste of time and resources as instances are constantly scaling up/down. If we need to make any modification to an ASG or application, we simply blue-green deploy a new ASG by modifying the data in Echelon to set old and new ASG values and have Jenkins kick off Ansible.</p><p>Ansible then makes the environment look like its representation in Echelon. This data to environment (one-way) model allows us to quickly re-configure and re-provision any part of the stack.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e80a3bdf027b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/orchestrating-aws-with-ansible-e80a3bdf027b">Orchestrating AWS with Ansible</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Data Science to Personalize the Customer Experience]]></title>
            <link>https://medium.com/code-carrier/using-data-science-to-personalize-the-customer-experience-d1ea6200f00c?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/d1ea6200f00c</guid>
            <category><![CDATA[personalization]]></category>
            <category><![CDATA[marketing]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Sailthru Engineering]]></dc:creator>
            <pubDate>Wed, 17 Feb 2016 18:43:54 GMT</pubDate>
            <atom:updated>2016-02-17T18:43:53.683Z</atom:updated>
            <content:encoded><![CDATA[<p>David Glueck, VP of Data Science, and Div Vats, Senior Data Scientist, recently gave a talk to students at the Columbia University Center for Pricing and Revenue Management.</p><p>They describe how they use data science to personalize the customer experience, go in-depth on building data science as a service, and take a look at Prediction Manager, one of the data science-powered products Sailthru offers.</p><p>Click to watch the video below:</p><p><a href="https://cbs360.gsb.columbia.edu:8443/ess/echo/presentation/27fbf5a0-2cd0-4920-a6c3-f01d8edd75ee?embed=true">Echo360</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1ea6200f00c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/using-data-science-to-personalize-the-customer-experience-d1ea6200f00c">Using Data Science to Personalize the Customer Experience</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[11 Impressions as a (New) Sailor]]></title>
            <link>https://medium.com/code-carrier/10-impressions-as-a-new-sailor-b9275c59e8bd?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/b9275c59e8bd</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Mike O'Brien]]></dc:creator>
            <pubDate>Fri, 08 Jan 2016 19:54:43 GMT</pubDate>
            <atom:updated>2016-01-11T16:32:48.538Z</atom:updated>
            <content:encoded><![CDATA[<p>I joined Sailthru in September 2015, and I’m happy to have the opportunity to share my ongoing impressions of the company and its people. I am probably not the typical new-hire at a software start-up — I had a long career working in Corporate America before I got here, and the contrast between working in the tech department of a giant corporation, versus joining a young and rapidly-growing start-up, has been eye-opening.</p><p>These are my 10 impressions:</p><h4>1. “I want to work here”</h4><p>I arrived early, so I had time to walk to my interview through the beautiful Soho / West Village area where the office is located. This was always my favorite part of New York City, which means, one of my favorite places anywhere.</p><p>I rode the elevator to the 12th floor, stepped through the Sailthru entrance door, and thought, <em>“I want to work here” b</em>efore I’d even taken off my jacket.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gFl-mTuncQdG00c4aFQ2QQ.jpeg" /><figcaption>View of the Freedom Tower, Hudson River, and New Jersey — out of the 12th floor window.</figcaption></figure><p>The place has a <em>vibe</em>. I’m not sure I can explain it. The physical space is an older, loft-style space, which means it is built on a human scale, and there is ample daylight.</p><p>Everyone sits in an open-plan floorspace (yes, <em>everyone</em>) and there are a hundred conversations going on at once. These people are <em>engaged</em>. There’s music playing — might be classic rock or Motown, might be 80&#39;s pop or reggae— that adds to the sense of energy. A gong sounds when we sign a new customer, and everyone applauds.</p><p>The place <em>hums</em>.</p><h4>2. Agile: we walk the walk</h4><p>The Agile Manifesto was published in 2001, and practically every place I’ve worked since then has claimed to be “doing agile”. None of them are. Sorry, former colleagues: there’s more to agile software development than having a Daily Standup.</p><p>Sailthru as a company is committed to Scrum software development, from the CEO on down. (If you’ve ever tried to implement Scrum without upper-management support, you know how huge this is.) The whole company lives and breathes the two-week sprint cadence. Product managers attend Standups every day. There’s no throw-it-over-the-wall. No 200-page specs.</p><p>Sprint teams are self-organizing, selecting our work from the top of the prioritized product backlog for each sprint, and committing to getting it done. We update our JIRA tickets and look at the burndown chart every day, and cheer or groan. We get daily feedback from our Product Owners and respond to it immediately, so we always know that the product increments we’re building match spec, functional expectations, and ultimately deliver value for our customers.</p><p>Oh, and we ship (get it?) code every day. Usually, several times a day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a9Sclz1LbpeE7SrIJcZZrQ.png" /><figcaption>Burndown chart for our Kingsguard sprint team — consistent downward slope means progress and productivity.</figcaption></figure><h4>3. Egalitarian by design</h4><p>No one has an office here. We basically have a huge open floor area with rows and rows of identical flat desks with Macs on them. The CEO? He sits at a desk exactly like mine, three desks down. I could hit him with a spitball from here (not that I would, of course).</p><p>One more thing: Meetings start on time and end on time. We are respectful of everyone’s time because we all want to just Get Things Done — one of our core values — so we’ll discuss, decide, and do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RnKdLXpnygVmuHpcNxuvxA.jpeg" /></figure><h4>4. TDD (Test-Driven Development)</h4><p>The 30-minute take-home coding test for new candidates here is of the form: “Here are some unit tests that fail. Write code so they pass”.</p><p>The three-hour on-site coding test (which you only get to take if you do well with the take-home test) is also of the form: “Here are some unit tests that fail. Write code so they pass”.</p><p>If you love test-driven development as I do, this should put a smile on your face.</p><p>Are we as test-driven as I’d like? Not yet, but here are a few things to get us closer to the goal:</p><ul><li>Test coverage metrics — percentage of lines of code that are covered by tests</li><li>Linking those metrics to the build, so that the build fails if the metrics drop</li><li>Incorporating test-coverage as a standard part of our process so that every ticket has an associated subtask to write tests</li></ul><h4>5. Radical transparency</h4><p>At most of my past jobs, we would hear about glowing reports on KPIs, but never actually heard anything about hard dollar figures.</p><p>At Sailthru we talk about money all the time: How we earn it, how we spend it, where we need to invest, where we need to conserve, whether and when we’ll need to raise more capital. As though we were partners and colleagues in the business; as though we were grown-ups who could be trusted with the information we need to do our jobs effectively, within the broader context of our company’s financial performance and health.</p><h4>6. The perks of embracing start-up life and culture</h4><p>All my working life I had shied away from joining a start-up, even though, in tech, that’s where the action is. I feared the lack of job security, and the frantic pace. So I spent decades working in Corporate America — where I <em>still</em> didn’t have job security, and I got the frantic pace <em>anyway</em>!</p><p>The benefits and perks at Sailthru are so much better than anyplace I’ve ever worked that it amounts to a qualitative difference. Now, I’ve come to understand that this is fairly common in the start-up world. But still: full health benefits for myself and my family, paid in full by my employer. A fully stocked kitchen (including adult beverages). Weekly free lunches. Biweekly chair massages. Stock options. Unlimited vacations.</p><p>There’s even a generously funded “Personal Growth Program,” to be used in any way that helps you grow as a person. So far, I’ve used mine to take a drum lesson with a famous drummer; other people have taken flying lessons, and even cooked with the NY Jets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5aakDFRVgb-QW1ogP8yPFA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zKA7Q2Aeti4QIFY86uS-xw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_g2plTAR0kTgg8LiuDPWnw.jpeg" /></figure><p>Don’t underestimate the importance of that shared, stocked kitchen. It encourages conviviality and the sense of being on a team together — like eating in the dining hall with your classmates when you were in college. It was one of the things that made me say “I want to work here” when I first walked through the door.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aNoS2UmDzONVOd9_ez78eA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PFLaSUO6xS0LbQvCMxlwYA.jpeg" /></figure><h4>7. Not just a department, but a whole company around tech</h4><p>The contrast between working in a tech company, versus working in a tech department of a non-tech company, is stark. Here, everyone “gets it,” because the technology <em>is</em> the product. You don’t have to explain why developing software takes time and resources, because the founders and the CEO are all technologists themselves. You don’t have to fight for tools, or argue for best practices. You’re not asked to cut corners, or pressured to trim an estimate to fit someone’s predetermined schedule.</p><p>All that time and energy I used to spend fighting to be allowed to develop code “the right way”? Now I just spend that time and energy developing code.</p><h4>8. Non-stop fun</h4><p>So far in my three months here we’ve had: a rafting outing; a Halloween costume party; a holiday party (dinner and open bar, plus-ones invited); Team Trivia Night (which I crushed); a movie screening; and two release parties. Not to mention numerous team lunches, the weekly Thursday evening “Sail-Ale” after-work drinks, and frequent impromptu Game Of Thrones board-game sessions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l58-Ybxqqk_ArmOHOxIcPw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ENiUi7EqUTs_FzoWoQ6ByQ.jpeg" /><figcaption>Halloween shenanigans + annual “sailing” trip down the Delaware River</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s6f6KK1QYKa89jhOBKOZ5Q.jpeg" /><figcaption>BubbleBall with people across all departments</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZTOFUw-IE1zWRIih5nZrfA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4XepuRmMRl0uZ0CzsNX2VQ.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ur4MQBfqPnWV9NB-yIh-nA.jpeg" /><figcaption>Board games during our bi-annual Dev Lodge + “Where’s Waldo?” + first Halloween at Sailthru</figcaption></figure><p>These people seem to genuinely like each other. Weird.</p><h4>9. Teamwork, making the dream work</h4><p>The mentality and attitude here is that we work together as a team, and we succeed or fail together as a team. It’s a blame-free culture: we don’t point a finger and say “you got it wrong” — we’re self-organizing, so we keep each other accountable for the work we commit to doing, and help each other whenever we can in order to just get the job done.</p><p>We do still recognize and celebrate individual successes, calling them out at All Hands meetings and also handing out the coveted Admiral Award to those who consistently go above and beyond their daily roles and expectations.</p><h4>10. Hiring interesting, smart, and different kinds of people</h4><p>The founders of Sailthru are some of the coolest, smartest people you’re likely to meet, and that has worked its way into the DNA of the entire organization. Five months in and I have yet to meet anyone I need to avoid; there’s no one I dread running into, no one I’m hoping will quit. It’s refreshing.</p><p>On the flip side, I have met: the systems engineer by day, bass guitarist by night. The data scientist who made his own 3D printing robot from scratch — and then 3D printed his engagement rings. The team lead who’s made more than 300 skydives. The IT manager who makes gorgeous pottery and shoots photography. The Deliverability Specialist who had a former life as a gymnast.</p><p>We all learn from each other’s backgrounds, experiences, and even hobbies, creating an environment of dynamic discussions and creative problem solving.</p><p>Everyone brings something unique to the table.</p><h4>11. There’s real diversity here</h4><p>Sometimes I think we look like one of those “United Colors of Benetton” ads; it’s almost a cliché, how multicultural and diverse we are. I’m not aware that it’s part of any master plan, or a mandate from the People team; it’s just what happens naturally when cool, smart people hire cool, smart people in the most diverse city in the world.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aBUj-iMeI7NAK908vz8WDQ.jpeg" /><figcaption>United Colors of Sailthru?</figcaption></figure><p>It seems so normal to me — my whole life in tech I have worked with people from all over the world — but I realize we’re in a rarefied bubble. When I hear about racism, sexism, homophobia, etc. happening in the world outside our bubble, I feel like — huh? what? In the 21st century, this is still happening?</p><p>We are a model of how the future will look. I hope.</p><blockquote>Mike is a backend engineer on the Personalization Manager sprint team. When he’s not coding, he’s playing drums or taking his kids on adventures.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b9275c59e8bd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/10-impressions-as-a-new-sailor-b9275c59e8bd">11 Impressions as a (New) Sailor</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Principles for Re-Architecting Subsystems for Reliability and Growth]]></title>
            <link>https://medium.com/code-carrier/evolving-personalized-email-at-sailthru-fd802e63fb00?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/fd802e63fb00</guid>
            <category><![CDATA[systems-thinking]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Rob Williams]]></dc:creator>
            <pubDate>Fri, 04 Dec 2015 20:02:46 GMT</pubDate>
            <atom:updated>2015-12-04T21:19:23.863Z</atom:updated>
            <content:encoded><![CDATA[<h3>3 Principles for Re-architecting Subsystems for Reliability and Growth</h3><h4>Simplify and Scale Out. Test Aggressively. Measure Everything.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WNjrA-BWyhrWoe77zL9KyA.png" /><figcaption>Grafana dashboard showing MTA server performance over time (Y-axis labels redacted)</figcaption></figure><h3>The Team and The Project</h3><p>The Site Reliability Engineering (SRE) team at Sailthru is focused on three main goals:</p><p>1. Increase system stability<br>2. Reduce incidents and alerts<br>3. Improve monitoring</p><p>To achieve these goals, we spend a lot of our time proactively re-architecting subsystems before they hit their limits. By monitoring traffic patterns and subsystem performance, we can identify systems that need to be rebuilt to accommodate our accelerated growth and scale. Then the team will hit the whiteboards and redesign the system from scratch so that it can handle the load we expect for the foreseeable future.</p><h4>RE-ARCHITECTING THE MAILING SYSTEM</h4><p>The SRE team identified the legacy email system as the top priority this year, before the holiday season rush. Our customers use this product and its underlying subsystems to create and send billions of personalized messages per month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1xKUnMA1pkCh0lYX7CUI2A.png" /><figcaption>Year-over-year comparison of our mailing volume growth, almost doubling since last year — illustrating the need to re-architect the mailing subsystem. (Y-axis labels redacted)</figcaption></figure><p>As we monitored the aggressive growth in message volume shown above, we anticipated that our legacy, sequential processing system would soon be pushed to its performance limits. So we needed to build a faster, parallelized system that would ultimately let our customers be more responsive to their changing needs while also getting more messages sent.</p><p>We successfully completed this year-long project on time (before the massive holiday rush) by keeping these 3 guiding principles top of mind:</p><blockquote>1. Simplify and scale out<br>2. Test aggressively<br>3. Measure everything</blockquote><h3>Rebuilding the Mailing System</h3><h4>SIMPLIFY AND SCALE OUT</h4><p>There are two major processes for personalizing email content:</p><ol><li>Define the audience — the dynamic list of people that will receive the email. The list is generated by a series of complex queries run across each client’s entire customer base. For example, a marketer looking to send out a new coupon for 20% off a $100 purchase at an LA store may want to find all customers that: 1) have opened in the last 30 days, 2) perform the majority of their opens in Los Angeles, 3) have not purchased anything recently, and 4) are statistically likely to spend $100 or more.</li><li>Construct and send a personalized message — the right content to the right person at the right time. Messages are composed in a Turing-complete <a href="http://getstarted.sailthru.com/new-for-developers-overview/zephyr-syntax/zephyr-syntax-overview/">templating language</a>, so the possibilities for granular control are almost limitless: for example, using a few {if}…{else} statements, a campaign sent to 1M people can send 1M completely different messages, each message personalized with the most relevant content to that specific customer’s interests and click history.</li></ol><p>Legacy systems at Sailthru tend to revolve around a single MongoDB cursor, where a single PHP process loops through the results of a query and performs business logic in each iteration. This serial processing has a low ceiling for scaling, and also carries with it some serious resiliency problems: a DB failover can cause long-running processes to restart from the beginning.</p><p>In the legacy mailing system, the user-defined query for a campaign audience would result in a complex MongoDB query. Each profile returned would have to undergo application-level matching (since not all the query criteria can be expressed within the MongoDB query language), and is written to disk in preparation for mailing. This serial process started to approach many hours for large, multi-million-user campaigns, and required a stateful handoff that would block until the cursor was fully iterated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0cWiEWs8M6atrfzqx-kw4Q.png" /></figure><p>The pattern that we have found to be very successful in addressing this type of legacy architecture is two pronged: Simplify and Scale Out. To simplify, the MongoDB query itself is reduced to something that will execute fast against a known DB index, and will only extract _ids from the database. To scale out, these _ids are put on a distributed queue (we use ActiveMQ) and consumed by stateless workers. The workers then perform a findOne to fetch the entire database document. With the full document in hand, the workers can do any business logic for matching and sending the message.</p><p>These changes allowed us to create a “stateless” process that was no longer sequential, so sending could happen as soon as the _ids were extracted from the database. We’ll review the performance gains in the concluding section.</p><h4>TEST AGGRESSIVELY</h4><p>Like <a href="http://readwrite.com/2014/05/08/gilt-eric-bowman-interview-scala-rails-jvm-reactive-platform">many</a> <a href="http://readwrite.com/2011/07/06/twitter-java-scala">startups</a>, Sailthru started with a dynamically typed scripting language (PHP) and is now moving new services to a more scalable language (Java). Java provides a <a href="https://prezi.com/fr8lerqzxewz/concurrency-options-on-the-jvm/">plethora of concurrency paradigms</a> that help to flexibly address all sorts of problems, and its ability to tightly control pooled connections to downstream resources is a huge win for our database team.</p><p>Porting code from dynamically typed single-threaded languages to statically typed multi-threaded languages comes with incredible challenges. That == (double-equals comparison operator) that used to “just work” in PHP gets expanded into a dozen lines of Java code. The cursory call to <a href="http://php.net/manual/en/function.strtotime.php"><em>strtotime</em></a> becomes a dizzying combination of regex and <a href="http://www.joda.org/joda-time/">Joda-Time</a>. PHP tends to ignore nullity and fail silently, while Java tends to be highly sensitive, throwing NullPointerException any time something is a little bit off. These issues are exacerbated by schema-less MongoDB documents that can have all sorts of data types mixed into the same fields.</p><p>The mailing re-architecture required porting an extensive library of code from PHP to Java, and we ran into countless edge cases. For this reason, we developed an aggressive testing strategy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/556/1*L297yQHeD8itHM0XF1DdTg.png" /></figure><ol><li>The developers wrote extensive unit tests, using 95% code line coverage as an initial metric to know when to stop.</li><li>Then, our QA team wrote an automated testing suite with 1800 test cases that compared the PHP and Java results for any discrepancies.</li><li>Finally, we conducted read-only testing in production using real client data.</li></ol><h4>MEASURE EVERYTHING</h4><p>The SRE team tries to measure as much as we can, but in some legacy systems it isn’t always easy. One major advantage of rebuilding a system is that measurement can be baked in from the beginning.</p><p>For Java services like the rewritten mailing system, we like to use the <a href="https://dropwizard.github.io/metrics/3.1.0/">Dropwizard Metrics</a> framework. It pumps metrics directly into Graphite, and then we use the <a href="http://grafana.org/">Grafana dashboard</a> tool as the frontend for monitoring what’s happening in real time. We like to measure all the external dependencies such as different databases, the cache, and many others so we can get anticipate potential bottlenecks in the system — and then address them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WC9dYWC3I9hzli8Gdozc6A.jpeg" /><figcaption>Partial view of the mailing dashboard (Y-axis labels and legends redacted)</figcaption></figure><p>There is a common question about how to alert based on Graphite metrics. We use a simple solution of PHP scripts that read the Graphite JSON web API, iterate through the results, and then do some simple statistics to detect if a threshold is exceeded. Finally, an automated process will trigger an alert via the PagerDuty API.</p><p>Measuring the performance in aggregate is very useful, but sometimes we want to dive into the details of what exact code is running slow. To tackle this, we use <a href="http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html">Flame Graphs</a>. This visual profiling tool helps identify, at a glance, which methods the CPU is spending time in. This has helped us identify quite a few bottlenecks in the Java standard library, as well as our own code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*669KdMPZx5n_x4fk0wSLeg.png" /></figure><p>These kind of changes are definitely micro-optimizations, but they tend to aggregate up the stack, so from a system level we’re being as smart as possible with our resources and code execution. We’ll revisit the flame graph after making the change, then measure and compare the performance or efficiency gain.</p><h3>Conclusion</h3><p>As a result of re-architecting and parallelizing the mailing system, we were able to horizontally scale and achieve an order of magnitude improvement in overall system performance — reducing hardware use by half, while increasing throughput.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xDsXePDGbiGkrLvgQVSKXw.png" /><figcaption>Comparing the legacy mailing system with the “stateless”, re-architected system</figcaption></figure><p>The above example shows the performance difference for a medium-sized email campaign for ~500k people: on the legacy system it took about 24 minutes to generate and then finish sending, but on the re-architected system, the entire campaign finishes <em>within</em> 2 minutes. As noted earlier, the big difference is that the new system does not block during the query (aka “generate”) step, so sending happens in parallel to those _ids being extracted from the database.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pn9op3XJwg3GHggGct03rw.png" /><figcaption>Comparison to a competitor system, on a very large and complex campaign</figcaption></figure><p>Most other competing email systems we’ve seen require a lengthy pre-generation step before sending, just as our legacy system once did. If a marketing team wants a campaign for 2M customers to start sending by 10am, they will often have to get everything set up and prepped by 8am or earlier. This severely limits the flexibility of the business, since publishers cannot react to breaking news and e-commerce companies cannot adapt to rapid changes in their product inventory.</p><p>In contrast, the new Sailthru mailing system has two big advantages:</p><ol><li>Marketers have more flexibility to make changes without incurring any re-generation delays</li><li>End customers get their highly personalized messages in their inboxes much faster, lifting engagement metrics like click-through and purchases</li></ol><p>The same guiding principles we used to re-architect the mailing system have now also been used to speed up a nightly aggregation subsystem by 10x. Moving forward, the team plans to apply the same 3 principles to other subsystems which are most in need of performance and scalability boosts.</p><blockquote>Rob Williams is a Senior SRE Engineer at Sailthru. His main responsibilities include making performance/reliability improvements to existing legacy code, implementing new high performance distributed subsystems that replace old ones in order to enable greater system scalability, responding to incidents while on-duty, and investigating root causes of any production problems across the full stack.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd802e63fb00" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/evolving-personalized-email-at-sailthru-fd802e63fb00">3 Principles for Re-Architecting Subsystems for Reliability and Growth</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Sailthru Engineering Sets and Navigates Its Culture]]></title>
            <link>https://medium.com/code-carrier/how-sailthru-engineering-sets-and-navigates-its-culture-b7442cd88557?source=rss----ed839bb7ce09---4</link>
            <guid isPermaLink="false">https://medium.com/p/b7442cd88557</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Johnson]]></dc:creator>
            <pubDate>Wed, 14 Oct 2015 19:52:00 GMT</pubDate>
            <atom:updated>2015-12-04T20:45:13.815Z</atom:updated>
            <content:encoded><![CDATA[<h4>This is our 7–word mantra: Think Big. Speak Up. Get It Done.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K83kI0BUd7fKpJnOnVGoJA.jpeg" /><figcaption>Photo by U.S. Pacific Fleet — Flickr</figcaption></figure><blockquote>Hello, I’m Johnson, the ScrumMaster at Sailthru. If the engineers were a motley crew of shipmates, I’d be their navigator: charting the course to becoming truly Agile, iterating on processes, and helping everyone work together better and smarter. Another part of my job is nurturing the culture of our teams — how we approach our work, how we treat each other, and what we expect of ourselves. We follow a 7-word mantra to navigate the seas of change when it comes to our people, product, culture, and code.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*lUFCuhJZFBQB4AnbObdsLA.png" /></figure><p>Our days are filled with building the best marketing automation and personalization technology to help our customers create unique experiences for each of their users. At the same time, we’re vigilant about staying curious and aware of the broader context of everything we do, so we don’t lose sight of the forest through the trees.</p><p>Think Big means establishing metrics, analyzing the data, and then building out our technology and platform to scale reliably and efficiently with massive traffic and demand.</p><blockquote>By the numbers, we have about 1.5 billion data-rich user profiles and billions more real-time events per month. We send over 6 billion emails every month for our 400+ customers.</blockquote><p>Out of all this rich data, we realized that we could help our customers by making the analytics “smart” and actionable. Our big idea was to use the data to create predictions. We recently launched <a href="http://www.sailthru.com/solutions/">Sightlines</a>, a first-of-its-kind algorithm that helps marketers predict the likelihood their customers will take specific actions, i.e. opting out in the next 7 days, purchasing at a set price point within the next 30 days, etc. To create these predictions, we built dozens of models across vastly differing datasets and business models. This generated over 1 billion predictions a day. With these predictions in hand, our customers are able to automatically create unique experiences for each of their users based on their past actions, and helping to nudge them toward future actions. This leads to increased pageviews and overall lifetime value of each user, which increases revenue for our customers.</p><p>In a later <a href="https://medium.com/code-carrier/evolving-personalized-email-at-sailthru-fd802e63fb00#.rvaj5n4hz">blog post</a>, we’ll highlight the work of our SRE team to re-architect our entire personalization and delivery platform — creating a “stateless” system — that gets used across millions of profiles. We figured out how to personalize and send 7+ billion emails per month, with plenty of room to scale up and support 3x that volume within a short 6 month window.</p><p>Internally, Think Big means we nurture continuous growth and value learning new skills.</p><blockquote>We set aside $1,500 annually, for every employee, starting from the day you join. This is what we call the Personal Growth Program.</blockquote><p>This money isn’t taken out of your paycheck. This is money deliberately set aside for encouraging and helping you learn new skills. So whether you want to take cooking classes, get certified for your private pilot’s license, or brush up on your salsa-dancing moves — we help you get there. We do this to increase the diversity of the skills each one of us has in our toolbox, as you never know when you might learn something new that could unexpectedly help solve some of the interesting and challenging problems we work on, day in and day out.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*Lh-BTOYjM8HxNQY1dU290w.png" /></figure><p>Speak up means it’s OK to ask challenging questions about everything: processes, changes, and the rationale behind decisions. We have an open floor plan — no cubicles, no barriers between desks, no corner offices — which lets anyone talk to anyone. It’s also easy (and encouraged) to go shoulder-to-shoulder with our Customer Success teams to understand what they’re hearing from customers regarding what’s working and what’s not working on our platform. That in turn means that we can take that real-time feedback and incorporate that into upcoming sprints. This way, we’re not only iteratively building out new product features, but also being mindful of delivering optimal software and workflows for our customers.</p><blockquote>Communication and the exchange of information becomes fluid and flat, and because you get feedback and answers quickly, you can get your work done faster.</blockquote><p>We’re nerds at heart who love technology, but we also know that nothing is perfect, especially systems or processes. So our starting point is that there will <em>always</em> be faults. But we welcome them. Let’s identify the faults, then step up to the challenge of solving them. And solutions don’t only originate from the top downward; inspiration can strike from anyone, anywhere in the company. Only when people Speak Up and recognize faults, will others become aware of them, and then conversations can start around what can be done to address them.</p><p>Specifically for the engineering team, as part of our Scrum ceremonies, we have end-of-sprint Retrospectives. We deliberately make time to reflect on the sprint we just completed, and ask ourselves:</p><ul><li>What worked?</li><li>What didn’t work?</li><li>How can we improve?</li></ul><p>One improvement we’ve made to the template is to put the <em>“How to Improve”</em> and <em>“What Didn’t Work”</em> sections side-by-side, so that for everything that didn’t work (that we want to stop doing moving forward), we immediately think about a matching action item for how to improve on it. We also @mention someone to become the owner of that action item to see it through and make it happen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ync0luKGWjKJ-n2uVxryzQ.png" /><figcaption>An example of a Sprint Retrospective from a recent sprint.</figcaption></figure><p>In this way, we inspect, adapt, and continuously iterate our processes so that sprint-by-sprint, we work smarter and build faster.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1020/1*lwot2bIB1N5fHa3j-OU7Xw.png" /></figure><p>We’re a results based work environment. We don’t believe in clocking in and out, or face time for its own sake; some of our employees are even fully remote.</p><blockquote>What matters the most is delivering the results you committed to.</blockquote><p>Life can get busy and unpredictable — we get that, our lives are the same — so take care of what you need to take care of. Run those daytime errands, let in the dog walker, and get those pearly whites checked regularly. But be responsible enough so that you still deliver on the things you said you would. Your teammates and other stakeholders in the company are depending on you.</p><p>We take this idea a step further by having unlimited vacation days. The mutual understanding is that when we are here, we are present and engaged. We all work really hard to achieve the goals we set for ourselves and the company, so it’s fair to then take time off to unwind, travel, go on an adventure and learn something new.</p><blockquote>We love hearing about tales of derring do and share in marveling at the world beyond our desks and devices.</blockquote><p>Interpreted another way, we also see Get It Done as an opportunity to go above and beyond our prescribed responsibilities. If there’s something you think you can do to make someone else’s life easier and more successful — both internally for your teammates, but just as importantly, externally for our customers — rally the shipmates and make it happen. Many of us turn these into learning opportunities.</p><p>Here are a few things our engineers proactively took on and got done:</p><ul><li>A new hire saw a chance for increasing productivity and standardizing environments by creating Docker containers for sandbox</li><li>Our SRE team noticed that a customer had a template with thousands of lines of conditional <a href="http://getstarted.sailthru.com/new-for-developers-overview/zephyr-syntax/zephyr-syntax-overview/">Zephyr</a> syntax which caused inefficient execution in our system (think about all those conditionals being evaluated across millions of profiles). So they proactively reached out to the customer and offered examples of more efficient and effective syntax. This helped reduce load on the system while also making it easier for the customer to troubleshoot their own logic</li><li>The QA team realized that they were manually generating a lot of data throughout testing, so they initiated their own team project to create a “data maker”, something that would help them generate all the data they needed automatically, on demand</li></ul><p>Irrespective of title or department, we keep our 7-word mantra top of mind and close to heart. It drives us to cross-pollinate, share knowledge, teach and listen to each other so that we can get things done — allowing us to be more responsive to changes, increasing productivity, and ultimately, stepping outside our comfort zones and boundaries to always learn and grow.</p><blockquote>In the coming posts, we’ll be covering topics like the technical details and engineering challenges behind our core systems, conduct interviews with individual engineers in our “Meet the Sailors” series, and share some of the tools and processes we use to work together smarter and build faster.</blockquote><p>Come join our motley crew of coders, hackers, tinkerers and architects:</p><p><a href="http://www.sailthru.com/engineering/">Careers at Sailthru | Engineering</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7442cd88557" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-carrier/how-sailthru-engineering-sets-and-navigates-its-culture-b7442cd88557">How Sailthru Engineering Sets and Navigates Its Culture</a> was originally published in <a href="https://medium.com/code-carrier">Code Carrier</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>