<?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 Cylinder on Medium]]></title>
        <description><![CDATA[Stories by Cylinder on Medium]]></description>
        <link>https://medium.com/@cylinderdigital?source=rss-763a6c4d4baf------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1-baK_dDit8Oss8PTh4qOA.png</url>
            <title>Stories by Cylinder on Medium</title>
            <link>https://medium.com/@cylinderdigital?source=rss-763a6c4d4baf------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 11:19:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@cylinderdigital/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[Using Vanity URLs for Stability and Easier Sharing]]></title>
            <link>https://medium.com/cylinder-blog/using-vanity-urls-for-stability-and-easier-sharing-aa30079eaaf2?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa30079eaaf2</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[scheduling-software]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Mon, 04 Jun 2018 23:09:01 GMT</pubDate>
            <atom:updated>2018-06-04T23:14:01.071Z</atom:updated>
            <content:encoded><![CDATA[<p>In developing business, most of my time is spent scheduling and attending meetings. The scheduling part can get time-consuming, so I’m always on the lookout for software tools to make this easier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eUtFBxExZCeaWgpa" /><figcaption>The Centre Pompidou in Paris. Photo by <a href="https://unsplash.com/@curtismacnewton?utm_source=medium&amp;utm_medium=referral">Curtis MacNewton</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>After much experimentation, I’ve landed on <a href="http://calendly.com/">Calendly</a>, which I’ve been using for the 12 months or so. The service creates a URL which you can share with prospective meeting attendees. It looks like this: <a href="https://calendly.com/cylinder"><strong>https://calendly.com/cylinder</strong></a></p><p>The link goes to a page which offers a few different meeting types. For me, these are geographically distinct, meaning “meet in “Oakland”, “meet in San Francisco”, or “Have some sort of not-in-person meeting”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/372/1*xYbRL8LwCeEp4yLaaPhHuA.png" /><figcaption><a href="https://calendly.com/cylinder">https://calendly.com/cylinder</a></figcaption></figure><p><em>Pretty cool, right? </em>It doesn’t matter what happens afterward other than it makes my availability super easy to discover and when you book a time, it creates a calendar invitation.</p><h3>Phase 1: Use the URL</h3><p>So I’m off to the races and giving this URL to people, and I start noticing something. People can’t spell “Calendly” if I tell them the URL using my voice. If I send a link by email or text, it’s easy enough to click on correctly, but I got a lot of questions about this service and what it was doing. I wanted the recipient to focus on our meeting, now how we were getting there.</p><p>I decided to create a forwarding URL, mostly for vanity purposes and kind of to see if it would work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*AfKvFTWuPAeOAC-x" /><figcaption>Photo by <a href="https://unsplash.com/@jamie452?utm_source=medium&amp;utm_medium=referral">Jamie Street</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Phase 2: Add a vanity redirect</h3><p>I wanted the URL to be related to my company marketing site, cylinder.digital. I also wanted it to be welcoming, so I decided on <a href="http://cylinder.digital/hello">cylinder.digital/hello</a>. Friendly, right?</p><p>I wanted to redirect to my Calendly page, so I used the power of HTML to do so. The code looks like this:</p><pre>&lt;head&gt;<br>  &lt;meta http-equiv=&quot;refresh&quot; content=&quot;0; URL=&#39;<a href="https://calendly.com/cylinder&#39;">https://calendly.com/cylinder&#39;</a>&quot; /&gt;<br>&lt;/head&gt;</pre><p>Now I have a simpler and more presentable URL for sharing.</p><p>It had this other side benefit, as pointed out to me by the very smart <a href="https://codeandsupply.co/">Justin Reese</a>:</p><blockquote>It’s Future-Proof.</blockquote><p>That sounds fancy, but it just means “if I change calendar scheduling tools in the future, all the URLs I handed out are always going to be valid.” Maybe it is fancy!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xDgLmPZ6WQDcXExK" /><figcaption>Photo by <a href="https://unsplash.com/@rawpixel?utm_source=medium&amp;utm_medium=referral">rawpixel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Phase 3: Stop Typing So Much</h3><p>Now that I have this neat-o URL, I’m sharing it with everyone to network like a boss.</p><p>Except I’m typing the exact same text <em>around the url</em> every time. What a waste! Also, hands only have so much mileage on them for typing before real damage kicks in. More also: as a <a href="https://www.vim.org/">Vim</a> user, it’s hard for me to abide by too much typing.</p><p>I decided to use a text expander to type out the text I seem to be writing over and over every day:</p><blockquote>My calendar scheduling tool is here: <a href="http://cylinder.digital/hello">https://cylinder.digital/hello</a> — or you can send me some times which work for you, either way is good for me.</blockquote><blockquote>Looking forward to speaking with you!</blockquote><blockquote>Best,<br>Adarsh</blockquote><p>(Note: I used the expander to type the above.)</p><p>If you are on MacOS, you have some great options like the original <a href="https://textexpander.com/">TextExpander</a> or <a href="https://www.trankynam.com/atext/">aText</a> (I used this for a while), or like me and you’re already using Alfred, <a href="https://www.alfredapp.com/help/features/snippets/">try their snippets feature</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*9LnfdjRbM773XNFlEj4Skw.gif" /></figure><p>If you would actually like to schedule some time to speak with us about your digital transformation, getting help with your software design and development efforts, or just to talk about productivity hacks, use, uh, <a href="https://cylinder.digital/hello">https://cylinder.digital/hello</a> or email us at <a href="/service/mailto:hello@cylinder.work">hello@cylinder.work</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa30079eaaf2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/using-vanity-urls-for-stability-and-easier-sharing-aa30079eaaf2">Using Vanity URLs for Stability and Easier Sharing</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Job Posting 2.0 — Recruit More Effectively By Describing A Typical Day at Work]]></title>
            <link>https://medium.com/cylinder-blog/job-posting-2-0-recruit-more-effectively-by-telling-candidates-what-a-typical-day-is-like-601835e7b90d?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/601835e7b90d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 22:38:43 GMT</pubDate>
            <atom:updated>2018-06-12T16:15:07.064Z</atom:updated>
            <content:encoded><![CDATA[<p>It’s hard to hire amazing colleagues. It’s especially difficult to find great engineers and designers. As we wrote before, <a href="https://medium.com/cylinder-blog/you-can-either-steal-great-developers-or-farm-them-cac86a761be9">you can either steal great developers, or you can farm them</a>.</p><p>The combination of technical experience, quality communication skills, empathy, problem-solving, interest in mentoring/teaching, offbeat perspective, and professionalism is tough to locate already. It’s even worse trying to find the right<em> mix </em>of those skills (and others) which augment your team best.</p><p>As an experiment, we have rewritten an engineering job description in the format of “A Day in the Life”. I’m curious to hear what you think of the result<em>.</em></p><h3>Hypothesis</h3><p>Tech job descriptions can be really bad at describing the true nature of the work they expect a new hire to do. Instead of a laundry list of technologies, management buzzwords, and the professional attributes of the world’s greatest employee, a job description could explain the meetings and rituals you’ll attend and just how they expect your 40 hours a week to be spent.</p><blockquote>We can do a better job attracting great candidates by more clearly describing what the day-to-day is like at the job.</blockquote><p>In a tight labor market, candidates are shopping for employers as much as the reverse. Describing the actual job in more detail can help attract the right people to your team.</p><p><em>(Note: For this experiment, I rewrote an engineering job description for our partners, </em><a href="http://codeforamerica.org/"><em>Code for America</em></a><em>. You can read more about our work with them </em><a href="https://medium.com/cylinder-blog/dignity-by-design-bringing-humanity-into-product-design-d7455e56a559"><em>here</em></a><em>.)</em></p><p><em>(Another note: This description is long and detailed intentionally. It’s designed to give a clear picture of what it’s like to work at this job. Please comment and let us know which parts are most valuable to you.)</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sq4BPbDRKRv_-R5RM7yFKQ.jpeg" /><figcaption>Linotype operators of the Chicago Defender. Photo by Russell Lee 1941. Source: <a href="https://en.wikipedia.org/wiki/The_Chicago_Defender">Wikipedia</a></figcaption></figure><h3>A Day in the Life of an Engineer on Our Team</h3><h4>Hello!</h4><p>I’m [NAME], one of the engineers working on the <a href="http://getcalfresh.org/">GetCalFresh</a> team. I’m going to tell you a little bit about what my day is like and hopefully you’ll find it so exciting, you’ll run out and apply for an engineering job with us!</p><p>(Note: You can apply at <a href="https://www.codeforamerica.org/jobs">this link</a>. I’ll also put the link at the end.)</p><h4>What am I working on?</h4><p>I am an engineer on the <a href="http://getcalfresh.org/">GetCalFresh</a> team. We use the startup-style tactics to optimize user signups and get more Californians enrolled in the food stamp program, <a href="http://www.calfresh.ca.gov/">CalFresh</a>. You can read more about it <a href="https://www.codeforamerica.org/services/getcalfresh">here on our project webpage</a> or in <a href="https://www.nytimes.com/interactive/2016/11/13/magazine/design-issue-code-for-america.html">this impressive New York Times article</a>.</p><h3>Start the Day</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HoGxQQqEszJpi8ptV3UneA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/cQCqoTjr0B4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Margarida CSilva</a> on <a href="https://unsplash.com/@marg_cs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I take the train/bus/walk to Code for America headquarters in downtown San Francisco. It’s a lively workplace filled with amazing people working hard every day to make a positive difference in the lives of real Americans.</p><p>I get into the office at about 9:30am and make some coffee. Mornings usually start for me by catching up on emails and having a quick look at any outstanding pull requests (PRs) in GitHub in preparation for…</p><h4>Morning Rituals</h4><p>Every morning at 10am the whole team spends an hour together doing something we call “Morning Rituals”. It’s a time to get together and plan our days using two structured discussions.</p><h4>1. Standup</h4><p>Like many modern software engineering teams, we have a round-robin standup discussion to start the day. We take turns sharing what we worked on yesterday and plan for today.</p><p>This is a great time to ask for help or to coordinate with another engineer to <a href="https://en.wikipedia.org/wiki/Pair_programming">pair-program</a>. It’s also helpful for hearing about teammates doing not-coding things like “I’m shadowing a partner meeting today to understand how the California Counties work with one another” or “I’m listening in on a client customer success call to learn how to better move users through our signup flow.”</p><h4>2. The Daily Diff</h4><p>This is a ritual unique to our team (as far as I know!). After Standup, we review the code which was merged into the master branch over the last day. We value knowing a lot of context information around our work and this really helps us maintain that. Doing a code review doesn’t always suffice for more involved conversations, so this is a great time to chat.</p><p>In this discussion, we also cover changes to the product, debate coding conventions, and occasionally some minor process improvement. If any bugs or emergencies pop up, we’ll discuss how to handle them here as well.</p><h4>Morning Coding</h4><p>From 11am to lunch, I usually review my teammate’s pull requests, merge my own, deal with any ops issues, and set up my afternoon’s work.</p><h4>Lunch</h4><p>Some of us will grab some food from the nearby Ethiopian restaurant, bring it back to the office and eat in the kitchen. Yum!</p><p>Sometimes on Wednesdays, we have lunch speakers who are usually badasses from the world of technology or government. These talks are super interesting and provide a good opportunity for us to learn from leaders in the two worlds we straddle.</p><h3>A Typical Feature</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Muv9p0GUdbCiDi2O1R0wCQ.png" /><figcaption>Photo by <a href="https://unsplash.com/photos/vYrcgxKUyw4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mounzer Awad</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h4>Design Discussion</h4><p>After lunch, we have a meeting with my amazing designer teammate. We do an hour-long sit-down with her where they present the new feature and we engineers ask questions. The next day they refine the flow in mockups (usually in <a href="https://www.sketchapp.com/">Sketch</a> app) and post screenshots into GitHub Issues for us. For the most part, static mockups are great for us although sometimes we use <a href="https://www.invisionapp.com/">InVision</a> when demo-ing for people outside the team.</p><h4>The Idea</h4><p>To take one specific feature as an example, we built something we called “Desktop-to-Mobile Handoff”. When someone is filling out a SNAP application on their desktop computer, they need to upload pictures of documents. This is tough to do on a desktop because most photos are taken on mobile devices.</p><p>We hypothesized it would be easier if clients could put a phone number into our app while using a desktop computer, get a text message with a link which would transfer the state of the SNAP application onto the mobile browser in order to upload document photos from your phone.</p><p>We tested this idea with some of our customers and they loved it, so we wanted to build the quickest version of this feature to see how much it helped our clients.</p><p>Because we are engineers, we talk through all of the edge cases where this feature could break: What if the text message fails to send? How do we resend? Is it the same link or a new one? What if the link is expired (we do this for security purposes)? What is the error message we show them? Our designer patiently works through these scenarios with us and then we have a more complete picture of how to build the feature.</p><p>Our fearless Project Manager then turns this feature picture into more detailed user stories and she queues them up for us in <a href="https://waffle.io/">Waffle</a>, an <a href="https://en.wikipedia.org/wiki/Kanban_(development)">Kanban</a>-type interface for GitHub Issues.</p><h4>Afternoon Coding</h4><p>After this meeting, I’ll write code on my own or with one of my colleagues until about 4pm.</p><h4>Development Flow</h4><p>We pick off the top card on the prioritized list in Waffle and get to work! Typically, two people pair on the feature, writing tests first and then making them pass. For example, I might guide my pair by saying something out loud like “Okay, now I am going to write the controller create action so that when it posts some stuff it gets saved to the model.” I write the test in RSpec and then pass control off to my pair so they can make the new failing test pass. Yay! Green test!</p><p>Once we’ve completed our work, we make a <a href="https://git-scm.com/">git</a> commit for the feature, open a Pull Request so our teammates can help us with Code Review. Often when we pair, we consider that a review so we will merge without a third person’s input. While the PR is open, we demo the results with the designer, or ask her to pull the code down and run it. We talk through it with her and see if it’s close to what she had in mind.</p><p>Because the stories were so well developed, we can merge with minor revisions into master and get ready to deploy our changes to the production server. We typically deploy 4–5 times a week.</p><h3>Tech Stack</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KOwj7MMEgc1V_9t6EQP2ag.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/Koxa-GX_5zs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ash Edmonds</a> on <a href="https://unsplash.com/search/photos/ruby-code?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>It’s probably worth taking a minute to describe some of the tools we use:</p><ul><li>Ruby on Rails (version 5.0)</li><li>PostgreSQL (version 9.4)</li><li>RSpec (test coverage 91%)</li><li>Selenium</li><li>Bourbon / Neat (SCSS grid framework and style libraries)</li><li>No Javascript! (as of now)</li><li>We deploy the app onto <a href="https://aws.amazon.com/govcloud-us/">GovCloud</a>, which is a separate part of AWS which is more secure and better designed for government work.</li></ul><p>You may notice the conspicuous absence of The New Hottness, technology-wise. This is very intentionally a boring list of well-worn technologies which help reduce uncertainty, risk, and reducing learning curves for new colleagues. Also, Rails is already really powerful for our purposes and sticking to the conventions allows us to cast a wide hiring net (I’m talking about you, reader!). Finally, by reducing the amount of JavaScript we use, we make the web application better for a broader population of customers who have a wide variety of mobile devices.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8c333d_YNEHG4q3UDb1wTA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5fNmWej4tAA?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Helloquence</a> on <a href="https://unsplash.com/?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>The Daily Drive</h3><p>This is my favorite part of the day — submitting SNAP applications to the various California counties.</p><p>We must submit SNAP applications to the county by 5pm for them to be valid for the day, so we all typically pause development at 4pm to start automated submission using Selenium. We call this process “The Daily Drive”.</p><p>As a design principle, we want to be very permissive regarding the information submitted to us. We do this in order to learn how clients view their situation as opposed to imposing a strict expectation from our side on what information should look like. This principle manifests itself in the form of loose validations in models and forms.</p><p>Of course, all decisions have tradeoffs and in this case, being more permissive means we have issues around address parsing and integrating with different counties’ sites, who may vary slightly. The Daily Drive is the dedicated time for us to run background jobs to submit the SNAP applications and then dig into issues when they fail for some reason. This is super useful because you learn so much about how your Rails application really works for your users. It’s also nice to have dedicated time for investigating operational issues.</p><p>This is a time for us to note failure patterns and figure out what needs fixing, then create tickets to address them. Most of these things have to do with validation of mailing addresses. For example, military base addresses don’t have street names, which can be confusing if you’ve not served in the military.</p><p>By the way, this is the most gratifying part of the day and the whole reason everyone comes to work each day. From 5pm onward, I spend some time doing cleanup, code review, email, wrap up, and get set up for the next day. I head home at 6pm on the train to watch British comedies and engage in Civil War cosplay with my 6 corgi dogs <em>(Editors note: adapt quirks for your specific situation</em>.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*T_HGYbKxtFVVM3dNHjmrmQ.jpeg" /><figcaption>Photo by <a href="https://www.flickr.com/photos/jgalleg4/">Joseph Gallegos</a></figcaption></figure><h3>The Longer View</h3><p>Of course, some things don’t happen every day so it’s probably good to describe what one of our iterations looks like:</p><p>We refer to our 2-week-long development phases as “iterations”. We don’t call them “sprints” because we feel the term has negative implications about how fast we should be going when developing software. We focus on continuous improvement and creating a sustainable development pace in order to keep our team happy and healthy.</p><h4>Planning Meeting</h4><p>On the Monday at the beginning of the Iteration, we have a planning meeting to track our progress against our goals and plan work for the rest of the iteration.</p><p>Each quarter, we develop a set of goals and ways to measure progress in the form of <a href="https://en.wikipedia.org/wiki/OKR">OKRs (Objectives and Key Results)</a>. Typically, they’re 3–4 big themes we are working toward.</p><p>With this context, we ask ourselves: What are the big project priorities for the next 2 weeks? This is not just an engineering question — it’s about the product and all parts of our team (including partnerships and client success) are included to create the most complete context.</p><p>Once we have a picture of our priorities, we then work to describe what accomplishing those priorities will look like during the iteration.</p><h4>Iteration Review</h4><p>At the end of the iteration on a Friday, we take a moment to look back and see how we’ve done as well as what we could do to improve.</p><p>We gather the whole team and allocate 1.5 hours for the meeting. We remind ourselves of what we set out to do for this iteration and ask if we accomplished our goals. We might ask quickly “why” but we then get deeper into that in the next activity.</p><h4>Retrospective</h4><p>We use a live online tool to create three lists, each with an emoji as a title: Happy Face, Meh Face, and Poop Emoji. We all shout out ideas and thoughts as they come up, and we categorize them based on the emojis. Some items get greater emphasis from the group and we “star” them to discuss in greater depth once the “popcorn” period is over.</p><p>This meeting is very important to the healthy functioning of our group, and as such, is the only non-optional meeting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uoqPobQ-vz2zE65CyHlOJQ.jpeg" /><figcaption>Photo by <a href="https://www.pexels.com/photo/man-sitting-on-edge-facing-sunset-915972/">Abhiram Prakash</a></figcaption></figure><h3>Wrapping Up</h3><p>Again, if this sounds like a day you might enjoy, you can apply to work with us or get in touch with us by email. Thanks!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=601835e7b90d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/job-posting-2-0-recruit-more-effectively-by-telling-candidates-what-a-typical-day-is-like-601835e7b90d">Job Posting 2.0 — Recruit More Effectively By Describing A Typical Day at Work</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dignity by Design: Bringing Humanity into Product Design]]></title>
            <link>https://medium.com/cylinder-blog/dignity-by-design-bringing-humanity-into-product-design-d7455e56a559?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7455e56a559</guid>
            <category><![CDATA[humanity]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[civictech]]></category>
            <category><![CDATA[interaction-design]]></category>
            <category><![CDATA[forms-design]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Tue, 13 Mar 2018 20:01:00 GMT</pubDate>
            <atom:updated>2018-03-21T23:00:41.655Z</atom:updated>
            <content:encoded><![CDATA[<p>Recently, we partnered with <a href="http://codeforamerica.org/">Code for America</a> to help simplify the process for people to sign up for government food assistance, also known as <a href="https://www.fns.usda.gov/snap/supplemental-nutrition-assistance-program-snap">“food stamps” or SNAP (Supplemental Nutritional Assistance Program)</a>. It’s part of Code for America’s <a href="https://www.codeforamerica.org/services/integrated-benefits">Integrated Benefits projects — an effort to create single portals for all government assistance</a>.</p><p>It was one of the best projects we’ve worked on and we wanted to tell you about how we improved the project’s outcomes by focusing on dignity in the product design process.</p><h3>Background</h3><p>Code for America partnered with the amazing Detroit-based design firm <a href="http://civilla.com/">Civilla</a> to make the signup process easier using modern technology. For our part, <a href="http://cylinder.digital/">Cylinder Digital</a> worked together with Civilla on the product design and built the web application which signed our first applicants up for SNAP. You can see the results of our work <a href="https://demo.michiganbenefits.org/">here on our demo site</a>.</p><p>The typical application process for SNAP assistance is lengthy. Folks have to fill out a very long form on paper or using an online service. The paper application — called “DHS-1171” in Michigan (<a href="http://www.michigan.gov/documents/dhs/DHS_Information_Booklet_and_Assistance_Application_242170_7.pdf">PDF</a>) — is FORTY TWO pages long and looks like this taped end-to-end:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*8pgZwwoj_TfGcRENojH79w.png" /><figcaption>Form 1171 (Bridge photo by <a href="http://www.bridgemi.com/about/joel-kurth">Joel Kurth</a> from <a href="http://www.bridgemi.com/public-sector/michigan-tames-18409-word-testament-bureaucracy-run-amok">this post</a>.)</figcaption></figure><p>The online application is called <a href="https://www.mibridges.michigan.gov/access/">MI Bridges</a> and looks a lot like the paper version.</p><h3>Customer Context</h3><p>In designing a web application, our first step was to understand the applicants and where they are coming from.</p><p>The applicants are in a very vulnerable position. First, they are unable to afford enough food for their families. Second, most applicants visit the Michigan Health &amp; Human Services (HHS) offices to get help completing the web form and assembling the required documentation. Asking others for help in this context can be a humiliating process.</p><p>Our goal was to make signing up for SNAP easier and bring dignity back to our customers.</p><p>The completion rate for the form isn’t great — it was not mobile responsive, it’s very long, and the copy on the form fields ranges from clinical to downright confusing.</p><p>It can also be... invasive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/0*OlrCHBRrlHWjynRd." /><figcaption>“Tell us as much as you can about the conception of your child…”</figcaption></figure><p>There are a lot of questions which go pretty far into personal experiences, in this case current or previous pregnancies. It’s hard to imagine why this is relevant information for getting food support, but those are topics for another project. We were concerned with the completion rate and how questions like this could lower it because they embarrassed the applicant.</p><h3>The Impact on Experience</h3><p>Long web forms are notorious for low completion rates and aggravating the applicants. There are lots of easy wins when improving a long form like <a href="https://bitzesty.com/2017/03/20/web-form-ux-making-long-complex-forms-easier-users/">breaking up long forms to multiple pages (AKA The Wizard), saving work as you go (and allowing people to finish later), and better help text copy</a>.</p><p>These address very understandable behavior: people will find <em>almost any</em> reason to abandon a long multipage webform.</p><h3>Hypothesis</h3><p>We hypothesized that asking sensitive questions in an insensitive way did not feel dignified and likely increased form abandonment. Instead, if we asked questions in a more human way, can help both treat people with dignity and encourage form completion.</p><h3>An Example</h3><p>When signing up for SNAP, an applicant is asked if they have recently been pregnant. While a very personal question, the information is necessary to determine both eligibility and amount of food assistance.</p><p>The paper form looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aCmwgMNwVj9GOsWG0lldlg.png" /></figure><p>On our application, we start by taking demographic information including applicant’s name and sex and follow up by asking about the members of the household (specifically, people with whom you prepare food).</p><h3>Our First Pass</h3><p>Taking direction from the paper form, we asked more-or-less the same question in our application:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DeCV5TJKZOpXFBHlql20Cg.png" /></figure><p>We followed a “yes” response by asking who this situation applied to:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OInZ3y79hRyorb31ZI--Bg.png" /></figure><p>You’ll note that we are asking if the household applicant who self-described as male if they are pregnant. For most men, this is an awkward question, but not the end of the world. It’s worth noting here that while perhaps not common, trans men can also be pregnant and give birth, so maybe this is the correct behavior.</p><h3>Let’s Do Better — Part 1</h3><p>If you choose your own sex to be female, we direct the question <em>to you:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gM7agx7zQF5AKoZeM2qnuA.jpeg" /></figure><p>To us, it felt like a small but important change — a dignified way to ask a personal question.</p><p>Note that we’ve also broken a big question with many parts into several small parts.</p><h3>Let’s Do Better — Part 2</h3><p>If you identify someone is in your household as female, we ask if <em>they</em> have been pregnant recently <em>and address them by name:</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pUopgKlg1r3XBuJtgBBqLg.jpeg" /></figure><p>Doesn’t that seem more human?</p><h3>Conclusions</h3><p>When we treat our customers like humans, we are more likely to have them complete a long multi-part form. This is especially true for fellow citizens in vulnerable situations and when we are asking sensitive questions.</p><p>Part of treating people with dignity is giving people the respect they deserve. Even small things like remembering their name or framing questions so they’re easy to understand respects their time and value.</p><p>We think of web applications as an interface to a “computer” — a database, server, maybe another application. Instead, we should consider web applications as a temporary stand-in for a person. Yes, it’s just a computer, but some human eventually processes the information on the backend, so the app is really an intermediary between two people talking. Software should display all the courtesy and warmth we’d like to see from other people.</p><p>Designing experiences with dignity in mind will garner incredible results for the people using services like SNAP and for organizations which provide them.</p><h3>Gratitude</h3><p>Big thanks to <a href="https://twitter.com/jayroh">Joel Oliveira</a> for noticing this issue during the project and proposing a fix. Thanks to <a href="https://twitter.com/jessieay">Jessie Young</a>, <a href="https://twitter.com/rachelcope">Rachel Cope</a>, and <a href="http://twitter.com/zspencer">Zee Spencer</a> who worked on the project from our side. Thanks also to <a href="https://foredesign.co/">Dan Perrera</a>, <a href="https://twitter.com/ptrikutam">Pavan Trikutam</a>, and <a href="https://www.linkedin.com/in/rudhir-krishtel-6314226/">Rudhir Krishtel</a> for helpful edits and feedback.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7455e56a559" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/dignity-by-design-bringing-humanity-into-product-design-d7455e56a559">Dignity by Design: Bringing Humanity into Product Design</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing The Cylinder Way]]></title>
            <link>https://medium.com/cylinder-blog/introducing-the-cylinder-way-446195db9198?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/446195db9198</guid>
            <category><![CDATA[innovation-management]]></category>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Wed, 07 Feb 2018 23:07:18 GMT</pubDate>
            <atom:updated>2018-02-07T23:08:56.549Z</atom:updated>
            <content:encoded><![CDATA[<p>We published a document outlining how we work with our clients, what that looks like in more detail, and most importantly, why we do any of this in the first place. We call it <a href="http://cylinder.digital/way">The Cylinder Way</a> and we’d like to know what you think of it.</p><p>We shared this document a few months ago and have revised it many times since (we even used <a href="https://semver.org/">SemVer</a> to version the progress). Many thanks are due to all of the wonderful people who provided feedback on drafts.</p><p>Like all projects including software, it’s unfinished and we expect it to continuously evolve as we put more work into the world, gain experience, develop knowledge, and get more feedback. We welcome your thoughts on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Irnqa6Z-LYyouGKJGPqQg.png" /></figure><p><strong>Why Write Something Like This?</strong></p><p>A few reasons:</p><ol><li>We believe there is a better way to design and build software to help businesses grow and work more efficiently. When talking with prospective partners and customers about our philosophy, we find ourselves saying the same things over and over — explaining who we are and how we might work together. This is tedious and not a great use of time. <em>Hypothesis: if we send a document describing what we do, how we do it, and why before an early discussion, we can make better use of everyone’s time by having shorter, more focused conversations.</em></li><li>It helps clarify our own thinking. With each project, we learn more about what works well and what does not when building software to solve business problems. <em>Hypothesis: if we write down what we have learned in one place, we won’t have to relearn the same lessons over and over.</em></li><li>We want to share what we have learned with other organizations like ours. We have succeeded as a business only through cooperating with other consultants, both freelancers and firms. We trade leads, help each other staff projects, and learn how to do a better job from one another. <em>Hypothesis: sharing our best practices can help some of our colleagues and in turn, encourage them to share tips with us.</em></li></ol><h3>What Do You Do Again?</h3><p>We build internal startups for companies of all sizes using Human-Centered Design and continuous iteration to experiment, test, learn, and grow. Those startups help grow new business lines and make existing systems more efficient. It’s actually a lot of fun to do and always feels great to help our clients.</p><p>Please <a href="http://cylinder.digital/way">check out the document</a> and let us know what feedback you have (email us <a href="/service/mailto:hello@cylinder.work">here</a> or tweet <a href="https://twitter.com/cylinderdigital">here</a>).</p><p><a href="http://cylinder.digital/way">cylinder.digital/way</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=446195db9198" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/introducing-the-cylinder-way-446195db9198">Introducing The Cylinder Way</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create a Distributed Work Culture]]></title>
            <link>https://medium.com/cylinder-blog/how-to-create-a-distributed-work-culture-b7ca0d59746a?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7ca0d59746a</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Tue, 14 Nov 2017 21:20:27 GMT</pubDate>
            <atom:updated>2017-12-12T18:58:12.197Z</atom:updated>
            <content:encoded><![CDATA[<p><em>PREAMBLE: Please don’t call it “remote work”. It makes people who work outside of an office into an exception of the in-office norm. Consider saying “distributed work” or “work”. To learn more, see </em><a href="https://medium.com/walmartlabs/we-are-distributed-4c64ec6109f4"><em>this excellent post from Chase Adams at Walmart Labs</em></a><em>.</em></p><p>We at Cylinder help achieve business goals using human-centered design and software, which is super fun. We also have an entirely distributed team, which works well for us.</p><p>Recently, we had a client say something we hear all the time:</p><blockquote>“We ’re having trouble hiring full-time expert developers in San Francisco.”</blockquote><p>One hears this a lot in the Bay Area. It feels impossible to hire expert developers in San Francisco, much less convince them (typically over-30, maybe with families) to move to <a href="http://www.sfgate.com/mommyfiles/article/Many-families-leave-San-Francisco-but-what-about-10887001.php">the major U.S. city with the lowest percentage of children</a>.</p><p>Distributing your team is one way to address this hiring challenge and benefit your team in a number of other ways.</p><p>However, creating a distributed work culture is much more than just “letting people work from home”.</p><blockquote>A distributed work culture is an <strong>intentional</strong> team-wide commitment to a set of communication channels and practices to enable working from different places.</blockquote><h3><strong>Here’s how you would create a distribute work culture and why.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KN0OLuHBZkAtq7iHMnjXmw.jpeg" /><figcaption>From https://morguefile.com/creative/diannehope</figcaption></figure><h3>Why Distribute Your Team?</h3><p>We will discuss the benefits in detail separately, but in short, the main three are</p><ol><li>Happier employees (<a href="https://www.slideshare.net/PGi/state-of-telecommuting-2014-pgi-report/1">better health</a>, <a href="https://medium.freecodecamp.org/the-economics-of-working-remotely-28d4173e16e2">enhanced</a> <a href="https://blog.hubstaff.com/remote-workers-more-productive/">productivity</a>, <a href="https://remote.co/championing-diversity-and-inclusion-remote-work/">increased diversity</a>, <a href="https://people.stanford.edu/nbloom/sites/default/files/wfh.pdf">less employee turnover</a>, encourages autonomy)</li><li><a href="https://medium.freecodecamp.org/the-economics-of-working-remotely-28d4173e16e2">Enhanced</a> <a href="https://blog.hubstaff.com/remote-workers-more-productive/">productivity</a> (more focused use of time, fewer lost work days due to illness)</li><li>Lower Costs (<a href="https://stackoverflow.blog/2017/04/14/cant-afford-private-offices/">real estate</a>, <a href="https://people.stanford.edu/nbloom/sites/default/files/wfh.pdf">employee turnover and hiring</a>, <a href="https://www.slideshare.net/PGi/state-of-telecommuting-2014-pgi-report/1">health care from happier/healthier people,</a> cheaper to recruit from a larger pool, lower salary when employees live in a lower-cost area)</li></ol><h3><strong>How to Build a Distributed Culture</strong></h3><p>There are four keys to making any organizational cultural change like shifting the location of where everyone works and how they communicate.</p><h3>1. Tell a Change Story</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HA25J9lhge1FwX-F6oVQJA.jpeg" /><figcaption>source: <a href="https://commons.wikimedia.org/wiki/File:First_Lady_to_Visit_Military_Families_at_Fort_Bragg_DVIDS156997.jpg">Wikimedia</a></figcaption></figure><p>To make a shift successfully in any organization, you need to prepare everyone for what’s about to happen. Most critically, the leadership needs to tell a compelling Change Story. The term sounds fancy but it’s a pretty simple idea:</p><ol><li>Tell a clear story about why your organization is going distributed, how the change will happen (specifically), and when it will be expected to be complete.</li><li>Continuously publicly revisit #1, keeping the story consistent, and report on how it’s going.</li><li>When the change is complete, send a message to everyone saying “the change is complete!” and thank everyone for their patience.</li></ol><p>Why is this important? Any major changes in a workplace create anxiety. Work is how we support ourselves and our families, not to mention how we get health care — imagine someone telling you it will all be different tomorrow! Even a change like opening up to distributed work can cause anxiety. If I work from home, will people think I’m slacking? Am I less likely to get promoted?</p><p>The Change Story helps everyone manage their expectations and reduce anxiety. It does so by holding your hand calmly throughout the whole process and not wavering from the plan.</p><h3>Example Change Story</h3><p>When distributing your team, your story might look like this:</p><p>At the start:</p><blockquote>We will be moving to a distributed work model between now and Thanksgiving. You are free to work from wherever you want but it’s important to understand how to do so effectively. Please read our best practices document (Editors note: ours are at the end) and begin a discussion with your team. For in-office folks, it’s just as important to read the document and buy in, maybe more so. We are doing this because we believe this change has positive business benefits, including happier employees, increased diversity, lower costs, and improved productivity. Get in touch with Alice or Bob if you have questions.</blockquote><p>Later on…</p><blockquote>Hi again! We are halfway through our transition. If you haven’t already started to shift your team or start discussions about what distributed work looks like for you, now is a great time. Remember, we are doing this for happier employees, increased diversity, lowered costs, and better productivity. Also, remember to get in touch with Alice or Bob if you have questions!</blockquote><p>At the end:</p><blockquote>Hello! Well, our transition to a distributed culture is now complete. We will continue to adapt and adjust how our teams live out this goal, but everyone has done a great job! So far X% of people have moved to full-time distributed work and Y% have at least tried it once. We are now experiencing all of the wonderful benefits we thought we would! Yay! Big thanks to Alice and Bob for spearheading this change!</blockquote><p>One tactical note: Everyone should be involved in writing the story, not just leadership. A story written by the people who have to live out the change is far more likely to be successful.</p><h3>2. Role Modeling</h3><p>The second key to cultural change is Role Modeling.</p><p><strong>The leaders of an organization have to actively and publicly demonstrate the new desired cultural change.</strong></p><p>This is key — if the leaders do not fully embrace the change story and live it out in their daily behavior, the cultural change will fail. Everyone else will feel like it’s more work they’ve been assigned by the bosses who don’t have to follow their own rules.</p><p>In our example of spreading distributed culture, the executives and management should work in a distributed fashion, participating in discussions about what works and what doesn’t, and otherwise being positive and encouraging. Seeing the CEO work from home is far more influential than hearing the CEO tell you to work from home.</p><h3>3. Reinforcing Mechanisms</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/491/1*c5cS72gecmtJSNUD3QfoFA.gif" /><figcaption>Source: <a href="https://giphy.com/gifs/satisfying-gears-nautilus-fi2BoljcO2Jiw">Giphy</a></figcaption></figure><p>Once you have a story in place and the leadership are showing everyone how it’s done, it’s important to monitor the progress and reinforce the desired behaviors.</p><p>In the case of moving to a distributed culture, consider tracking some very basic metrics which answer the question: “Hey, how’s that distributed work thing working out for you all?”</p><ul><li>Percent working entirely outside of the office or at least once per week</li><li>1–10 survey of how conducive the culture is to working elsewhere.</li></ul><p>You can then send out short reports on which teams have the best scores and randomly gift them something like a prize or outing. <a href="http://blog.deliveringhappiness.com/the-motivation-trifecta-autonomy-mastery-and-purpose">Studies show financial bonuses are not as effective</a>.</p><p>In the case of creating distributed culture, incentives may not be necessary — the change may be it’s own reward. Saving time on commuting and having more schedule flexibility may be a positive enough change to motivate others to do the same.</p><h3>4. Skill Building</h3><p>Finally, it’s important for all employees to feel supported in making the change with the skills and tools to do it right. Specifically, to encourage distributed culture, leadership should provide training on how to effectively work on distributed teams.</p><p>It’s important to be intentional about a cultural change like this and acknowledge that success more than just allowing some to work from outside HQ. It’s about understanding and implementing best practices, and evolving them for your own organization.</p><p>Working productively outside of an office is a skill which can be improved upon, like any other. If you hire software developers based on how many years they have been writing code, you should also consider how long someone has worked in a distributed team before hiring them into one.</p><p>Let’s take a look at what organizations can to enhance communication across wide spaces.</p><h3>What a Great Distributed Team Looks Like</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7MX4d9FlmZELG2FweJRbsA.jpeg" /></figure><p>It bears repeating — creating a distributed work culture is much more than just “letting people work from home”.</p><p>Here are some best practices you can test out with your team, as you develop your unique way of working:</p><p><strong>Communication</strong></p><ul><li>Hold a short video standup meeting each day. It helps to feel connected and provides a consistent opportunity to talk synchronously at least once a day.</li><li>Avoid hallway chatter — move everything online where possible. More importantly, create a culture where it’s okay to call this out. Some things are best done in person like sketching / white-boarding, which is okay, but try to capture the output and share back via chat..</li><li><a href="https://medium.com/@fox/building-remote-first-teams-a98bf8581db">ASAP is poison</a>. Asking for something to be done immediately is disrespectful of our teammates valuable time. Plan ahead for actually-urgent tasks by laying out a protocol for how to handle fires and set shifts for who is on-call for support.</li><li>Maintain consistent work hours and mute notifications during off hours. Post your working hours in your profile. All of this prevents Slack burnout where you feel the need to be online constantly.</li><li>Post “Good Morning” and “Good Night” messages to clearly indicate when you are online and greet your team.</li><li>Set a maximum time zone difference. Even flexibility has it’s limits, and this is a hard one to overcome. If you can’t regularly have 2–3 hours of workday overlap for the whole team, it’s very difficult to communicate well. This means practically about a 6 hour limit in timezone variance.</li><li>Watch out for snark (“Oh, look who’s loafing off in their sweatpants at home today!”).</li><li><a href="https://medium.com/cylinder-blog/how-to-conserve-your-precious-attention-span-92b869b88e81">Respect the precious attention span or your colleagues</a>.</li></ul><p><strong>Video Conferencing</strong></p><ul><li>Everyone should log in to a video call, even when some people are in the same room. We all need to see close-ups of your beautiful face, not a grainy wide shot of several people.</li><li>Consider not using a conference room for the people in-office to avoid audio issues. Or alternatively, use a room but have everyone wear headphones and turn their microphones on. (hat tip to <a href="https://medium.com/u/a7914a0d1eaa">Ken Miller</a> for this one.)</li><li>Train participants to look into the camera — it creates a deeper connection and conveys the sense you are looking at the other person, rather than off to the side.</li><li>Set expectations at home with your family on when is okay to come in, <a href="https://www.youtube.com/watch?v=Mh4f9AYRCZY">so you don’t get ambushed</a>. Consider a lock on the door.</li><li>Work from a quiet place where everyone can hear you. Coffee shops are okay in a pinch but too noisy for everyday communication.</li><li>Share the video conferencing link well before the scheduled start of the call to allow everyone to log in and set up. One way to do that is to maintain a single video “room” for most meetings.</li><li>If the majority of attendees are in one room, designate someone as the “remote delegate” to represent any AV issues, particularly in very large calls like all-hands meetings.</li><li>If you’ve never met before, budget 5–10 minutes to get the video/audio setup correct in your conference room.</li></ul><p><strong>Investments</strong></p><ul><li>Meetup once every quarter in-person for a few days or a week. This is the biggest investment with the biggest payoff.</li><li>Nicer video camera — Even a<a href="http://amzn.to/2hw9mq6"> $50–75 external webcam</a> is a big upgrade in video quality from the default camera.</li><li>Reimburse workers for network connectivity, ensuring it’s enough to pay for higher-bandwidth.</li><li>Reimburse for better home office gear like standing desks, external monitors, chairs, and standing mats to prevent injury and create a more comfortable space.</li><li>Invest in upgraded video conferencing services like <a href="http://zoom.us/">Zoom</a>.</li><li>Add <a href="http://amzn.to/2icAxDA">sound-dampening foam</a> to the walls.</li></ul><p><strong>Hiring Distributed Teammates</strong></p><ul><li>Aim to hire teammates with distributed experience. Like any skill, it does take time to learn and improve.</li><li><a href="https://medium.com/@fox/a-guide-to-empathetic-hiring-processes-c11c7ce0cd49">Rewrite your job description to create a picture of day-to-day work</a>.</li><li>Evaluate written/oral communication skills carefully in interviews. For that matter, conduct interviews over video conference.</li><li>As an employer, experienced distributed workers will judge you on all of your written communication to get a sense of the writing standards. Continuously edit and improve your job postings, public documentation, blog posts, etc. so they are crystal clear and fun to read.</li><li>When hiring, search outside your normal local networks. <a href="https://medium.com/@fox/building-remote-first-teams-a98bf8581db">Post your jobs on distributed job boards and spread the word about your hip new distributed work culture</a>.</li></ul><p>If you like this work, please consider sharing it with someone else.</p><p>At Cylinder, we believe simple software can get work done faster, leaving more time for life. Using human-centered design, modern software practices, and high-quality communication, we research, design, and build simple web and mobile software for businesses and people. <strong>Email hello@cylinder.work to learn more</strong>.</p><p>And if your organization needs a hand changing to a distributed culture, <a href="/service/mailto:hello@cylinder.work">give us a shout</a>.</p><p><strong>Gratitude</strong></p><ul><li>Thanks to <a href="http://www.cocreationpartners.com/who-we-are/our-people/">Gaurav Bhatnagar</a> for first introducing the Influence Model and teaching me about culture at work.</li><li>Thank you to <a href="https://medium.com/@fox">Karolina Szczur </a>for her great writing on distributed work, inclusion, and communication.</li><li>Thanks to the wonderful team at <a href="http://codeforamerica.org/">Code for America</a>.</li><li>Thanks to the great team at <a href="http://infinite.red/">Infinite Red</a> for first showing me all-distributed consultancies can be successful. <a href="https://shift.infinite.red/taking-the-pain-out-of-video-conferences-7b7abe822b36">Read their post on best practices here</a>.</li><li>Thanks to all of my friends and colleagues for feedback and edits.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GYEbeCSqXztrJSD9OtUipw.png" /><figcaption><a href="https://pxhere.com/en/photo/1211244">https://pxhere.com/en/photo/1211244</a></figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7ca0d59746a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/how-to-create-a-distributed-work-culture-b7ca0d59746a">How to Create a Distributed Work Culture</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Conserve Your Precious Attention Span]]></title>
            <link>https://medium.com/cylinder-blog/how-to-conserve-your-precious-attention-span-92b869b88e81?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/92b869b88e81</guid>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 23:29:03 GMT</pubDate>
            <atom:updated>2017-09-19T18:42:49.007Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*JdJWaMXmOCfsDocyFLddIA.jpeg" /></figure><p>One of our client projects needed help with developer operations and infrastructure. The client had grown large enough to need a dedicated Ops specialist on staff who specialized in knowing how to configure servers and the like. This was good news for us.</p><p>But this person was very busy, being the only ops person in a quickly growing organization, so they agreed to help under one condition:</p><blockquote>“Hey I’m happy to help out and join your team, but I need you to tag my @ mentions as either [action required] or [FYI]. I will respond in a timely fashion to the former and eventually catch up on the latter.”</blockquote><p>Immediately, I realized this person was a genius.</p><p>Unsurprisingly, these days <a href="http://time.com/3858309/attention-spans-goldfish/">we have shorter attention spans than goldfish</a>. Everything we install on our mobile devices (or every Saas product we sign up for) greedily asks us if they can send us pushes, badge icon numbers, emails, SMS, and stop by to ring the doorbell. We experience a constant battle to keep this sort of thing under control.</p><p>Some choose to silence all of it, which is a totally rational response.</p><p>At work, this is harder to do. The ops person I mentioned is “part of” a half-dozen or more teams, each vying for their attention, probably saying something like “this is super urgent please help!” (like I did, shame on me).</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*Lwzzwrpic4_WhQRJa2IwkA.jpeg" /></figure><p>Each team they join (like ours) added them to our Slack/Trello/GitHub accounts and send them an untold number of notifications.</p><p>A request to say “hey, let me know what is _actually_ urgent vs. informational” is the most rational thing we’ve heard in a long time.</p><p>So try this out on your projects and let us know how it works:</p><blockquote>“@ghostscript_killa [FYI] Hey we’re going to up the capacity on this server so you may see the bill go up by about 20%.”</blockquote><p>or</p><blockquote>“@ol_querty_bsd [ACTION] Hey the DNS is misconfigured and no one can use the app!”</blockquote><p><em>You can add us to your team to solve your business problems with software by </em><a href="/service/mailto:hello@cylinder.work"><em>sending us an email</em></a><em> :) We promise to @ mention you only when it’s super duper necessary.</em></p><p><em>Originally published at </em><a href="https://hackernoon.com/how-to-conserve-your-precious-attention-span-7e7161ec48f6"><em>hackernoon.com</em></a><em> on September 13, 2017.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=92b869b88e81" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/how-to-conserve-your-precious-attention-span-92b869b88e81">How to Conserve Your Precious Attention Span</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Conserve Your Precious Attention Span]]></title>
            <link>https://medium.com/hackernoon/how-to-conserve-your-precious-attention-span-7e7161ec48f6?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e7161ec48f6</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[notifications]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Wed, 13 Sep 2017 23:29:03 GMT</pubDate>
            <atom:updated>2017-09-19T13:56:13.061Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JdJWaMXmOCfsDocyFLddIA.jpeg" /></figure><p>One of our client projects needed help with developer operations and infrastructure. The client had grown large enough to need a dedicated Ops specialist on staff who specialized in knowing how to configure servers and the like. This was good news for us.</p><p>But this person was very busy, being the only ops person in a quickly growing organization, so they agreed to help under one condition:</p><blockquote>“Hey I’m happy to help out and join your team, but I need you to tag my @ mentions as either [action required] or [FYI]. I will respond in a timely fashion to the former and eventually catch up on the latter.”</blockquote><p>Immediately, I realized this person was a genius.</p><p>Unsurprisingly, these days <a href="http://time.com/3858309/attention-spans-goldfish/">we have shorter attention spans than goldfish</a>. Everything we install on our mobile devices (or every Saas product we sign up for) greedily asks us if they can send us pushes, badge icon numbers, emails, SMS, and stop by to ring the doorbell. We experience a constant battle to keep this sort of thing under control.</p><p>Some choose to silence all of it, which is a totally rational response.</p><h3>DHH on Twitter</h3><p>This is critical life advice. Phone notifications are in most cases simply a weapon on the battleground of attention. Don&#39;t be a victim. https://t.co/qP1rNOXV0L</p><p>At work, this is harder to do. The ops person I mentioned is “part of” a half-dozen or more teams, each vying for their attention, probably saying something like “this is super urgent please help!” (like I did, shame on me).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Lwzzwrpic4_WhQRJa2IwkA.jpeg" /></figure><p>Each team they join (like ours) added them to our Slack/Trello/GitHub accounts and send them an untold number of notifications.</p><p>A request to say “hey, let me know what is _actually_ urgent vs. informational” is the most rational thing we’ve heard in a long time.</p><p>So try this out on your projects and let us know how it works:</p><blockquote>“@ghostscript_killa [FYI] Hey we’re going to up the capacity on this server so you may see the bill go up by about 20%.”</blockquote><p>or</p><blockquote>“@ol_querty_bsd [ACTION] Hey the DNS is misconfigured and no one can use the app!”</blockquote><p><em>You can add us to your team to solve your business problems with software by </em><a href="/service/mailto:hello@cylinder.work"><em>sending us an email</em></a><em> :) We promise to @ mention you only when it’s super duper necessary.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e7161ec48f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/how-to-conserve-your-precious-attention-span-7e7161ec48f6">How to Conserve Your Precious Attention Span</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Surprise! You’re an Engineering Manager. What now?]]></title>
            <link>https://medium.com/cylinder-blog/surprise-youre-an-engineering-manager-what-now-4c8bf2f79be3?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c8bf2f79be3</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Wed, 26 Apr 2017 21:06:59 GMT</pubDate>
            <atom:updated>2017-09-19T18:38:08.177Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iR5TAArmwaptM-hU82SNiQ.jpeg" /></figure><p>Great software engineers are amazing problem solvers with code and can get a crazy amount done. That’s what they’re paid to do. But if you become very skilled at writing code, you often get promoted. Great news, right? Maybe.</p><p><strong>The worst use of an engineering manager’s time is writing code. Be sure you know that before you accept a promotion.</strong></p><p>The software industry still (mostly) promotes excellent developers into people-management roles because companies rarely develop advancement paths for non-people managers (AKA Individual Contributors or “people who are not managing other people”). So now you’re the boss, are you prepared to not write any more code? Where is the documentation for this new “manager” job anyhow?</p><p><em>How can you, as an excellent developer, succeed as people-managers; a role for which you may have no experience or training?</em></p><p>Moving from a job for which you have tons of experience and expertise (writing code), to one where you have none at all (people management), is like becoming a baby again: you’ve got a whole lifetime of knowledge to learn and you need to do it yesterday.</p><p>It’s a transformative moment in any career to get promoted to a managerial role (it sure was for me). Here’s how you can handle this specific change and come out happy on the other side.</p><h3>Flat Organizations are Replacing Command-and-Control</h3><p>After World War II, veterans flooded into the workforce, at all levels. The following years saw huge growth in companies like IBM, General Motors, General Electric, and Westinghouse. As they grew, the ex-military executives used a command-and-control management structure to quickly grow companies.</p><p>Tech companies are rapidly deconstructing this management philosophy by flattening control structures. Where one manager may have previously had few direct reports, all of whom took directive orders, a manager now may have dozens of reports and employees are expected to be much more independent. This model scales up much more quickly than the command-and-control way, and also provides autonomy — <a href="http://www.halogensoftware.com/blog/3-things-that-motivate-employees-more-than-money">one of the work qualities employees value more than money</a>.</p><p>However, this flatness creates a very tough job for engineering managers: You manage more people, have less room to be directive, and you’re no longer doing the technical work at which you are so amazing. Not to mention you’re doing a lot of touchy-feely things (aka “not writing code”) at which you may not be experienced.</p><p>When we promote people <a href="https://twitter.com/adarshp/status/855138312444497920">diagonally</a> like this, is it any wonder we see so many management issues at technical companies?</p><h3>How can I be a great engineering manager?</h3><p>It’s not prior job experience, because generally speaking, there are few jobs which prepare people to manage others. Coding is a focused, solitary activity, so developers are often less prepared to lead others.</p><p>Here is what makes a great manager:</p><ul><li>High emotional quotient (EQ)</li><li>Excellent communication skills</li><li>An understanding of the job</li></ul><p>The first two are straightforward and I won’t delve into them here. The last <em>should</em> be clearly defined by the organization, but rarely is. Let’s give it a whirl:</p><h3>Understanding the Job of Engineering Manager</h3><p>Your job is to</p><ul><li>Set the broad goals of the team</li><li>Propose a plan to achieve the goals</li><li>Track progress against those goals</li><li>Remove obstacles in the way of those goals</li><li>Create alignment through organizational transparency</li></ul><p>Seems simple? It’s super hard because each of those things shifts all the time. Let’s look at an example.</p><h4>Set the Broad Goals of the Team</h4><p>Let’s say you are a new engineering manager and you’ve been tasked with something like adding a “Teams” feature. Your job as the manager is to clarify what this means and propose a plan to get there.</p><p>The goal of the project is “figure out how our individual users can work together in teams”. Maybe you have 3 months and a team of 4 to get it done. This is your goal and you should probably write it on the wall in huge letters. Everyone needs to know right away if this goal changes, even slightly.</p><h4>Propose a plan to achieve the goals.</h4><p>Breaking this down, it means you can propose some kind of plan like:</p><ol><li>Figure out how people are using the application collaboratively now (probably using hacky workarounds). This is the hardest part — figuring out what “working in teams” means specifically.</li><li>Prototype some ways of making those previously hacky interactions simpler and easier. Do this super cheaply and quickly.</li><li>Test prototypes with customers by showing them what you sketched up and talking to them.</li><li>Build the prototype customers loved most.</li><li>Deploy and get feedback via analytics and talking to customers.</li></ol><p>Part of the plan involves group delegation, or figuring out whose strengths match up with the most important team tasks. As the manager, it’s your job to make it happen, but you need to do so with input from the group.</p><h4>Track progress against those goals</h4><p>How can you track progress? You can try a few ways and likely, your project or workflow may demand a specific way to know how you’re doing. Maybe the simplest first-draft is to write your plan up on the wall in big letters (see a theme?) and put check boxes next to it. Alongside that, you can also post work artifacts on the wall, like pictures of prototypes, photographs of user-testing, or quotes from customers. Maybe it’s in<a href="https://en.wikipedia.org/wiki/Timeline"> right-to-left timeline format</a>?</p><p>I prefer <a href="https://trello.com/">Trello</a>, but other tools (e.g. <a href="https://asana.com/">Asana</a>) do the job just as well. Avoid things like Pivotal Tracker or Jira, as they’re built to grind out big waterfall software projects, not squishy projects which change constantly.</p><h4>Remove obstacles in the way of those goals</h4><p>Now that you’ve got a plan and a way to track progress, step back and do the obstacle-removing. This could means things like:</p><ul><li><strong>Team Design</strong> — hiring, recruitment, interviewing, performance evaluations, terminations</li><li><strong>Better processes</strong> — using your broad view, spot process/flow issues and see if they’re an issue for others. Allow the people <em>in the process</em> to come up with the solutions.</li><li><strong>Engage in internal politics for the good of your team</strong> — Public recognition and kudos for your team, jockeying for more budget, trading favors, etc.</li><li><strong>Check in with employees to see how happy they are</strong> — Helping employees achieve autonomy, mastery of craft, projects with purpose, adjusting compensation, ensuring a safe working environment.</li></ul><p>Some of these are obvious but you should also figure out what other obstacles lie in the way using this patented phrase:</p><p>“What obstacles are in the way of you doing your best work and helping us achieve our team goal?”</p><h4>Create alignment through organizational transparency</h4><p>This is an important activity which isn’t exactly related to the project success but is critical to engage in, nevertheless.</p><p>To describe this in other words, your goal as a manager is twofold:</p><ol><li>Keep your team up to date on the activities, priorities, and temperature of the rest of the organization, particularly leadership.</li><li>Share what your team is doing with people elsewhere in the organization.</li></ol><p>By helping to share of work across the organization, managers can help create alignment across all of the teams. This benefits the broader organization by facilitating knowledge sharing (best practices, useful new tool, etc.) and fostering a sense of cohesiveness. In general, sharing tactical project information like this has the effect of making everyone feel aware of the internal current events, which can help prevent feeling blindsided by organizational changes, not to mention feeling like a valued teammate.</p><h3>What Is Not The Job of Engineering Manager</h3><p>Your job is not to</p><ul><li>Write Code. You have a team for this.</li><li>Review Code. You are not writing code, so you don’t get to have opinions about code.</li></ul><p>I’m a decent coder (I think). At one previous management job, I shared plenty of opinions about code and it was a huge mistake. When I talked too much about how to write code, I noticed communication with me stopped until I backed off of the codebase.</p><p>Why? The team wasn’t 100% sure if they should take my advice as an order or disregard it and work in the way they found most efficient. I’m not alone in my experiences: many other managers and executives I’ve talked to have similar stories about muddying the communication waters.</p><p>This is a hard lesson to learn for many new engineering managers, because again, usually the reason they were promoted is because they’re great at coding, right?</p><h3>What If I Still Want to Code?</h3><p>Since most developers don’t really understand what their managers do, it’s inevitable that some want to be promoted — or already have been promoted — into a job that’s not a good fit.</p><p>This is a good realization to have, at any point.</p><p>You might be better suited for the role of Lead Developer. The Lead is more of a “first among equals” leader, setting tone for the actual technical work. This person gets to lead the architecture discussions, set code standards, lead developer improvement discussions, streamline deploy processes, and serve as the tiebreaker for bikeshedding arguments.</p><p>Lead Developers <strong>absolutely</strong> should be writing code.</p><p>If your organization declines to create a position like this or a parallel advancement path for Individual Contributors, and you really feel you want to follow a dev track, consider moving on. Fortunately, at the present time, there are a lot of other companies who would be happy to hire you.</p><h3>I Took the Manager Job. How Do I Know If I’m Any Good?</h3><p>Besides understanding what the job actually is, this is next the hardest thing about managing. <strong>You are very unlikely to get good or honest feedback as a manager from your team</strong>. It’s just hierarchy and there isn’t much to do about it. Even teammates who are excellent at giving feedback will inherently be averse to speaking up to their “boss”. It’s not their fault.</p><p>Here are some questions which might help you figure out how well you’re doing:</p><ul><li>Are you crazy-productive as a group?</li><li>Are people eager to join your team or asking to be transferred elsewhere?</li><li>If you ask, do the people on your team feel like you’re looking out for them?</li></ul><h3>Conclusion</h3><p>Mostly, engineering managers struggle because of a lack of support from the organization, lack of definition of the role, or just a mismatch in strengths vs. role.</p><p>This doesn’t mean expert developers have no future career path outside of management, it just means you may have to work with your organization to develop a career path for people who don’t want to be future executives.</p><h3>Acknowledgements</h3><p>Thanks to <a href="https://twitter.com/drewdil">Drew Dillon</a> and <a href="https://twitter.com/ornellasmike">Michael Ornellas</a> for the original discussion which inspired this article. Thanks Chris Morrison for help in getting this this article started. Thanks to <a href="https://twitter.com/ptrikutam">Pavan Trikutam</a> and <a href="http://gabebw.com/">Gabe Berke-Williams</a> for editing help.</p><p>Special thanks to anyone who has ever put up with me as a manager.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c8bf2f79be3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/surprise-youre-an-engineering-manager-what-now-4c8bf2f79be3">Surprise! You’re an Engineering Manager. What now?</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[You Can Either Steal Great Developers or Farm Them]]></title>
            <link>https://medium.com/cylinder-blog/you-can-either-steal-great-developers-or-farm-them-cac86a761be9?source=rss-763a6c4d4baf------2</link>
            <guid isPermaLink="false">https://medium.com/p/cac86a761be9</guid>
            <category><![CDATA[apprenticeship]]></category>
            <category><![CDATA[junior-developer]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring-tips]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Cylinder]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 21:26:07 GMT</pubDate>
            <atom:updated>2017-09-19T18:43:23.252Z</atom:updated>
            <content:encoded><![CDATA[<h4><em>To grow software development teams, you can either steal excellent developers or you can develop them internally.</em></h4><p><em>Everyone tries to steal but few invest in farming new developers. Those who do have lower salary and recruiting costs, better learning cultures, and improved diversity.</em></p><p>Here’s why you would set up an Apprenticeship program and how to do so.</p><p>If you want help setting up a program like this, <a href="/service/mailto:hi@cylinder.work?subject=Saw%20Your%20Blog%20Post!%20Can%20you%20Help%20Us%20With%20Our%20Apprenticeship%20Program?">email me</a>!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*tUIaC9ZqD7IKs1QB.png" /></figure><p><em>photo courtesy of WOCinTech (</em><a href="http://www.wocintechchat.com/?utm_source=adarsh.io&amp;utm_medium=blog"><em>wocintechchat.com</em></a><em>)</em></p><h3>Why Steal Them</h3><ul><li>It’s straightforward. You have a need for help, they have skills you probably need.</li><li>You can buy your way out of the problem.</li><li>It is how everyone has hired for as long as anyone can remember.</li><li>Short-term impact. Expert developers can get ramped up quickly and help you ship much faster.</li></ul><h3>Why Farm Them</h3><ul><li>Cost — Creating a developer growth pipeline is much cheaper in the long-term. Apprentices are cheaper than experienced developers and will take a salary hit for the learning opportunity.</li><li>Loyalty — Apprentices are extremely loyal and less likely to turn over. You took a chance on them and they will always remember.</li><li>Diversity — The experienced developer pool is very homogeneous. The junior pool is not. If you can turn juniors into seniors, diversity will improve.</li><li>Vibe — Apprentices add a lot to company culture. Senior devs love to teach and coach, so give them a chance to do so. Also, Apprentices have an energy and optimism the old folks may have lost over the years.</li></ul><h3>Personal Backstory</h3><p>Back in 2012, as I tried to break into the software industry as a developer, I got a break. That break was <a href="http://www.apprentice.io/?utm_source=adarsh.io&amp;utm_medium=blog">an apprenticeship at a local development consulting firm</a>. I’m still not clear how I got it, but it was amazing.</p><p>I made $100/day and worked 8 hours shadowing a developer consultant at a client. In the evenings, I would stay up late Googling terms I didn’t understand during the day and practicing new techniques on toy apps. It’s made all the difference to my career and I’m thankful every day for the shot.</p><p>After getting hired as a full-timer (and later, serving as manager), I had a chance to interview candidates and see which ones succeeded.</p><p>This is what I’ve learned about how to successfully run an apprenticeship program.</p><h3>What is a Apprentice?</h3><ul><li>A junior developer with <em>some</em> experience. You will pay this person and train them for a few months with the goal of hiring them as full-time employees.</li><li>They should be able to write and deploy working software, however simple the app is or rough the code is.</li><li>Boot camp grads are usually a good fit. As of this writing, I recommend <a href="https://www.turing.io/?utm_source=adarsh.io&amp;utm_medium=blog">Turing School</a> or <a href="https://devbootcamp.com/?utm_source=adarsh.io&amp;utm_medium=blog">DevBootCamp</a>.</li><li>Everyone from fresh college grads to mid-career switchers are great candidates.</li></ul><h3>How do I Interview Them?</h3><h4>Use the same interview process as your full-timers</h4><p>Give them the same questions/challenges as your full-timers but evaluate their responses with this lens:</p><p>“If I coach this person for 3 months, would their answer meet our expectations for a full-time junior developer?”</p><p>This involves a bit of imagination of what someone’s learning vs. time slope is before you get to work with them.</p><h4>What the Heck is a Learning vs. Time Slope?</h4><p>Through experience, I have discovered that each person has an internal rate of learning. That is, people can accumulate and apply new concepts at a consistent rate. Imagine it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/658/0*wF23awaPPjyL3hrO.png" /></figure><blockquote>For any given candidate their slope will remain constant over time, given ongoing support. (AKA “Pandit’s Postulate”)</blockquote><p>You can use this imaginary non-quantifiable slope to both judge if they are good apprenticeship candidates, and later, if they would be good full-time hires.</p><p>The trick here is to use an interview to figure out what the candidate’s slope is. Good ol’ y = mx + b.</p><p>How do you do that? Well, you get two data points, somehow, and solve for m.</p><p>You can look at their public code samples noting the dates, and watch progression. You can also see if their toy applications increase in complexity over time.</p><p>But these are guesses. You can also run an experiment to get the data.</p><h3>A Hiring Case Study</h3><p>Once upon a time, a designer applied to work with our team. She was very skilled as a visual designer, working mostly in print/media at ad agencies. She was also professional, proactive, and the team really liked her.</p><p>The role I was hiring for required front-end skills, which she did not have. I gave her some homework saying something like “See if you can rebuild your portfolio site using these tools and deploy to GitHub Pages or Heroku.” I gave this homework to lots of non-coding applicants.</p><p>She was the only one to ever respond, and just four weeks later. Now I had two data points: (0,0) and (4 weeks, learn enough front-end to make a portfolio site).</p><p>Solving for a non-numerical m value, I guessed she would be ready for full-time work in 3 months. Turns out, it was 4 months, but her slope kept constant (or improved!). So as a result, I got a top-notch teammate and culture for a pretty small investment.</p><h3>Tactics for Starting Your Apprenticeship Program</h3><ul><li>Put up a separate landing page which feeds into your full-time hiring pipeline. Run ads against it or blog/tweet about it.</li><li>Select for humility <em>and</em> confidence. You want candidates are willing to take a step back to learn, regardless of their past work history or accomplishments.</li><li>Only take candidates excited about the apprenticeship opportunity. Focus on people who want to learn/grow. Otherwise you’re selling something to a reluctant buyer.</li><li>Respond quickly to applicants! You should do this for other candidates also. Just sayin’.</li><li>Develop and document how to screen and mentor apprentices.</li><li>Turn down almost all of your candidates at first, to get a feel for who is out there.</li><li>Be very clear about it being an apprenticeship. Apprentices may not get a job at the end, and they’ll have to work for it. Be clear about that.</li><li>Set a decision point at the end of two months when you make full-time offers. This gives the candidate time to look for another job.</li><li>Don’t have too many apprentices at once. Maybe a ratio of 1:10 or 1:20.</li><li>Also, before you even start the program, you should have a few mentors who are very excited about the program, otherwise you’re forcing something on the team which they may resent.</li></ul><h3>Other Notes</h3><ul><li>Have retrospectives with everyone (Candidates, Apprentices, Mentors, Everyone Else) as you go.</li><li>Frequently iterate based on the feedback. Your success metric should be “number of great full-time hires made out of the program.”</li><li>Make sure candidates get the same experience they’d get on the job. This helps you evaluate the candidate and helps them evaluate you as an employer.</li><li>Try to have more than one participant at a time. This camraderie is helpful support for a pretty stressful job experience.</li><li>Allow candidate to set up their own success criteria and use it to keep them accountable and measure how they’re doing.</li><li>Any learning the candidate does should be shared back with the mentor, maybe in a weekly check-in.</li><li>Encourage candidates to network, go to meet ups, etc. Community is part of the job.</li></ul><h3>Shameless Plug</h3><p>Do you want help setting up a program like this? <a href="/service/mailto:hi@cylinder.work?subject=Saw%20Your%20Blog%20Post!%20Can%20you%20Help%20Us%20With%20Our%20Apprenticeship%20Program?">Email me</a>!</p><p><em>Originally published at </em><a href="http://adarsh.io/on-growing-great-developers/"><em>adarsh.io</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cac86a761be9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/cylinder-blog/you-can-either-steal-great-developers-or-farm-them-cac86a761be9">You Can Either Steal Great Developers or Farm Them</a> was originally published in <a href="https://medium.com/cylinder-blog">Cylinder Digital Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>