<?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 Rob Duffy on Medium]]></title>
        <description><![CDATA[Stories by Rob Duffy on Medium]]></description>
        <link>https://medium.com/@duffy_21693?source=rss-11d736b53c62------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*nTEfLTFJgZMzWlDlaRNfsQ.jpeg</url>
            <title>Stories by Rob Duffy on Medium</title>
            <link>https://medium.com/@duffy_21693?source=rss-11d736b53c62------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 19:33:58 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@duffy_21693/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[Giving Back for Thanksgiving: The 200 Turkey Challenge]]></title>
            <link>https://medium.com/ship-on-day-one/giving-back-for-thanksgiving-poultry-based-marketing-1e0c1e9bd174?source=rss-11d736b53c62------2</link>
            <guid isPermaLink="false">https://medium.com/p/1e0c1e9bd174</guid>
            <category><![CDATA[turkey]]></category>
            <category><![CDATA[thanksgiving]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[beta-testing]]></category>
            <dc:creator><![CDATA[Rob Duffy]]></dc:creator>
            <pubDate>Fri, 10 Nov 2017 00:32:49 GMT</pubDate>
            <atom:updated>2017-11-10T20:41:07.861Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sodo is giving turkeys to Seattle’s Union Gospel Mission when developers join our beta.</h4><p><em>Sodo (short for ship on day one) helps developers manage the growing number of tools and services modern applications need. And we’ve launched sodo’s private beta just in time for Thanksgiving.</em></p><p>This Thanksgiving many of us will be fortunate enough to sit down with family and friends at a well stocked dinner table, many will not. Sodo is helping those in need by distributing a turkey for every developer that signs up to our private beta between now and Thanksgiving. You can help by sharing <a href="http://sodo.rocks/turkeys">this landing page</a> on Facebook, Twitter, LinkedIn and email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Q3qgh4QqJVSAfh6zhCn8hw.png" /></figure><h4>200 turkeys</h4><p>Our goal is to deliver 200 turkeys to those in need the most this year. Seattle’s Union Gospel Mission is a great partner as they reach even farther across King County supplying turkeys to partnering nonprofits, food banks and church pantries.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/537/1*O3AVBAz3gAzeJivac63SEQ.png" /></figure><p>This is a win-win-win for us, turkey sales, and Seattle’s Union Gospel Mission. However, we don’t have nearly as much scale as Slack or GitHub (yet) and neither does Seattle’s Union Gospel Mission, or The Turkey Guy. So we need your help.</p><h4>Your help needed</h4><p>To accomplish the 200 turkey goal, we need our network of friends, colleagues and co-workers to help with the promotion — I’m sure many of which have a sense of glee at the thought of saddling us with hundreds of turkeys (challenge accepted).</p><p>You can help us out by sharing <a href="http://sodo.rocks/turkeys">this page</a>, as well as messaging and forwarding it to developers and developer communities you know, preferably with a personal note. And in doing so you’ll be helping feed the most in need this Thanksgiving (and helping us grow, too).</p><p>If you have writer’s block here’s a couple of good social posts for you to use:</p><blockquote>Help Seattle startup sodo give 200 turkeys to those in need this Thanksgiving. <a href="http://sodo.rocks/turkeys.">http://sodo.rocks/turkeys.</a></blockquote><blockquote>Developer tool company, sodo, is giving 200 turkeys to those in need this Thanksgiving, help them achieve their goal. <a href="http://sodo.rocks/turkeys.">http://sodo.rocks/turkeys.</a></blockquote><p>Happy Thanksgiving!<br><em>Team sodo</em></p><h4>Follow <a href="http://sodo.rocks/fb">Ship On Day One on Facebook</a> for the latest High Performing Engineering articles, videos and more.</h4><p><em>Stay up to date with our latest posts as we cover a whole range of topics on how to level-up your engineering team and implement high performance engineering best practices </em><a href="http://sodo.rocks/fb"><em>http://sodo.rocks/fb</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1e0c1e9bd174" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ship-on-day-one/giving-back-for-thanksgiving-poultry-based-marketing-1e0c1e9bd174">Giving Back for Thanksgiving: The 200 Turkey Challenge</a> was originally published in <a href="https://medium.com/ship-on-day-one">Ship On Day One</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Meet sodo— intelligent docs for your development teams]]></title>
            <link>https://medium.com/ship-on-day-one/meet-sodo-intelligent-docs-for-your-development-teams-ddf13b595651?source=rss-11d736b53c62------2</link>
            <guid isPermaLink="false">https://medium.com/p/ddf13b595651</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Rob Duffy]]></dc:creator>
            <pubDate>Sun, 05 Nov 2017 05:12:08 GMT</pubDate>
            <atom:updated>2017-11-10T18:12:23.814Z</atom:updated>
            <content:encoded><![CDATA[<h4>We’re making sense of the swirling mass of services used in modern software applications.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yjgHX1DwoLvkVkRVwwvbRg.png" /></figure><p>Every time I leave and come back to a software project, the number of tools and services it uses has doubled. Static documentation doesn’t stand a chance in keeping up.</p><p>There are wasted cycles spent trying to find information just to start a project. If you switch projects often, you’re bothering teammates to get up to speed and worry you are doing negative work.</p><p>There are painful on-call and stressful emergent issues as you scramble to figure out what tools are being used for monitoring, hosting, logs and deployments. All while cursing at a README file that says TODO: Write Docs.</p><p><strong>That’s why we built SODO.</strong></p><p>SODO replaces the tired old README file with an intelligent tool that finds each tool used and organizes them in a simple UI. It gives your documentation a boost by cataloging the tools the application is using, making them easy locate. Say goodbye to hours of wasted time spent searching for tools.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1UHlbazZqpgNYkZPpLxstw.png" /><figcaption>Organized tools make for a more-efficient, stress-free, work environment.</figcaption></figure><p>The best thing? The cost of a single repository for a whole year is less than a large pizza. <strong>$1/month/repository.</strong></p><p><a href="https://www.shipondayone.com/joinbeta?utm_campaign=beta&amp;utm_source=medium&amp;utm_medium=hello">Get early access to our beta here</a>.</p><h4>Follow <a href="http://sodo.rocks/fb">Ship On Day One on Facebook</a> for the latest high performing engineering articles, videos and more.</h4><p><em>Stay up to date with our latest posts as we cover a whole range of topics on how to level-up your engineering team and implement high performance engineering best practices </em><a href="http://sodo.rocks/fb"><em>http://sodo.rocks/fb</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ddf13b595651" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ship-on-day-one/meet-sodo-intelligent-docs-for-your-development-teams-ddf13b595651">Meet sodo— intelligent docs for your development teams</a> was originally published in <a href="https://medium.com/ship-on-day-one">Ship On Day One</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Rapid On-boarding Is Crucial to the Gig Economy]]></title>
            <link>https://medium.com/ship-on-day-one/why-rapid-on-boarding-is-crucial-to-the-gig-economy-242ae574d0f8?source=rss-11d736b53c62------2</link>
            <guid isPermaLink="false">https://medium.com/p/242ae574d0f8</guid>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[sharing-economy]]></category>
            <category><![CDATA[gig-economy]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Rob Duffy]]></dc:creator>
            <pubDate>Fri, 06 Oct 2017 01:43:25 GMT</pubDate>
            <atom:updated>2017-10-19T17:36:02.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Rapid On-boarding Is Crucial for Temporary Staff</h3><p>When it comes to the gig economy, Uber and Airbnb tend to suck up most of the journalistic oxygen, but in reality, these platforms make up only a fraction of the independent contractor workforce. Instead, analysts say that traditional employment sectors are generating most of the momentum for hiring 1099 workers, and software and technology industries are at the forefront of that wave.</p><p>While developers have embraced the flexibility of an increased reliance on independent contractors, many are struggling to adapt traditional onboarding methods to this new dynamic. Here’s what you need to know about the 1099 revolution and what it means for your engineering workforce management.</p><h3>Software and the Booming Gig Economy</h3><p>Hard statistics for the explosion in 1099 workers are notoriously hard to come by, mostly because the federal government stopped tracking “contingent workers” in 2005 after failing to find good methods for identifying their numbers. Though the Bureau of Labor Statistics plans to restart its contingent worker research this year, it’ll be some time before reliable numbers are gathered.</p><p>In the meantime, a variety of analysts have used tax data and other sources to provide estimates for the gig economy gold rush, and their research consistently confirms that the revolution is well underway. The Freelancers Union estimates that nearly 55 million Americans are currently working as independent contractors, and a study by Intuit predicts that 40 percent of the workforce will consist of freelancers and independent contractors by 2020. Other experts foresee that more than half the workforce will fall into that category by 2030.</p><p>Crucially, tech has consistently been the largest industry hiring freelancers, with computer and IT positions in the top spot and software development usually coming in fifth.</p><p>As a result, you’ve likely grown familiar with rotating through a continuously refreshing roster of temporary workers, but what does this new dynamic mean for onboarding?</p><h3>The Challenges of Never-ending Onboarding</h3><p>The benefits of hiring temporary talent when and where you need it are significant, but an increasingly temporary workforce also makes training seem endless. Indeed, as the freelance industry optimizes and speeds up with aid from a growing number of employer-matching platforms and websites, the length of individual gigs gets shorter and shorter. Under that dynamic, you may feel like more than 50 percent of every new project entails simply onboarding the temporary workers involved with it.</p><p>Spending so much time familiarizing your temporary developers with the work environment means you’re in danger of losing all the productivity gains that you hired them for to begin with, marking a clear need for change. While some of that change requires adjusting your internal policies for training and evaluating software teams, you’ll struggle to match the speed of the gig economy without an update to your onboarding technology.</p><p>One of the biggest challenges for quick-turnaround projects is initiating workers into the systems used to do the actual work. Manual login assignments and credentialing are common culprits, along with an inability to quickly pass on the documentation necessary for engineers to get up to speed.</p><p>Instead of struggling to manually initiate individuals, you’re better served by a platform that can be configured to automatically bring new hires into the fold, smoothing over the most common pain points that lead to on-boarding delays. To get started, learn how <a href="https://www.shipondayone.com/?utm_campaign=beta&amp;utm_source=medium&amp;utm_medium=gigeconomy">SODO onboards engineers</a> and gets them shipping on day one.</p><h4><em>Follow </em><a href="http://sodo.rocks/fb"><em>Ship On Day One on Facebook</em></a><em> for the latest High Performing Engineering articles, videos and more.</em></h4><p><em>Stay up to date with our latest posts as we cover a whole range of topics on how to level-up your engineering team and implement high performance engineering best practices </em><a href="http://sodo.rocks/fb"><em>http://sodo.rocks/fb</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=242ae574d0f8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ship-on-day-one/why-rapid-on-boarding-is-crucial-to-the-gig-economy-242ae574d0f8">Why Rapid On-boarding Is Crucial to the Gig Economy</a> was originally published in <a href="https://medium.com/ship-on-day-one">Ship On Day One</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Communication Tools Are Important for Development Teams]]></title>
            <link>https://medium.com/ship-on-day-one/why-communication-tools-are-important-for-development-teams-6c98155d3ea1?source=rss-11d736b53c62------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c98155d3ea1</guid>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <dc:creator><![CDATA[Rob Duffy]]></dc:creator>
            <pubDate>Fri, 06 Oct 2017 01:43:05 GMT</pubDate>
            <atom:updated>2017-10-18T02:04:40.561Z</atom:updated>
            <content:encoded><![CDATA[<p>Development teams live and die on communication. When everything goes right, engineers get to focus on their work and reach their deadlines without a problem. If team communication isn’t where it needs to be, you end up with issues that range from minor setbacks to project-ending problems. Approximately<a href="https://www.integritysolutions.com/insights/blog/organizations-pay-a-high-price-for-poor-communication-skills"> 86 percent of employees and executives</a> can point to instances where poor quality communication has lead to some type of failure.</p><p><em>Follow Ship On Day One on Facebook, LinkedIn and Twitter for more discussion of high performance engineering, live shows, videos, and articles.</em></p><h3>Symptoms of Communication Problems</h3><p>In your eyes, communication might seem great. When the development teams get together over lunch, they give the impression that they have excellent communication skills in place. Once they’re back with their own teams, these symptoms tell another tale. While not always only attributable to poor communication, asking if there is an underlying issue is a good first step.</p><ol><li><strong>Missed deadlines and long lasting blockers</strong>: Development projects go off-track for many reasons, but poor communication often has a hand in this situation. Engineers get stuck sitting around and waiting for answers or for another person to finish their part of the work. Poor communication visibility makes it difficult for the team to know which issues are holding up development and what they need to do to get back on track.</li><li><strong>Long resolution times for emergent issues</strong>: The team may not know who they should contact for answers or to resolve project roadblocks. If they don’t know the right people to contact, the engineers end up spending their valuable time playing phone tag. Depending on staff availability, this could tie them up for hours or days as they bounce around from person to person.</li><li><strong>Cultural Difficulty Between Teams</strong>: When the development team interacts with other teams in your organization, do they share a similar communication culture? Some teams encourage reaching out and proactively messaging other employees whenever they need to ask questions or spread relevant information around. Other teams may have a culture where they try to resolve issues themselves before they bring it to another person or team. This happens even if the issue can’t be resolved without the help of someone else.</li></ol><h3>Types of Development Team Communication Tools</h3><p>You can address many development team communication problems with the right tools. While you ultimately need a way to build strong communication within the company culture itself, using solutions that work for your needs and empower team members provides the necessary foundation.</p><p>The expectations of development teams may be different than other teams in your organization. Engineers work best in a state that they call “the flow,” which means that they encounter few distractions that take them away from their work and low-latency communication. The communication tools you choose should support this environment for the team.</p><h3>Email</h3><p>Email gets a bad rap at times, since critical messages and documents like to get lost in the depths of someone’s inbox when they’re on vacation or have left the company. However, it often makes the most sense when you know that the person won’t receive the message for a few hours, whether they’re in another time zone or are simply trapped in a never-ending meeting. Emails also work well if you need an answer to a complex question, as you can save the response for future reference.</p><h3>Slack, Hipchat and Other Instant Messengers</h3><p>These communication tools provide the visibility that’s critical for distributed teams. When you have engineers and other staff halfway around the world from each other, it’s difficult to just visit someone’s office to ask a quick question.</p><p>Slack and similar tools offer a chat room for the entire team. Members can stay on top of communication and quickly answer anything that comes up during the workday. You don’t need to have a remote team to take advantage of instant messenger solutions. An engineer might not want to leave their desk for fear of interrupting the flow. They won’t need to when everyone on the team is sitting in a shared chat room and low-latency communication is available.</p><h3>Video Conferencing and Google Hangouts</h3><p>Sometimes verbal communication is key for the team as they work their way through the development process. While they have the option of picking up the phone, a better option is video conferencing.</p><p>You can promote an in-office style culture among remote teams by setting up a persistent Google Hangouts video call or with frequent web conferencing. Everyone can talk as though they were sitting across from one another at a meeting table, facilitating important discussions.</p><h3>On-Call Directory</h3><p>You can avoid many communication disasters simply by making it clear who needs to be contacted and when. If a critical system goes down and the first thing you hear about it comes from an end user, your first instinct might be to panic and call someone in a leadership position.</p><p>However, once the VP of Engineering gets alerted, they simply go and reach out to the person capable of fixing the problem. A lot of time and frustration gets saved when you have clarity in the chain of command in these types of situations.</p><h3>Pager Duty</h3><p>Pager Duty is a solution that automates the on-call workflow for you. You can create on-call schedules for your teams and develop workflows to account for common issues. For example, if an outage occurs and your development team reaches out to the on-call technician, Pager Duty will call and text that person until they get a response. The application automatically escalates to the next person in line if the first technician fails to answer.</p><p>Are you worried that your development team has communication problems? Download our checklists to find out whether you would benefit from implementing new tools to facilitate team collaboration.</p><h4>Follow <a href="http://sodo.rocks/fb">Ship On Day One on Facebook</a> for the latest High Performing Engineering articles, videos and more.</h4><p><em>Stay up to date with our latest posts as we cover a whole range of topics on how to level-up your engineering team and implement high performance engineering best practices </em><a href="http://sodo.rocks/fb"><em>http://sodo.rocks/fb</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c98155d3ea1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ship-on-day-one/why-communication-tools-are-important-for-development-teams-6c98155d3ea1">Why Communication Tools Are Important for Development Teams</a> was originally published in <a href="https://medium.com/ship-on-day-one">Ship On Day One</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>