<?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 Craig Coffman on Medium]]></title>
        <description><![CDATA[Stories by Craig Coffman on Medium]]></description>
        <link>https://medium.com/@craiguh?source=rss-f0700d6d859------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*1l5rFZiXC381Hme8md9vRQ.jpeg</url>
            <title>Stories by Craig Coffman on Medium</title>
            <link>https://medium.com/@craiguh?source=rss-f0700d6d859------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:40:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@craiguh/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Books I Read in 2018]]></title>
            <link>https://medium.com/@craiguh/the-books-i-read-in-2018-a4a6e07a0e52?source=rss-f0700d6d859------2</link>
            <guid isPermaLink="false">https://medium.com/p/a4a6e07a0e52</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[science]]></category>
            <category><![CDATA[religion]]></category>
            <category><![CDATA[science-fiction]]></category>
            <dc:creator><![CDATA[Craig Coffman]]></dc:creator>
            <pubDate>Mon, 24 Dec 2018 05:31:28 GMT</pubDate>
            <atom:updated>2018-12-24T05:31:28.790Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EGP7bFl3dYywVGnDzuakIQ.png" /></figure><p>Do you like space, technology, or politics? If so, read on, because those categories feature heavily among the books I read over the past year.</p><p>It’s been a personal goal of mine to read more, and in particular I’ve been interested in books that I felt would 1) keep me better informed on current topics, 2) deepen skills that I use everyday at work, and 3) inspire creative thinking.</p><p>I listened to many of these books in audio format (thanks to <a href="https://audible.com/">Audible</a>). I commute to work on the subway from Brooklyn to Manhattan, and the ride can take 20–40 minutes. I’ve found this time to be a great opportunity to listen without distraction.</p><p>Now, please enjoy these poorly-written reviews I wrote mostly on a redeye flight!</p><h4><em>Fire and Fury: Inside the Trump Whitehouse</em></h4><p>By: Michael Wolff</p><p>I kicked off the year with a nice, soothing read about politics and how everything’s falling apart. I found most of this to be very believable, especially after reading some of the sensational stuff in the Bob Woodward book. It’s clearly biased, politically speaking, but presented in a very entertaining way.</p><p><strong>Verdict:</strong> Worrisome, but hard to put down.</p><h4>Children of Time</h4><p>By: Adrian Tchaikovsky</p><p><em>Children of Time </em>is set in a universe where humanity spread across the galaxy as Earth’s ability to support life failed. The story is about an experiment gone wrong on a distant, terraformed planet which results in highly-evolved spiders becoming the dominant species instead of primates. Meanwhile, a remnant of spacefaring humans, searching for a home, happens upon this seemingly welcoming candidate.</p><p>There were a lot of really interesting elements in this book. I enjoyed observing how communication, social and gender norms, and technology developed for such a different type of life form. You watch as spider society evolves and advances while the remaining humans are becoming more desperate and bestial. I’m very excited to see where the story goes next, and it looks like there will be a follow-up in 2019.</p><p><strong>Verdict:</strong> Really fascinating premise, enjoyed it a lot!</p><h4>The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses</h4><p>By: Eric Riess</p><p>I’ve been an advocate of agile software development for over six years, and the lean business model has often come up as a related set of principles. I hadn’t ever taken the time to delve deeply into what they were or the thinking behind it, so I decided to read up.</p><p>The thesis is straightforward: Build for the customer. Conduct research to validate assumptions first. Build the MVP and iterate rather than spending lots of time on a final product that could be completely wrong.</p><p>It was helpful to see these principles applied generally to business, since I had mainly focused on the more prescriptive frameworks that apply them to engineering.</p><p><strong>Verdict:</strong> Common sense business advice.</p><h4>Unf*ck Yourself: Get Out of Your Head and into Your Life</h4><p>By: Gary John Bishop</p><p>This is a self-help book. It’s motivational and “real”. What I got out of it was, basically, don’t give a fuck. But then, do give a fuck about some important things. But don’t overthink it.</p><p><strong>Verdict:</strong> If you need some motivation… sure.</p><h4>The Dark Path: Conspiracy Theories of Illuminati and Occult Symbolism in Pop Culture, the New Age Alien Agenda &amp; Satanic Transhumanism</h4><p>By: Isaac Weishaupt</p><p>I was looking for some good books about the occult and Satanism, but this didn’t really fit the bill because it didn’t have enough depth. “Did you know that rock music is associated with the occult?” Wow, amazing observation.</p><p><strong>Verdict:</strong> Meh.</p><h4>Aleister Crowley’s Liber Al vel Legis: The Book of the Law</h4><p>By: Aleister Crowley</p><p>My motivation for reading this was similar to the last one. Since I spent a lot of my life on the Jesus track, I thought it would be interesting to get some other perspectives. Listening to this in audio format is probably not a great choice. It contains tons of symbolism.</p><p>This book is the central sacred text of Thelema, which Aleister Crowley claims was given to him by a disembodied voice named Aiwass in 1904 while he was in Cairo. I think I might revisit this one later with some analysis to better understand what’s going on.</p><p><strong>Verdict: </strong>3/5 goat sacrifices.</p><h4>Kabbalah, Science, and the Meaning of Life: Because Your Life Has Meaning</h4><p>By: Rabbi Michael Laitman</p><p>This, too, was a selection driven by my exploration of various religious philosophies. I was looking for an introduction to the ideas of Kabbalah and its origins, but this book was about the relationship between spirituality and science. It might be another case of “bad in audiobook format,” but I couldn’t really follow. Still looking for another introduction to Kabbalah, so please send me suggestions if you’ve got any!</p><p><strong>Verdict:</strong> Wasn’t for me.</p><h4>Cracking the Code to a Successful Interview: 15 Insider Secrets from a Top-Level Recruiter</h4><p>By: Evan Pellett</p><p>I changed jobs this year, and read this a couple of months before I started seriously interviewing. There are some good, common sense, tips in the book about presenting yourself, focusing on achievements, etc. However, it feels geared towards sales roles more that my field, software engineering.</p><p>I found it useful to get in the right headspace, but much of the book was not really applicable.</p><p><strong>Verdict:</strong> It’s fine.</p><h4>Cracking the Tech Career: Insider Advice on Landing a Job at Google, Microsoft, Apple, or any Top Tech Company</h4><h4>&amp;</h4><h4>Cracking the Coding Interview: 189 Programming Questions and Solutions</h4><p>By: Gayle Laakman McDowell</p><p>McDowell’s books (and YouTube videos and website) are crucial if you’re studying to interview at Facebook, Google, or similar tech-oriented companies. I can’t say enough positive things about her.</p><p><em>Cracking the Tech Career </em>gives an overview of interview preparation, covering things like how to build a winning resume and how to be a good interviewee.</p><p><em>Cracking the Coding Interview</em>, as the title suggests, focuses on how to succeed in coding interviews. This is more of a study guide. It includes a general approach for problem solving on a whiteboard, overview of Big-O notation with examples, and solutions to some common problems.</p><p>I recommend these books all the time, and I think they’re the best around. Unless you’re a fresh graduate with a computer science degree (and even if you are), the latter will help you brush up on almost anything you’ll encounter as far as algorithm problems.</p><p>There are also variations on these geared toward product management, if that’s your bag!</p><p><strong>Verdict:</strong> Both are a must for engineers.</p><h4>The Dark Forest</h4><p>By: Cixin Liu (Translated by Joel Martinsen)</p><p>I didn’t realize this was book 2 in the trilogy until I was deep into the book. That explains why it was hard for me to get into at first. As a fan of Fermi Paradox theories, I enjoyed it a lot. I recommend the Kurzgezagt <a href="https://www.youtube.com/watch?v=sNhhvQGsMEc">YouTube videos</a> on the topic if you’re not familiar. Excited to jump back in with <em>The Three-Body Problem</em> in 2019.</p><p><strong>Verdict:</strong> Great read, but wish I’d started with the first book!</p><h4>The Man in the High Castle</h4><p>By: Philip K. Dick</p><p>Answers the question: What would the world be like if the Nazi’s had won World War II?</p><p>I was surprised to find out how many “<a href="https://en.wikipedia.org/wiki/Hypothetical_Axis_victory_in_World_War_II">hypothetical Axis victory</a>” books, movies, and games there were out there, because I always assumed this was the original.</p><p><strong>Verdict:</strong> Classic, but I prefer the way the story develops in the Amazon show.</p><h4>A Higher Loyalty: Truth, Lies, and Leadership</h4><p>By: James Comey</p><p>Most of the juicy bits were covered pretty well by news outlets. Can’t help but feel like it’s justifying a couple of bad calls.</p><p><strong>Verdict:</strong> Consider Hillary’s <em>What Happened.</em></p><h4>Blood Meridian: Or the Evening Redness in the West</h4><p>By: Cormac McCarthy</p><p>Hailed as McCarthy’s masterpiece, this is the story of a kid in the Old West. The writing is beautiful and the details rich, but I had difficulty staying focused enough to follow the plot.</p><p><strong>Verdict:</strong> Bailed.</p><h4>Less</h4><p>By: Andrew Sean Greer</p><p>Romantic comedy isn’t something I usually read, but I enjoyed this. <em>Less</em> was the book of the month for a book club at work. It also won the Pulitzer Prize. It’s a funny and sometimes sad story about an aging writer who tries to avoid attending his ex-boyfriend’s wedding by accepting a bunch of invitations to literary events around the world.</p><p><strong>Verdict: </strong>Entertaining. Not scifi, but entertaining.</p><h4>Crucial Conversations: Tools for Talking When Stakes Are High, Second Edition</h4><p>By: Kerry Patterson</p><p>Right after I accepted the offer for my new job, I asked a couple of people at Facebook for book recommendations. The engineering director for my department recommended both this book and the next one on my list. Crucial Conversations is also the name of a course covering the same material that is facilitated by the company. During my on-boarding, I took a similar course called Fast Feedback.</p><p>This book outlines a framework for having hard conversations or being “persuasive without being abrasive.” These are skills that can make or break your effectiveness at work (probably also life?), so I would recommend studying them.</p><p><strong>Verdict:</strong> Good stuff. Worth reading.</p><h4>This Is Now Your Company: A Culture Carrier’s Manifesto</h4><p>By: Mike Rognlien</p><p>Building and maintaining a healthy team culture is everything. It impacts recruiting, retention, inclusiveness, quality of life, and quality of output. As a manager, I feel that creating culture is an important part of my job, but it’s really the responsibility of every team member. This book talks about why that’s the case and contains some strategies for making it better.</p><p><strong>Verdict:</strong> Develop an internal locus of control and read this.</p><h4>The President Is Missing</h4><p>By: Bill Clinton, James Patterson</p><p>I had a free weekend during on-boarding at Facebook in Menlo Park, so I decided to drive down to Santa Barbara to visit my brother and his wife. This book seemed to have a fun plot, and it was co-authored by Bill Clinton. The audiobook was mostly narrated by Dennis Quaid. Clearly, it must be a masterpiece to warrant such star power, so I listened to it while sitting in traffic on the way down.</p><p>The President in the book is some sort of Jack Ryan hero character. There’s a cybersecurity threat that could take down all of civilization, and he’s the only one that has the common sense solutions to defuse this cyber bomb. Okay. Also, there’s a section where he goes incognito in public to elude detection. I can’t help but imagine Bill Clinton sneaking through a shopping mall wearing glasses and a fake mustache.</p><p><strong>Verdict:</strong> Not enough suspension of disbelief available to enjoy.</p><h4>The First 90 Days, Updated and Expanded: Proven Strategies for Getting Up to Speed Faster and Smarter</h4><p>By: Michael Watkins</p><p>I read this hoping it would help me to get organized while ramping up at the new gig. I liked the framework for getting up to speed and building rapport with your team. The book outlines milestones along the first 90 days of the process, with the premise that if you haven’t ramped up in 90 days, you’re not going to be well-positioned to be successful.</p><p>That said, I didn’t actually apply much from the book. I would imagine that for those who didn’t have as much structure coming in, it might be more valuable.</p><p><strong>Verdict: </strong>Good ideas, wasn’t immediately useful.</p><h4>Why I’m No Longer Talking to White People About Race</h4><p>By: Reni Eddo-Lodge</p><p>This book talks about racism, the fallacy of meritocracy, the whitewashing of feminism, and, despite its title, the importance of actually engaging in a meaningful dialog about all of it. It also gives a history of racism in Britain, which I knew nothing about.</p><p><strong>Verdict:</strong> Read it!</p><h4>Sapiens: A Brief History of Humankind</h4><p>By: Yuval Noah Harari</p><p>This book is educational, thought-provoking, and surprising. Everyone I know who has read it, loves it. It covers how humans came to be humans and how that informs where we’re heading as a species.</p><p>I also read the follow-up, <em>Homo Deus</em>, which you’ll see below. Both are awesome. If you liked either of these, then consider Ray Kurzweil’s <em>The Singularity is Near.</em></p><p><strong>Verdict:</strong> Favorite book of the year, must read.</p><h4>The Wayfinders: Why Ancient Wisdom Matters in the Modern World</h4><p>By: Wade Davis</p><p>This book, like <em>Sapiens</em>, talks about the development of humans, but through the lens of indigenous cultures from around the world. It’s a good reminder that ancient wisdom still has value, and that we’re not as smart and advanced as we sometimes like to think.</p><p><strong>Verdict:</strong> Liked it, but not as much as <em>Sapiens.</em></p><h4>Fear: Trump in the White House</h4><p>By: Bob Woodward</p><p>This is a book by a very credible journalist.</p><p><strong>Verdict: </strong>We’re all in so much trouble.</p><h4>The Fifth Season: The Broken Earth, Book 1</h4><p>By: N. K. Jemisin</p><p>This book is a beautiful mixture of sci-fi and fantasy. I’ll probably continue reading the series in 2019.</p><p>The story is set on Earth, but it’s unclear if it’s in the distant future or past. There is a magic called Orogeny that enables some to control seismic elements. There are subtle hints about what brought the world to its current state that I enjoyed.</p><p><strong>Verdict:</strong> Great story, interesting world.</p><h4>The End of Faith</h4><p>By: Sam Harris</p><p>As a formerly religious person, I find it to be a fascinating subject. This book seeks to demonstrate why religion is harmful and dangerous. It spends a lot of time on Islam in particular.</p><p>I don’t endorse the intolerant ideas presented in the book. I <em>would</em> like it if all people, religious or not, stop hurting and killing each other. However, there are some good points about how we’ve insulated religion from critique.</p><p><strong>Verdict:</strong> Thought-provoking but in some cases too extreme.</p><h4>Homo Deus: A Brief History of Tomorrow</h4><p>By: Yuval Noah Harari</p><p>This is a follow-up to <em>Sapiens</em>, and it holds up to its predecessor very well. A couple of sections stand out to me. I particularly enjoyed the discussion of how humans were able to become the dominant life forms on Earth, not due to their ability to organize as a collective (bees and ants do better there), but because they can share a belief in concepts that don’t actually exist. For instance, a company can own property, have value, and build trust in people, but the company is just an idea. The same goes for money, kingdoms, and religion. These beliefs are more effective than social groups, because such groups can only reach a certain size before they fall apart. Scalability is key to success, as usual.</p><p>I also enjoyed the sections on the mind, self-awareness, and free will. Is our mind truly just the data that we store in our brains, or is there a missing element we don’t understand that makes us who we are? If we can break down the algorithm that defines our decision-making and personality to the point that super computers are able to perfectly predict our responses, do we really have the capacity for free will? Are we any more complex than other animals? Can we transfer our consciousness entirely into a digital paradise and live forever? The book doesn’t answer the question, unfortunately.</p><p><strong>Verdict:</strong> Pretend you control your destiny and choose to read it.</p><h3>What I’m Reading Now</h3><p><em>Neuromancer, </em>by William Gibson. The classic cyberpunk novel. Pretty dated, though.</p><p><em>Soviet Women: Walking the Tightrope</em>, by Francine du Plessix Gray. Non-fiction about the lives of women living in the Soviet Union. Very dense. Going to take some time.</p><p><em>The Gnostic Gospels,</em> by Elaine Pagels. Talks about why the Bible contains some gospel accounts and not others. So far, really great! About halfway through.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4a6e07a0e52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Communicate With Software Engineers]]></title>
            <link>https://medium.com/@craiguh/how-to-communicate-with-software-engineers-806c4f7cf7cf?source=rss-f0700d6d859------2</link>
            <guid isPermaLink="false">https://medium.com/p/806c4f7cf7cf</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Craig Coffman]]></dc:creator>
            <pubDate>Mon, 23 Oct 2017 17:28:21 GMT</pubDate>
            <atom:updated>2017-10-30T00:39:49.615Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VgS2EFaZbI0P9odvle2GIw.png" /></figure><p>In my adventures leading engineering teams and acting as their advocate, I’ve learned the importance of being a capable translator. Even in the world of tech startups, it’s not uncommon to find people that don’t really understand “this software stuff.” It’s not surprising. As our world advances, we keep adding layers of abstraction between the biological and the technological, to the point where the technology we interact with is only noticed when it fails.</p><p>People <em>really </em>notice when it fails! We rely on software in many aspects of life, and when it doesn’t work as expected, it’s painful. When Alexa doesn’t play the song you ask for, you may just shrug it off. However, when the developer a few desks away from you makes a decision–or mistake–that costs the company time or money, it’s hard to stay cool.</p><p>For the technically uninitiated, understanding how to work effectively with engineers can be a challenge, and bumps in the road are inevitable. I’m going to share some insights that will help you avoid the rough patches, and collaborate with engineering teams effectively.</p><h3>Learn The Ropes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/686/1*phgVcpSv0vO5OoDuT-dnOg.jpeg" /><figcaption>Ned Ludd, notable technophobe and Robin Hood’s flatmate</figcaption></figure><p>Collaboration starts with empathy. You’re going to need to equip yourself with an understanding of the fundamentals to empathize with your technical colleagues. That’s not to suggest you need to take a class and start coding (although that’s an option, if you’re interested). The important thing is to be open to learning and to stay curious.</p><p>People love to talk about things they’re good at, and that includes developers. Ask questions and show an interest when you can. Doing so will help you become informed progressively and build rapport.</p><p>Being a Luddite isn’t a badge of honor. The original movement ended no more than a year after it started, and any remaining members of this technophobic movement were shipped off to Australia. Being ‘old school’ may be a source of comfort at home, but embracing progress is vital to success in business.</p><h3>Don’t Build Walls</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iy6NrIm1yG88feG1gZ9dGQ.png" /></figure><p>Developing software is still a relatively new field, and the technical lingo is only where it starts. The way projects are organized, the KPI’s, and team hierarchy are also different than other functions. People sometimes treat engineers differently than their other colleagues, and there is no shortage of bad stereotypes. Fight the tendency to treat or see the technical team as a separate team.</p><p>While the business of software development is a team-oriented, collaborative process, engineers often spend a large portion of their time heads-down and headphones-in. Don’t confuse quiet for a lack of enthusiasm. Most developers are more than happy to help out, brainstorm, or listen. So much so, in fact, that we need strategies to make sure developers can stay on task while quickly identifying incoming requests that merit immediate attention. Help desk software can be instrumental in load balancing, prioritizing, and tracking the response to issues that arise.</p><p>I’ve received many eye rolls and groans when I’ve instituted ticketing systems for requesting developer support. I sympathize–doing so <em>feels </em>like too much process, and it runs the risk of creating yet more communication barriers. On the other hand, having no system for prioritizing tasks and their assignment isn’t viable at scale. Tech leaders must use process as a tool to protect from waste (of time and effort), but that should be complemented by constant advocacy for open lines of communication.</p><h3>Assume Good Intent</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Dwa5pfAORD3Cb17ILZnJeQ.jpeg" /><figcaption>Captain Hindsight, swooping in for a post-mortem meeting</figcaption></figure><p>Even when the lines of communication are strong, stressful situations can arise. People make mistakes, forget things, and say hurtful things thoughtlessly. It can be confusing and frustrating when the same person that stayed up all night to build your feature then forgets to deploy it in the morning.</p><p>I cannot overstate the power of positivity. When someone fails to deliver, misses a timeline, or something breaks, try this: Imagine an explanation (within the realm of reality) where the person had the best intentions and meant no harm. Can you think of a realistic explanation? In lieu of knowing all of the details, assume the best. Once you’re on the other side of the situation, there will be time to figure out the real source of the breakdown.</p><p>Poor or unreliable behavior should not be tolerated, but negativity while in crisis is only going to work against you. Keep Captain Hindsight at bay until the post-mortem meeting. <em>Always</em> make time for the post-mortem meeting. <a href="https://www.audible.com/pd/Business/Radical-Candor-Audiobook/B01MZ6RMS4/">Radical candor</a> will be a valuable tool once you’re there.</p><p>It’s also important to acknowledge that there are areas of expertise where you may not have the full picture or experience to back up your opinions. In addition to assuming good intent, build a foundation of trust with your team mates, and ask questions to prove or disprove your assumptions.</p><h3>Avoid Icebergs</h3><p>Every developer has heard it: “That change should only take five minutes!” Sometimes the assessment is correct, and sometimes it’s wrong. A broken clock is right twice a day. Pro-tip: If you find yourself tempted to say those words, consider rephrasing it as a question.</p><p>I’m not suggesting that software engineers need to have their egos stroked at all times. In reality, even our estimates are very often wrong. Here’s one reason why.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7Ao4_b0W7hKo_W05LPOXhg.png" /><figcaption>The tip of the iceberg, estimated</figcaption></figure><p>People are good at estimating based on known quantities. You want a feature, so you’ll need to tell the developer. They will write some code, probably, and once it’s finished, they ship the feature. Simple!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ocdZJOkgNCj2u5RaC4Ucbw.png" /><figcaption>The rest of the iceberg, estimated</figcaption></figure><p>Here’s the reality in a team-based environment. The developer was doing something else, so they have to snap out of it and field your request. Assuming no planning is required and no dependencies exist, they write some code. It’s the team’s policy to peer review changes in order to eliminate “bus factor” and uphold code style and design guidelines. It’s also team policy to have QA test the feature before shipping it. Next, it has to be deployed. Depending on the platform, this process can vary a great deal–from painless/instantaneous to a multi-day review process courtesy of Apple. Now the feature is out in the wild. The developer: “What was I doing, again?”</p><p>You might be thinking, “That seems like overkill. I <em>just </em>wanted the text to be a different color.” That’s true. Dropping everything to change the color of text is outrageously expensive, time-wise. That’s why we’ve created systems to queue and prioritize tasks. Scrum does this by packaging work into time-boxed iterations, or sprints. Kanban solves the problem by controlling the number of tasks in progress. Both use a queue, or backlog, to allow work to be sorted by priority.</p><p>Interrupting scheduled work to inject another task is essentially a very abrupt change in priority. If you find yourself shifting priorities a lot–particularly interrupting other work–it will be worthwhile to determine why.</p><h3>Don’t Hack Habitually</h3><p>There are good hacks and bad hacks. When Zappos started, the founder took pictures of shoes on sale at the local mall and listed them online. When a purchase came in, he would go back, pick them up, and ship them out. That was a good hack, because it proved the concept. It was also a bad hack because they lost money on each transaction.</p><p>This is the definition of hack that I’m talking about here: To make a quick code change to patch a computer program, often one that, while being effective, is inelegant or makes the program harder to maintain (from: <a href="https://en.wiktionary.org/wiki/hack">wiktionary</a>).</p><p>Use hacks to prove the concept. If it works, resist the urge to make it a habit, and instead get the hack built into a permanent, repeatable solution.</p><p>Why? This isn’t just another formality; hacks come at a cost. They often require developers to support them, which means you’ll be waiting on us. It interrupts otherwise scheduled work (see previous section), and corners may have been cut on process, which can be risky.</p><p>It’s really hard to stop doing something that works. If the hacked solution produces sales or saves time, giving it up will be a challenge. If you need help breaking the habit, consider getting together to brainstorm better solutions as a group, and don’t forget to include engineering and product stakeholders.</p><h3>Strategies</h3><p>When it comes to internal communication, choose the right medium. What kind of response is desired, synchronous or asynchronous? If your request needs an answer right away, then go speak in person or make a phone call. On the other hand, if it’s either non-urgent or informational only, consider email. If you have no qualms with your message getting overlooked accidentally, Slack or GChat are probably the way to go.</p><p>Consider who you need to contact. Don’t “spray and pray” by emailing a dozen engineers. If you don’t know who to talk to, check with an engineering manager or product manager. If a system is in place for reaching the on-call developer, use it. If you hesitate to do so because it’s been ineffective, take the time to talk to the person that instituted it, and work with them to find ways to improve the solution.</p><p>You shouldn’t have to walk on eggshells around developers. Ask for what you want. If it’s urgent, ask if it can be done sooner. Just be careful not to minimize others’ effort in the process. Remember the “it’s <em>just</em> a text change” example. Bad phrasing like that is an easy mistake to make–I get called on it from time to time.</p><p>Software engineers are humans (for now), and there’s a good chance that you are, too. I hope that some of these tips will help you to work alongside them more effectively. End of line.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/625/1*eYKOYRj6G1zCXGSB71kwcA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=806c4f7cf7cf" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>