<?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 Kaanon MacFarlane on Medium]]></title>
        <description><![CDATA[Stories by Kaanon MacFarlane on Medium]]></description>
        <link>https://medium.com/@thekaanon?source=rss-a4d31c5abf99------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nmIATSdxhc0q3MND.jpg</url>
            <title>Stories by Kaanon MacFarlane on Medium</title>
            <link>https://medium.com/@thekaanon?source=rss-a4d31c5abf99------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 10:02:54 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thekaanon/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[Management Values and Virtues]]></title>
            <link>https://medium.com/@thekaanon/management-values-and-virtues-63518cbfc933?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/63518cbfc933</guid>
            <category><![CDATA[values]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Fri, 04 Nov 2022 03:27:33 GMT</pubDate>
            <atom:updated>2022-11-04T19:00:36.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*Cra7DkGEVYirKMVXP4R2nQ.jpeg" /></figure><p>These are the values I have as an Engineering leader, and the virtues I try to make sure the teams have in order to exemplify these values.</p><h3>Growing engineers</h3><p>It’s the responsibility of an EM to find out what engineers want. We can’t promise they will get to do whatever they want all the time (sorry crypto fans), but we <em>can</em> promise they won’t have to do things they don’t like all the time either. One of the fun parts of management is figuring out how to map employee goals to the business goals and matching. It’s also about setting the context for engineers to understand why a less attractive project might actually be the most impactful.</p><h4>Delegate for Growth</h4><p>One of the best ways to grow your staff (and free your time) is to delegate. However, it must be done intentionally so that the individual is now more capable than they were at the beginning. Depending on their level of aptitude at that particular task, you might demonstrate while they watch carefully before handing over the responsibility. You might give lots of guidance and coach them through it. You might even explain the problem and only check in for progress. How you decide to engage must be done on a case by case basis, based on the individual and project you want them to take over.</p><p><strong>Virtues</strong></p><ul><li>Assigning more senior engineers projects where they must work across teams</li><li>Making sure each senior engineer has an area of responsibility and runs a team level function</li></ul><h3>Range</h3><p>I want my engineers to grow <a href="https://davidepstein.com/the-range/">Range</a> by trying out a bunch of stuff over their career to learn what they really enjoy and then go deeper into that. I think it’s easy to remember that many people start out their career in one technology, but might enjoy others as well.</p><p><strong>Virtues</strong></p><ul><li>Encouraging client engineers to do a little backend, and vice versa</li><li>Encouraging product engineers to develop something for the platform, and vice versa</li></ul><h3>Product Thinking</h3><p>I believe that engineers need to fully understand how the end user of their work experiences it. For Product Engineers, this means <em>using</em> the product, not just understanding how it works from a technical perspective. For more platform focused engineers, it’s best to see how the clients get built from end to end.</p><p><strong>Virtues</strong></p><ul><li>Engineers take part in product brainstorms</li><li>Engineers are expected to run basic analysis on experiments</li><li>Engineers can propose their own ideas and get them on the roadmap</li><li>If an idea takes less than 1 day, the engineer should just do it and run an experiment.</li></ul><h3>Chainability</h3><p>Setup things for the next plan.Things need to work in sequence. Design a sequence that grows towards your end goals</p><p><strong>Virtues</strong></p><ul><li>Assign promising future leads on the team with someone who’s an attrition risk.</li><li>Build a “bench” of strong leaders underneath you, on every team, who can take on responsibility from you and give you room to grow into.</li><li>Give small projects to new employees to familiarize themselves with the codebase before working on big projects.</li></ul><h3>One-on-ones</h3><p>Meeting with your engineers is a key event that should happen regularly, usually weekly. They are for understanding the needs of your team, not project status updates. Status updates should happen alongside other stakeholders, like product, design and data. This is where you can help coach them through tough problems, understand what’s happening that you might be aware of and give them feedback.</p><p><strong>Virtues</strong></p><ul><li>Use a shared doc to allow the engineer to drive the conversation</li><li>Regularly (every other month or so), have a <em>career convo</em>, to record major accomplishments, give each other feedback and build towards bigger goals outside of day to day engineering work.</li></ul><h3>Culture</h3><p>One of the most important parts of a well functioning team is it’s culture of a team, the set of norms for individuals interact within a group. There are few things that Leaders should do to help create a culture of trust, belonging and honesty so that engineers are able to have the psychological safety required to perform at the best of their abilities.</p><p>At the end of the day, it’s a <em>job</em>. Hopefully it’s a good job, but it’s not that serious. It’s ok to be light-hearted. Laugh. Tell jokes, heckle in the Google meet chat. Have some fun.</p><h3>Transparency</h3><p>Everyone wants to know what’s going on. It’s important to share metrics with employees, so they understand progress towards goals and how their work relates to it. It’s also important to be honest about other things, like future plans, or LACK of future plans. Things like where they need to improve and how to get a promo. Sharing this information (within reason) with your team members is one of the ways to build trust. The modern business environment doesn’t work without trust, and growing this as part of your culture leads to happier workers and happier teams.</p><p><strong>Virtues</strong></p><ul><li>Openly discussing company team feedback results</li><li>Asking for and accepting feedback from subordinates even when it’s hard to hear</li><li>Sharing your concerns, as long as they are constructive</li><li>Don’t badmouth <em>people, </em>keep complaining out of group meetings</li></ul><h3>Diversity</h3><p>We want to build a product for the whole world, so it makes sense that the whole world should help build it. Growing the diversity of background is well proven to <a href="https://www.forbes.com/sites/forbestechcouncil/2021/11/12/how-diversity-can-help-with-business-growth/?sh=5deb49b352ad">improve business metrics</a>, but it’s also <em>right.</em> It’s right for us to make sure that we reflect the varied experiences of our user base.</p><p>Diversity leads to more diversity and hiring for different groups allows each to become more comfortable after a critical mass is reached.</p><p>We do not “lower the bar” but look further for those who might be great.</p><p><strong>Virtues</strong></p><ul><li>Aspire to interview as close to gender balance as possible for open roles</li><li>Assign some administrative projects to men, as women are often over assigned these projects</li><li>Run your job listing text through analysis to make sure to not use accidentally gendered words that won’t be well received by female candidates.</li></ul><h3>Driving results</h3><p>We are trying to build stuff. Project management, either directly or through proxy is important to get things done.</p><p><strong>Virtues</strong></p><ul><li>Project tracker meetings ensure no project gets lost</li><li>Use Experiment Tracking documents to ensure no experiments get lost</li><li>Have a regular cadence to go over team OKRs to make sure progress is being made</li><li>Check in on the code your engineers write. Most engineers should be committing code every few weeks</li><li>Hold engineers accountable for their own project time estimates</li><li>Take steps to address poor performance. Engineers must be given a chance to improve, with clear direction or we can find an engineer who will be able to perform at the level that meets our expectations.</li></ul><h3>Great Books to Read</h3><p>One of the important parts of managing is recognizing that you also need to grow. Devoting time to this is the only way you’ll be able to improve and grow in your management skills. One way to do this is by reading books on management and applying some of the lessons you learn. There’s a lot of great content out there, but these are some of my favorites.</p><h4>Books</h4><p><a href="https://a16z.com/book/whatyoudo/">What you do is who you are</a> by Ben Horowitz</p><p><a href="https://davidepstein.com/the-range/">Range</a> by David Epstein</p><p><a href="https://erinmeyer.com/books/the-culture-map/">The Culture Map</a> — Meyer</p><p><a href="https://www.goodreads.com/book/show/11721498-the-progress-principle?from_search=true&amp;from_srp=true&amp;qid=oDhIjrWV2O&amp;rank=1">The Progress Principle</a> by Teresa Amabile &amp; Steven Kramer</p><p><a href="https://echelonfront.com/extreme-ownership/">Extreme Ownership</a> — Willink &amp; Babin</p><p><a href="https://www.goodreads.com/en/book/show/324750.High_Output_Management">High output management</a> by Andy Grove (CEO of Intel!!!!!)</p><p><a href="https://www.goodreads.com/book/show/15798078-decisive?from_search=true&amp;from_srp=true&amp;qid=l5ZdS0C1Eg&amp;rank=3">Decisive: How to Make Better Choices in Life and Work</a> — Chip Heath &amp; Dan Heath</p><p><a href="https://www.goodreads.com/book/show/11721966-good-strategy-bad-strategy?from_search=true&amp;from_srp=true&amp;qid=gbv4EAE4Zi&amp;rank=1">Good Strategy Bad Strategy: The Difference and Why It Matters</a> by <a href="https://www.goodreads.com/author/show/1709397.Richard_P_Rumelt?from_search=true&amp;from_srp=true">Richard P. Rumelt</a></p><p><a href="https://www.goodreads.com/book/show/25744928-deep-work?from_search=true&amp;from_srp=true&amp;qid=HXtZhW59l7&amp;rank=15">Deep Work: Rules for Focused Success in a Distracted World</a> by <a href="https://www.goodreads.com/author/show/147891.Cal_Newport?from_search=true&amp;from_srp=true">Cal Newport</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63518cbfc933" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role-based team building: a philosophy]]></title>
            <link>https://medium.com/@thekaanon/role-based-team-building-a-philosophy-9ac085253587?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ac085253587</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[team-building]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Sun, 27 Sep 2020 23:56:53 GMT</pubDate>
            <atom:updated>2021-01-12T20:06:48.510Z</atom:updated>
            <content:encoded><![CDATA[<h3>Role-based team-building: a philosophy for engineering teams</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/833/1*Su2pCK3sYwsDsoalT9LrWQ.png" /><figcaption>Mighty Avengers #1 (2007)</figcaption></figure><p>In the workplace, we build teams of engineers, but typically we source candidates based on skills. My philosophy is that, in addition to hiring for skillset &amp; experience, we also build teams based on filling a <em>role</em>. I’ll define the roles in a bit, but first, let’s set up some context.</p><p>One of the few good points of the quarantine has been getting back into D&amp;D with some old friends.</p><p>I play a Warlock, a magic user who has a pact with a being who grants them great power (I mostly use it to blow stuff up). One of my friends plays as a Paladin, essentially a Holy Knight. The Sorcerer is part of a magical bloodline that they use to power their mastery of the Arcane arts. Our Druid is one with nature, he can even turn into an animal if the situation calls for it.</p><p>A typical adventure for our party involves wandering around ruins, checking for traps, and looking for treasure until some enemy finds us (last time it was a huge Double-headed snake!) The Paladin dives right in, attacking with his sword and holding his shield to protect himself. The Druid might follow suit, turning into a giant bear to engage the enemy, or standing aside to heal the Paladin. The sorcerer uses magic to control the battlefield with spells. And me? I just stand really far away and shoot at it, with my Eldritch Blast, drastically damaging the snake. Most of the time, we don’t die. Most of the time, it works. But, if we didn’t have this particular makeup of the party, it wouldn’t work at all.</p><p>You see, my Warlock isn’t just a magic user. I’m DPS (damage per second) and I deal damage on the enemies. The Paladin isn’t <em>just</em> a knight, but a Tank, who soaks up damage from the enemy (that’s why the shield comes in handy). Our sorcerer acts as support, keeping other enemies at bay, or helping the rest of us to play to our strengths with spells that help us. Our Druid is either a Tank who soaks up damage or Support, who heals us, depending on the situation. The party wouldn’t be successful without these people, but not because of the <em>class</em> of character we play, but rather, our <em>roles</em>.</p><p>We can see the concept of <em>role</em> on a team everywhere.</p><p>It’s in action movies:</p><ul><li>Planner</li><li>Disguise</li><li>Demolition</li><li>Hacker</li><li>Face</li></ul><p>In basketball, there are positions like Point guard and Center. But these are different from the <em>roles</em> they play on the court.</p><ul><li>Scorer</li><li>Facilitator</li><li>Enforcer</li><li>Motivator</li><li>Glue guy</li></ul><p>In comics, like the Avengers or X-Men, you can see it all the time</p><ul><li>Tech: Iron Man or Beast</li><li>Power: Thor or Storm</li><li>Leader: Captain America or Cyclops</li><li>Damage: Hulk or Wolverine</li><li>Teleportation: Doctor Strange or Nightcrawler. (If you are up to date on comics, maybe Manifold on Hickman’s Avengers or Magik on his X-Men.)</li></ul><p>‘It’s always sunny in philadelphia’ even commemorated the concept in the episode <em>The gang solves the gas crisis.</em><strong><em> </em></strong>The roles they create are:</p><ul><li>Brains</li><li>Looks</li><li>Muscle</li><li>Wildcard</li></ul><p>Amusingly, when discussing this episode with my siblings, we each assigned out the various roles to one another, but considered ourselves to be the enigmatic Wildcard. 😂</p><p>One of my favorite movies, ‘Inception’, also did this well. It went so far as to name the roles. I’ll use this as a framework for outlining the types of roles that we need to build high performing engineering teams.</p><p><em>Cobb</em> (Leonardo DiCaprio) is the film’s best Extractor. In our set of roles, he’s the <strong>Sage</strong>, who’s seen it before and knows what to stay away from. He messes up constantly at the second point, which was incredibly relatable to me.</p><p><em>Arthur</em> (Joseph Gordon-Levitt) is the Point man who sets up everything and makes sure everything is running properly. We’ll call this role the <strong>Administrator.</strong></p><p><em>Ariadne</em> (Elliot Page) is the Architect in the story, designing the dream worlds the characters will travel in. For us, she’s the <strong>Visionary,</strong> we see her several times thinking on her feet to adjust to the shifting reality in ways to make sure the plan goes through.</p><p><em>Eames</em> (Tom Hardy) is the Forger, who pretends to be other characters to trick the mark in the movie. This versatility allows him to be whatever the team needs him to be, whether presenting as the mark’s godfather, or fending off security during later scenes. His role is the <strong>Chameleon</strong>, able to shift into any role and perform any task.</p><p><em>Yusuf</em> (Dileep Rao) is the Chemist, who enables the rest of the team to succeed with his innovative technology. This role, which takes many forms based on the team, is that of the <strong>Chemist,</strong> because without chemistry, any team will fail.</p><p><em>Saito</em> (Ken Watanabe) is the Tourist, who bankrolls the mission and tags along to make sure things progress. He even sacrifices himself at one point, in order to ensure the mission’s success. I’ll call this role, <strong>The Manager.</strong></p><p>There’s also another role that’s not present in the film, but is very important for building software. It’s <strong>The Professional</strong> who gets the job done, with little complaint and puts in the work to build things. Obviously, every team member is a bit of a Professional, but one who does this well, with high productivity helps unlock the speed of others as well.</p><p>Keep in mind, <em>roles</em> are distinct from the title we have. There are many backend engineers who are visionaries, designers who keep the logistics going and so forth. While each of these skills is important in a vacuum, software isn’t built in isolation. <strong>It’s best built by teams.</strong> And teams don’t work as a collection of parts, but as an organic unit. The body is not comprised of skin, bones and muscle, but of hands, eyes and feet. A team is not merely built from Mobile, API and Database engineers, but consists of Sages, Visionaries, Professionals, Chameleons, Administrators, Chemists and Managers.</p><p>I’ve been on teams with nothing but Visionaries. We had lots of great ideas, but nothing got done. I’ve been on teams with lots of Chameleon’s but sooner or later, the lack of deep expertise rears its head. As I’ve built more teams, I’m finding it more important to consider the roles that an individual can fill, and not <em>only</em> what their <em>skills</em> can provide.</p><p>Let’s dig into these roles a little more for a clearer explanation</p><h4>The Manager</h4><p><em>All right, what’s next?</em></p><p>Typically, the on-paper Engineering manager, or Product Manager, this is the person DRIVING the project. Someone who isn’t afraid to get their hands dirty, and especially someone who makes sure the team is unblocked. The job of the Manager is to support their team and make sure they are working on the most impactful projects possible. The Manager is the one who decides <em>what</em> the mission is, and why it’s important. They are also the one who’s accountable if things go awry.</p><h4>The Administrator</h4><p><em>Looks like everything is in order</em></p><p>The project planner, the scrum master, the bug triager, the release manager. Someone needs to make sure there is an oncall runbook and alerts on all the important systems. While the manager makes sure the car is headed in the right direction, the Logistician is the one who gets the directions and schedules keeps an eye on the fuel tank. In a software development project, this is the person who intrinsically values order and process. This is the person who <em>looks</em> at the burndown chart and knows how many story points the team is capable of accomplishing in a sprint.</p><h4><strong>The Visionary</strong></h4><p><em>Maybe we should try this solution</em></p><p>The person who comes up with ideas. The one who figures out how to move forward when the team is inevitably stuck. A typical scene is the engineering team sitting around, having finally understood the mission, and why it’s important. But now, how do they build it. We could try &lt;old technology X&gt;, but it probably won’t scale. We could just add it to our existing system, but it’s not really meant for this new use case. The visionary is the one who sees the way forward and can articulate a new path. This is especially an important role in THE MIDDLE of the development lifecycle, when things come up (as they always do). The visionary is the one who suggests innovative ways out of the maze and gets the team back on track.</p><h4>The Chemist</h4><p><em>We’re going for lunch, want to come?</em></p><p>One of my favorite books is “The Book of Basketball” by Bill Simmons. In it, he has a chapter about how the secret of basketball, is that it’s not really about basketball, but people. And the real truth of software development is that the <em>people</em> who build it are just as important as the speed, performance and complexity of the technical solutions. The Chemist is the one who recognizes that. They are the party planner, the joke teller. They are the one who keeps the conversation going and is always trying new things. Similar to the Chemist in Inception, the team couldn’t really GO without the chemist. They would little-g go, but it wouldn’t be the same. A team can’t reach its full capacity if you just have a bunch of technically proficient humans (even in those other roles) who don’t have a good relationships amongst each other. One thing that’s special about people who perform the Chemist role well is that they help the relationships not be just 1 on 1, between 2 nodes, but they build a graph of friendship and trust, which together super-charge the team. It’s always better to build things with people who enjoy spending time with one another.</p><h4><strong>The Sage</strong></h4><p><em>There might be dragons in that canyon, let me show you the way</em></p><p>The Sage has been there. They’ve done this all before. They understand how to build role-based access control. They’ve sharded MySQL in the past. They know that a simple way to improve speed is to place a Memcache or Redis cluster in front of the real backend. This person helps the team <em>avoid</em> the mistakes of the past. They also add confidence to the rest of the team, because even though new solutions will NEVER be the exact same as old ones, knowing that they pass inspection from the Sage will allow the team to build faster and without as much doubt.</p><p>The Sage is often the one who brings people along and grows them. This is one of the hardest roles to fill, because it requires both a breadth of experience, a ton of patience and the willingness to share your skills.</p><h4>The Chameleon</h4><p><em>I’ll figure it out</em></p><p>Every engineer eventually encounters that one engineer who seems to be able to do <em>anything</em>. While it’s uncommon, there are people who have a breadth of experience and showcase a tremendous amount of versatility. These individuals fill in the gaps of the team, especially when the team is going through transitions. They are the one who is proficient in front-end, back-end and systems administration. These are those full-stack developers who might not be able to build you a system from scratch, but are very adept in systems that are already there.</p><h4>The Professional</h4><p><em>I finished two tickets and I’ve got one in review</em></p><p>Sometimes, you need someone who just excels at getting things done, unlike the Chameleon, this person might be a generalist or a specialist, but the key point is that they DO THE WORK, even if it’s not the sexiest work. It invigorates them, and they are good at it. Their productivity pushes the team forward. This is one of the most important roles, and one you should make sure you have filled.</p><p>Recently, I was hiring engineers for my team at work and needed to think about what type of engineers would fill the needs of the team. I wanted someone with Android experience, but I also need someone who cares about the logistics of our development process. I needed a iOS developer, but it would be really nice if they also interact well with other teams as a representative. I finally realized the end shape of the team also needed to account for roles, much in the same way that our Dungeons &amp; Dragons party did.</p><p>I took a look at the existing members of my team and realized that maybe I didn’t know them as well as I thought I did. I used our 1:1 sessions to discover what role they might fill, and found that I already had several of the roles filled. Now when I was conducting interviews, I was able to craft my questions in such a way to start to understand the type of role that each candidate was, and could hopefully fill on my team. I’m not sure if I would hire solely on any of these attributes, but they were definitely factors in how I wanted my team to look once all positions were filled.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ac085253587" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2018 Book Rundown]]></title>
            <link>https://medium.com/@thekaanon/2018-book-rundown-c70e015605be?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/c70e015605be</guid>
            <category><![CDATA[books]]></category>
            <category><![CDATA[review]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[year-in-review]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Thu, 27 Dec 2018 18:56:15 GMT</pubDate>
            <atom:updated>2018-12-27T18:57:27.561Z</atom:updated>
            <content:encoded><![CDATA[<h3>My 2018 Book review</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XktYI0r7XSFXTDE5hQnwSw.png" /></figure><p>The older I get the more I’ve given myself over to admitting the truth. I like to read. No, I <em>love</em> to read. The ability to dive into another experience, real or fictional, is incredible. I can learn deeply about a subject in a way that documentaries or articles will never reach. I can immerse myself in a fantasy, either close to real life or in a universe far away. Most importantly, I can continue to grow.</p><p>I’ve always wanted to do this, a sort of book report of my readings. As I read more, I forget more, and this is a bald opportunity to revisit some of my favorite books and remember why I loved them.</p><p>I decided to sort the books into a light ranking of Incredible, Recommended, Fine, and Unfinished</p><h3>Incredible 📕📘📗📙</h3><h4>The Color of Money: Black Banks and the Racial Wealth Gap 💸</h4><p><em>Mehrsa Baradaran</em></p><p>BASICALLY THE BEST BOOK. So… why are black people more poor? Wasn’t slavery abolished, like, 150 years ago. If you’ve ever wondered what’s going on, this is the book for your. From the stopping of reparations, to sharecropping, to redlining, Black people have continually been pushed down and kept out of earning wealth. It’s why so many white people I know have rich uncles and grandfathers, and most every black professional I know is at or near the top of earning in their entire family. The problems are much more systemic than I realized. The book also goes deep into why “banking black” isn’t a panacea, because of the structural problems with taking money and loaning it to other banks. Required Reading.</p><blockquote><em>There is a pervasive myth that immigrant success was based purely on individual work ethic. Certainly there was a lot of hard work and perseverance, but left out of this popular narrative was the significance of the FHA– GI Bill combination, the government subsidy that bolstered the work and turned it into capital-producing assets.</em></blockquote><h3>Bad Blood: Secrets and Lies in a Silicon Valley Startup 💉</h3><p><em>John Carreyrou</em></p><p>Read like a novel. Amazing. You won’t believe the fraud and lies that happened as this biological startup pretended it was a tech startup, playing fast and loose with regulations. When the undercover CIA agent showed up I couldn’t thought to myself “this book has EVERYTHING”</p><blockquote><em>It was as if Boeing built one plane and, without doing a single flight test, told airline passengers, “Hop aboard.”</em></blockquote><h3>Lab Girl 🌲</h3><p><em>Hope Jahren</em></p><p>A good friend, who happens to be a librarian recommended this. It’s probably the most beautiful book I’ve read in years. And it’s about Botany (!), a subject I wouldn’t have expected to get so much joy from. It’s an autobiography, but it’s so much more than that. The subject of chapters switches from a phase of her life, either in school or as a professor, to one about plants, usually trees. With this style she weaves beautiful imagery of lifelong friendship. Truly incredible literature.</p><blockquote><em>The hard coat that surrounds a peach pit, a sesame or mustard seed, or a walnut’s shell mostly exists to prevent this expansion. In the laboratory, we simply scratch the hard coat and add a little water and it’s enough to make almost any seed grow. I must have cracked thousands of seeds over the years, and yet the next day’s green never fails to amaze me. Something so hard can be so easy if you just have a little help. In the right place, under the right conditions, you can finally stretch out into what you’re supposed to be.</em></blockquote><h3>Dark Matter: A Novel 🚪</h3><p><em>Blake Crouch</em></p><p>Like many of the best novels, the story is not just the story. So good, I made my wife read it. It’s about the different lives you might have and how those in your life change who you are.</p><blockquote><em>If you strip away all the trappings of personality and lifestyle, what are the core components that make me me?</em></blockquote><h3>The Song Machine: Inside the Hit Factory 🎶</h3><p><em>John Seabrook</em></p><p>Do you love music? I love music. This book is an eye opening account of how Hits are made. Not just songs. Hits. Basically, a bunch of Swedish guys and their friends figured it out. The role they played in the introduction of some of today’s hitmakers is much deeper than I had originally thought. Abba, Ace of Base, N’Sync, Backstreet Boys, Britney Spears, Justin Timberlake, Kesha, Katy Perry, Rihanna all get mentions. Basically, your favorite artists had some help to make those hits.</p><blockquote><em>In the late 1940s, the record industry began to promote these groups under the label “rhythm-and-blues,” a term invented by a white Billboard writer, Jerry Wexler — later a partner in Atlantic Records — to replace the derogatory trade name “race music.” (He later regretted he hadn’t called the music “R&amp;G,” for rhythm and gospel, instead; such R&amp;B staples as falsetto singing and hand claps derived from gospel music.) R&amp;B was, as Stuart Goosman points out in his 2005 book Group Harmony, a marketing term that became a badge of black musical identity. By definition, a black group would always be labeled R&amp;B even if they sang pop.</em></blockquote><h3>Decisive: How to Make Better Choices in Life and Work ✅</h3><p><em>Chip Heath</em></p><p>Thanks to a former boss for recommending this book. This book give more tools for making good decisions than the simple list of Pros vs Cons. That’s a good tool, but it’s not the only one there is. This book gives a breakdown of other tools you can use to ensure you make the best decisions. Personally, I’ve internalized the practice of coming up with multiple options when making a decision. I haven’t run the numbers to determine if this is actually <em>working</em>, but I feel a lot more comfortable with decisions after they are made.</p><blockquote><em>If you’re willing to invest some effort in a broader search, you’ll usually find that your options are more plentiful than you initially think.</em></blockquote><h3>Factfulness: Ten Reasons We’re Wrong About the World–and Why Things Are Better Than You Think 🌍</h3><p><em>Hans Rosling</em></p><p>Bill Gates recommended this book. He liked it so much he bought a <a href="http://time.com/money/5303143/bill-gates-free-book-graduates-factfulness/">copy for every 2018 college graduate</a>. It totally changed my view of the world. Essentially, the world is no longer split into first-world and third-world countries (maybe it never was). The facts are much more complicated than that. It’s not a simple binary of “rich” vs “poor” countries or “developing” vs “established” countries. There are multiple levels of poverty. Also, much of the world is further along than you might think in many ways.</p><blockquote><em>Your most important challenge in developing a fact-based worldview is to realize that most of your firsthand experiences are from Level 4; and that your secondhand experiences are filtered through the mass media, which loves nonrepresentative extraordinary events and shuns normality. When you live on Level 4, everyone on Levels 3, 2, and 1 can look equally poor, and the word poor can lose any specific meaning. Even a person on Level 4 can appear poor: maybe the paint on their walls is peeling, or maybe they are driving a used car.</em></blockquote><h3>The Rise and Fall of D.O.D.O.: A Novel ⏰</h3><p><em>Neal Stephenson and Nicole Galland</em></p><p>I’m a big fan of Stephenson and this might be my favorite one yet. It’s got time-travel, magic, history, humor, government beauracracy and vikings. What more could you want?</p><blockquote><em>She has reverted to typical witch maneuvers of requesting impossible-to-get things (in this case myrrh from the cradle of Baby Jesus).</em></blockquote><h3>Good Strategy/Bad Strategy 💼</h3><p><em>Richard P Rumelt</em></p><p>This is the book I wanted the other strategy book (How to Think Strategically: Strategy) to be. Earlier in the year, I got a new boss and we were talking about expectations. One of his expectations was that I develop a strategy for how we build things on my team. I told him “I don’t know how to do that.” So I went and downloaded that book. It was fine, I came up with a strategy. Fast-forward to now, and I’m on a different team and trying to think about what our strategy should be moving forward. I decided to circle back to the same question. I went and borrowed this book from my <a href="https://www.sanleandro.org/depts/library/">local library</a>.</p><p>In it I learned the kernel of a good strategy, discovering power and using advantage. I learned how many so-called strategies are nothing but “fluff”. It was exactly what I needed.</p><blockquote><em>It is human nature to associate current profit with recent actions, even though it should be eveident that current plenty is the harvest of planting seasons long past.</em></blockquote><h3>Recommended 📕📘📗</h3><h3>Children of Blood and Bone (Legacy of Orisha Book 1) 💀</h3><p><em>Tomi Adeyemi</em></p><p>A young girl that once had magic journeys with friends and frenemies to reintroduce it to the world. I’ve read so much fantasy that is in the Tolkien model that seeing one told through a fake African (rather than fake British) point of view was refreshing. Also, magic being derived through spirits and ancestry was an enjoyable difference. I bought it for my niece, and you know a book must be good if you spend money on it twice.</p><blockquote><em>Tzain presses his fists to his forehead as if he could smash through his own skull. He wants to believe that playing by the monarchy’s rules will keep us safe, but nothing can protect us when those rules are rooted in hate.</em></blockquote><h3>In defense of food 🥦</h3><p><em>Michael Pollan</em></p><p>Eat food, not too much. Mostly plants. This gift from a coworker helped me lose weight without feeling shame. It talks about food in a way I hadn’t heard before and I’m grateful to have read it.</p><h3>The 48 Laws of Power 😳</h3><p><em>Robert Greene</em></p><p>I actually read this 2 or 3 times in a row. It’s a series of 48 “laws” that take anecdotes from history, or legend and explain why these laws are powerful. Reading this book felt EVIL. I felt that I was embarking in some sort of low level villainy. Obviously, I didn’t take all of them to heart. However, I now don’t share information until I need to. The law of planning ALL the way to the end has also been instructive</p><blockquote><em>If you think it important to do all the work yourself, you will never get far, and you will suffer the fate of the Balboas and Teslas of the world. Find people with the skills and creativity you lack. Either hire them, while putting your own name on top of theirs, or find a way to take their work and make it your own. Their creativity thus becomes yours, and you seem a genius to the world.</em></blockquote><h3>This Will Be My Undoing: Living at the Intersection of Black, Female, and Feminist in (White) America 🙍🏿‍♀️</h3><p><em>Morgan Jerkins</em></p><p>The stories she tells are my wife’s stories, my sisters’ stories. Someday they will be my daughter’s stories. As a Black human, I recognize the stories, but as a man, some of it was new to me. The honesty was hard to read! I went over my notes from this book and was struck at how specific it was. Books are a great way to learn about experiences different from your own, and this was a perfect example of it.</p><blockquote><em>It was not only our presence that made them mad, but our excellence.</em></blockquote><h3>How to Think Strategically: Strategy — Your Roadmap to Innovation and Results (Financial Times Series) 🤔</h3><p><em>Davide Sola</em></p><p>Really liked this, made lots of good points.</p><h3>Children of Eden: A Novel 👫</h3><p><em>Joey Graceffa</em></p><p>Fun YA type novel. Reminded me of the Divergent series. A girl explores her utopian society. But maybe things aren’t as perfect as they seem…</p><h3>Surviving Dreaded Conversations: How to Talk Through Any Difficult Situation at Work 🗣</h3><h3>Seveneves: A Novel 🌑</h3><p><em>Neal Stephenson</em></p><p>Really liked this LONG thing. Something hits the moon, and it breaks. Humans need to get off the planet because the dust generated will eventually envelope the earth and kill all life. Goes deep into Space stations and even Space travel before the final third of the book throws all reality to the side.</p><h3>The three body problem 🛸</h3><p><em>Cixin Liu</em></p><p>We’ve all read books about encounters with aliens. NOT LIKE THIS. I really loved this book because it’s told from a Chinese perspective and was different from other things I was used to.</p><h3>The dark forest ⚔️</h3><p><em>Cixin Liu</em></p><p>Sequel to the 3 body problem. Now that the central issue of the three body problem is solved, what happens next? Wall-Facers &amp; Sword-Holders.</p><h3>Death’s End 📦</h3><p><em>Cixin Liu</em></p><p>Final book in the trilogy. More Sword Holders, Dimensional Weaponry, Pocket Universes.</p><h3>Fine 📕📘</h3><h3>Surviving Dreaded Conversations: How to Talk Through Any Difficult Situation at Work</h3><p><em>Donna Flagg</em></p><p>Basically, get over it and have the tough convo.</p><h3>Crucial Conversations Tools for Talking When Stakes Are High, Second Edition 😴</h3><p><em>Kerry Patterson</em></p><p>Good, but boring</p><h3>Milk and Honey 🐝</h3><p><em>Rupi Kaur</em></p><p>My only poetry book, didn’t like it.</p><h3>The Changeling: A Novel 👶🏾</h3><p><em>Victor LaValle</em></p><p>Kind of a fantasy novel. Meh.</p><h3>Relic 🦖</h3><p><em>preston &amp; childs</em></p><p>Fun read. There’s a beast loose in the Museum of Natural History</p><h3>Mem 👯‍</h3><p><em>Bethany Morrow</em></p><p>A book about extracted memories. I think it was supposed to be deeper than what I’ve gotten out of it. I’m <em>hoping</em> it’s about how each memory is something that shapes you, but I might be reaching.</p><h3>Unfinished 📕</h3><p>Not every book is meant to be finished. I started (most) of these books, but for some reason, didn’t get to the end.</p><h3>Exactly What to Say: The Magic Words for Influence and Impact</h3><p><em>Phil M Jones</em></p><p>Say “Just Imagine”. Other stuff, probably.</p><h3>Real Food/Fake Food: Why You Don’t Know What You’re Eating and What You Can Do About It</h3><p><em>Larry Olmsted</em></p><p>The chapter on Parmegianno Reggiano changed my life. It’s really frigging good. Most food is lying about where it came from. Will finish one day</p><h3>The Signal and the Noise: Why So Many Predictions Fail-but Some Don’t</h3><p><em>Nate Silver</em></p><p>Didn’t even start</p><h3>The Design of Everyday Things: Revised and Expanded Edition</h3><p><em>Don Norman</em></p><p>Didn’t finish, but liked what I did read</p><h3>The Price of Inequality: How Today’s Divided Society Endangers Our Future</h3><p><em>Joseph E. Stiglitz</em></p><p>Never finished</p><h3>Three Parts Dead (Craft Sequence Book 1)</h3><p><em>Max Gladstone</em></p><p>Ugh. Didn’t get through the first chapter</p><h3>Never Split the Difference: Negotiating As If Your Life Depended On It</h3><p><em>Chris Voss</em></p><p>Didn’t finish, but really enjoyed it. Mirroring is cool.</p><h3>A Brief History of Seven Killings: A Novel</h3><p><em>Marlon James</em></p><p>Didn’t finish 3 chapters. I didn’t like the vernacular used, it was too hard to read.</p><h3>Feel Free: Essays</h3><p><em>Zadie Smith</em></p><p>Didn’t read all the essays, but the one on libraries was beautiful.</p><h3>Leonardo da Vinci</h3><p><em>Walter Isaacson</em></p><p>Pretty boring actually. Gave up</p><h3>Hunger: A Memoir of (My) Body</h3><p><em>Roxane Gay</em></p><p>TOO tough to read. Gave up.</p><h3>The Terror: A Novel</h3><p><em>Dan Simmons</em></p><p>Kinda boring. It’s about a boat.</p><h3>Barracoon: The Story of the Last “Black Cargo”</h3><p><em>Zora Neale Hurston</em></p><p>Borrowed from library, so I didn’t finish, but it was eye-opening to hear one of the last slaves from Africa tell his story</p><h3>Beautiful Bodies</h3><p><em>Kimberly Rae Miller</em> Was this me? My wife probably bough this</p><h3>I Am Number Four (Lorien Legacies Book 1)</h3><p><em>Pittacus Lore</em></p><p>Never read it, but I did like the movie</p><h3>Storytelling with Data: A Data Visualization Guide for Business Professionals</h3><p><em>Cole Nussbaumer Knaflic</em></p><p>Read a few chapters, this was for looking good on my desk. It does look good on my desk</p><h3>Whisper Me This: A Novel</h3><p><em>Kerry Anne King</em></p><p>Starting to read, it needs to pick up, or i’ll move on.</p><h3>Star Wars: Guardians of the Whills (Star Wars: Rogue One)</h3><p><em>Greg Rucka</em></p><p>Barely read. I like Greg Rucka (go read Lazarus), I like the characters from the Rogue One movie. Somehow, I can’t get myself to care.</p><h3>Battle Angel Alita Vol. 1</h3><p><em>Yukito Kishiro</em></p><p>Really weird, I did not finish. This guy makes a robot and goes killing something(?) No thanks.</p><h3>Managing Humans: Biting and Humorous Tales of a Software Engineering Manager</h3><p><em>Michael Lopp</em></p><p>Lopp’s sell call brought me to the Bay Area. His book is honest and true. Will finish someday</p><h3>The Undoing Project: A Friendship That Changed Our Minds</h3><p><em>Michael Lewis</em></p><p>Couldn’t finish. Amos Tversky and Daniel Kahneman are dope. They apparently created Behavioral Economics (which I love). My library loan ended and I didn’t renew.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c70e015605be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Win at Technical Interviews]]></title>
            <link>https://medium.com/dev-color/how-to-win-at-technical-interviews-1fe2384d6eda?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/1fe2384d6eda</guid>
            <category><![CDATA[personal-development]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Sat, 19 Nov 2016 16:42:07 GMT</pubDate>
            <atom:updated>2017-06-07T18:51:00.920Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/876/1*CndJTHht2yxIkq2KeSl_ig.jpeg" /><figcaption>The Dorland Company</figcaption></figure><p>For many, Technical Interviews are the gate preventing access to software jobs at great companies. Getting past them is a sort of tribal knowledge of those in the know. I aim to give you the key. 🔑</p><p>By now, you might have heard about how <a href="https://medium.com/@Code2040/real-talk-the-technical-interview-is-broken-b84b8375dccb#.bz31u5rn4">technical interviews are broken</a>, and how they are <a href="http://www.thedailybeast.com/articles/2013/06/20/even-google-doesn-t-do-interviews-better.html">not necessarily good predictors</a> of who ends up being a good employee. Interviews often focus on things that are less relevant to the day to day task of being an engineer, and certainly not the parts of engineering that engineers pride themselves in being good at.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/450/1*uvjYiFcGEjOKuK4FrcKdeg.gif" /></figure><p>Smart companies are starting to recognize this dissonance and switch things up. For instance, Google no longer asks ridiculous puzzle questions. One of the reasons I joined Pinterest was because they had the courage to ask me to solve problems that were similar to the ones I would be asked to solve while working at the job.</p><p><strong>But we are not there yet.</strong> Most job seekers are going to have to interview at a few places that are still doing “old school” technical interviews. Until they become enlightened, or an improved system arises, it’s best to face reality head on and prepare.</p><p>Once, when I was fresh out of college with my brand new Computer Science degree, I got an interview with Amazon. But it was different than any interview I had ever been on. They were going to <em>call</em> me. On the phone. “That’s new”, I thought. They gave me a call and began to ask me about programming concepts I knew about, but hadn’t looked at since my CS 141 class at UC Riverside. Needless to say, I did not do well on the interview. When I hung up, I sat on my bed and thought “Was I supposed to <em>prepare</em> for this interview?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*evIiG9KASdeMa-oPNZ3m8w.gif" /></figure><h4>Preparing for the interview</h4><p>You’ve gotten a call back, or an email reply with a company you’ve applied to. Great, now what? Now it’s time to get ready. One of the things you can ask is “What should I wear?” It sounds silly, but if you show up to the interview with a 3 piece suit on, while everyone else is in a t-shirt and flip-flops, you won’t be able to focus on the task at hand, because you’ll feel out of place. It’s important that you allow yourself to be as comfortable as possible, because the process of interviewing is stressful.</p><p>Another thing you can do is ask the recruiter who will be interviewing you. You might want to do a little research on them, just so you are not surprised at who comes in to speak with you.</p><p>You should also take another look at the job listing, to make sure you fully understand what they are looking for and can practice any parts that you feel less confident with.</p><h4>What to Expect</h4><p>If you are interviewing for a position as a Software Engineer, you’ll be expected to write code. You’ll be expected to talk about code, and pros and cons of different techniques. You’ll need to remember your data structures and algorithms. If you are a more experienced engineer, you should be able to do some architecture, and design a large scale system. Depending on the role, you might be expected to answer questions related to computer science theory or testing.</p><p>These interviews typically take a full day, even including lunch. You are likely to have several session of 45 minutes to an hour long with one or more interviewers asking you questions. I’ve heard it said to take every break they offer you, so you can stay calm and get a break from the stress of the process.</p><h4>Practice</h4><p>Practice is the only way to handle this. Just as asking about dress code is an effort to relax you, practicing the sorts of questions you’ll get is the most effective way to become comfortable with answering them. I’ve added some reading material at the bottom of this post.</p><h3>UAA on Twitter</h3><p>Don&#39;t go through practice, grow through practice. #IWILL</p><p>Before my last job search, I had been at my previous company for over 7 years. I was wildly out of practice when it came to interviews. So I had to set apart 3 weeks and practice. Every night for 2 hours, I got to work.</p><p><strong>I read. I wrote code. I memorized.</strong></p><p>It felt odd, needing to spend so much time preparing to get a job that I was already qualified for. But the interview is NOT the job. It’s a completely distinct thing. In fact, it’s a lot more like the SAT, in that it’s not a measure of how smart you are or how good of a software engineer you are, it’s a measure of how well you take the test. For most software engineers, their everyday job doesn’t entail tree traversal or recreating regex (2 real questions I got when I interviewed at Google). It involves <strong>making</strong> things, and improving performance and shipping code. Until the industry finds a way to discover who is good at that, we are left with the existing technical interview. That’s ok. We just need to prepare for it, so we can come out on top.</p><h4>Put your keyboard away</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*5TbHT59u2lBScyewuVJmxg.gif" /><figcaption><a href="https://www.youtube.com/watch?v=aClxtDcdpsQ">https://www.youtube.com/watch?v=aClxtDcdpsQ</a></figcaption></figure><p>One of the many ways that the typical technical interview is unlike the technical job is that you are asked to write code, but not on a keyboard. I already mentioned my phone interview. Get a friend to call you and ask you a question.</p><p>You also sometimes get asked to write on a whiteboard. Find a whiteboard and write out a simple function. A nice thing about the whiteboard, is that you can use all of the space to write down little “notes”, such as expected output and input or helper functions.</p><p>You might end up writing code in a Google Doc, with no syntax highlighting. Sometimes, you might get a good interviewer who will have <a href="https://codepen.io/">Codepen</a> (or something like it) setup, but you need to be prepared just in case. Learn how Codepen works so you don’t waste time during your interview getting used to it.</p><p>You should also make sure you are having a dialogue with your interviewer. You can ask questions about what languages they want you to write in. In general, smaller places prefer candidates write code in their language, and larger places will let you pick. Choose carefully. Not every language is great for interviews. Choose one you are most familiar with.</p><h4>Understand the question</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/290/1*XZQFq89Lpy9ehRc68-SbMg.gif" /><figcaption>Family Matters</figcaption></figure><p>Don’t start writing before you understand the question. Too many times, an interviewee begins solving a problem, that isn’t the problem they’ve been asked to solve. It’s like buzzing in before the question is finished on Jeopardy. Wait. Listen, and <em>then</em> ask questions to clarify the question. Questions about expected input and output are always helpful. State your assumptions. This is a little bit like elementary school math, where it’s better if you show your work and how you got to a place. An interview isn’t only a time for an employer to find out whether you can write code, but find out how you think.</p><p>Don’t be too clever, straightforward is ok for the first time you answer the question. A common technique that interviewers use is to ask a question, and then ask about space constraints, or speed constraints. If this happens, now you can get clever by searching from both the right and left at the same time or something like that.</p><h4>Data Structures and Algorithms</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*Brqji620cxibWAwNBm5Jxw.gif" /><figcaption><a href="https://www.youtube.com/watch?v=qybUFnY7Y8w">https://www.youtube.com/watch?v=qybUFnY7Y8w</a></figcaption></figure><p>This is the crux of it. This is what you need to review (or learn for the first time) in order to do well on these interviews. Here are some data structures that it helps to know about.</p><ul><li>Arrays or Lists (obviously)</li><li>Maps or Hash Tables or Dictionaries</li><li>Sets</li><li>Graphs, Heaps</li><li>Binary Search Tree</li><li>Stacks &amp; Queues</li></ul><p>Here are some algorithms it’s helpful to know.</p><ul><li>Sorting algorithms (quicksort or mergesort)</li><li>Tree Traversal</li><li>Recursion</li><li>Binary Search</li></ul><h4>Big O Notation</h4><p>It’s good to memorize the Big O of things. If you don’t remember, Big O notation is a way to describe the time complexity of a function in the worst case. For instance, finding an item in an array is O(n), but finding it in a Hash table is O(1). Going through 1 loop of items is O(n) but if there is a nested loop, it would be increased to O(n²)</p><p>A really helpful site for this is <a href="http://bigocheatsheet.com/">Big O Cheatsheet</a>.</p><h4>Testing</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*fyT-Z4krpbJyLKQJdaufOA.gif" /><figcaption><a href="https://www.youtube.com/watch?v=E2evC2xTNWg">https://www.youtube.com/watch?v=E2evC2xTNWg</a></figcaption></figure><p>You would never write code and commit it without testing it. Similarly, you should always run through your code at least a few times to make sure it works in the way you intend to. Make sure to do the happy path, but the bad path too. One way to do this is to take note of “bad” inputs, such as <em>null</em>, or -1 if you are dealing with integers. It’s easy to go overboard with this so make it a conversation with your interviewer as you go through the code out loud.</p><h4>Architecture</h4><p>More experienced engineers are often asked questions about software architecture or system designs. Things like “how would you create a system to send messages back and forth to users” or something broad like that. When discussing your answer for this, make sure you analyze the trade-offs of size/cost/latency/etc as you make decisions. Consider the scale of the question, and take a look at the numbers. Don’t worry if you don’t finish, this is usually an open ended question.</p><h4>Other types of questions</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*cfoyISiO2gywcg2A4vqIUg.gif" /><figcaption>Jimmy Kimmel Live</figcaption></figure><p>You should also be prepared to answer questions about things outside of coding, such as:</p><ul><li>Why do you want to work at this company? <em>Prepare for this by doing research on the company first.</em></li><li>Biggest/Best project you worked on? <em>Have a story ready that paints you in the best light and showcases your skills.</em></li><li>Where do you see your career going? <em>Be honest about what you want. If it’s not a place you can see yourself growing, it’s not worth your time.</em></li></ul><h4>Questions for the interviewer</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*ndaVfeKyG_J8qT0HCkuTdA.gif" /><figcaption>Curb Your Enthusiasm</figcaption></figure><p>When the time comes to ask your interviewer questions, have some ready!? There is nothing stranger than sitting there awkwardly after the technical questions have been asked. An easy one is asking the interviewer about their work at the company. People love talking about themselves, and you should be able to gain an understanding of a typical work day in the organization. Here are some other questions to ask:</p><ul><li>What is unique about this company?</li><li>How often do you ship code?</li><li>What would my role be?</li><li>Describe the culture</li><li>Is there anything you are trying to change in the company?</li><li>What is the work/life balance like? or What are typical hours?</li></ul><p>Hopefully this has been helpful. Good luck!</p><h3>Reading Material</h3><p>Glassdoor — <a href="https://www.glassdoor.com/Interview/Google-Interview-Questions-E9079.htm">https://www.glassdoor.com/Interview/Google-Interview-Questions-E9079.htm</a></p><p>Khan Academy — <a href="https://www.khanacademy.org/computing/computer-science/algorithms">https://www.khanacademy.org/computing/computer-science/algorithms</a></p><p>Cracking the Coding Interview — <a href="https://www.amazon.com/gp/product/0984782850/ref=pd_sbs_14_t_0?ie=UTF8&amp;psc=1&amp;refRID=TFM33FC66DHFMG2BF3S2">https://www.amazon.com/gp/product/0984782850/ref=pd_sbs_14_t_0?ie=UTF8&amp;psc=1&amp;refRID=TFM33FC66DHFMG2BF3S2</a></p><p>Coursera — <a href="https://www.coursera.org/learn/cs-tech-interview">https://www.coursera.org/learn/cs-tech-interview</a></p><p>CoderByte — <a href="https://coderbyte.com/challenges/?a=true">https://coderbyte.com/challenges/?a=true</a></p><p><em>This was written with lots of insights from Cynthia Lee of Stanford, Eric Yurko and Antoine Picard of Google, Jayson P Phillips of Pandora and Devaris P Brown of Floodgate Academy. My thoughts are my own.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1fe2384d6eda" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dev-color/how-to-win-at-technical-interviews-1fe2384d6eda">How to Win at Technical Interviews</a> was originally published in <a href="https://medium.com/dev-color">The Compiler</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Me and Your Mama — a stream of consciousness review]]></title>
            <link>https://medium.com/@thekaanon/me-and-your-mama-a-stream-of-consciousness-review-9d0c1693f12a?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d0c1693f12a</guid>
            <category><![CDATA[music]]></category>
            <category><![CDATA[music-review]]></category>
            <category><![CDATA[stream-of-consciousness]]></category>
            <category><![CDATA[childish-gambino]]></category>
            <category><![CDATA[hip-hop]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Tue, 15 Nov 2016 22:50:28 GMT</pubDate>
            <atom:updated>2016-11-15T22:51:10.567Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0MAXCUjW_AYccGVfeMhhxw.jpeg" /></figure><ul><li>What is this?</li><li>This doesn’t sound like a rap song?</li><li>It’s kinda beautiful, tho</li><li>Oh snap, the beats about to drop.</li><li>Come on, beat, drop.</li><li>The beat dropped.</li><li>This is not what I expected to hear when the beat dropped.</li><li>“Let me innnnn, to your heart” Ok, i can work with this.</li><li>This is like some primal, loving screaming. I love this.</li><li>Donald Glover is on some other stuff, honestly.</li><li>That falsetto, tho.</li><li>I can’t help thinking he’s singing about Van.</li><li>Or maybe Jhene Aiko, i dunno.</li><li>More songs need proper screams.</li><li>“Oh my god”</li><li>I need to see this live. I want to feel this vibe.</li><li>Oh, it’s slowing down now.</li><li>Is that a tambourine….. Heat check.</li><li>Ambient noises now, a cool down from the screaming.</li><li>Can this song last forever, plz?</li><li>What kind of instrument is that?</li><li>I feel calm for some reason.</li><li>I’m just gonna listen to this all day, now.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d0c1693f12a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’ve been so naive.]]></title>
            <link>https://medium.com/@thekaanon/ive-been-so-naive-77d7bac5e367?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/77d7bac5e367</guid>
            <category><![CDATA[woke]]></category>
            <category><![CDATA[2016-election]]></category>
            <category><![CDATA[politics]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Wed, 09 Nov 2016 16:27:38 GMT</pubDate>
            <atom:updated>2016-11-19T21:26:07.071Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1NsSQ3LYix89WErA9KpvQQ.jpeg" /></figure><p>I thought Americans really wanted to move past racism and hatred of outsiders.</p><p>I thought Americans could recognize an idiot and a liar.</p><p>I thought common sense would prevail.</p><p>I thought we were smarter than this.</p><p>Apparently, I am wrong. Fully half of the country chose this candidate. Christians chose pro-life over <em>basically everything else in the Bible. </em>Poor people<em> </em>choose the billionaire who <em>doesn’t pay taxes</em>. Rich people <em>really</em> wanted that tax cut. Women voted for a man who doesn’t respect them. Republicans choose their <em>team</em> over their actual policies.</p><p>People said “ok” to the man who would ban an entire religion. So much for religious freedom.</p><p>People said “ok” to a man dumb enough to think a wall can stop immigration. We can fly now, Donald.</p><p>People said “no” to a career politician with years of experience and empathy for humans and actual policy positions. Because, emails.</p><p>We chose to blow it all up. Even though <a href="http://data.bls.gov/timeseries/LNS14000000">unemployment is down</a>. Even though the market is high. Even though <a href="http://fortune.com/2016/03/10/president-obama-approval-rating/">Barack Obama has a higher approval rating than George W Bush</a>.</p><p>But this is the country of slavery. Then segregation, then lynching, then the KKK. <a href="http://www.theatlantic.com/magazine/archive/2014/06/the-case-for-reparations/361631/">Redlining in housing discrimination</a>. Mandatory minimum sentencing. Three strikes. <a href="http://qz.com/806498/food-service-group-funds-group-opposing-marijuana-legalization-effort/">Prison industrial complex fueling a war on drugs</a>. <a href="http://www.history.com/topics/world-war-ii/japanese-american-relocation">Internment camps</a> for the Japanese. <a href="http://www.slate.com/articles/news_and_politics/politics/2014/03/andrew_jackson_should_be_kicked_off_the_20_bill_he_ordered_a_genocide.html">Genocide for Natives</a>. We are the only ones who have ever actually used a nuclear bomb. We have the most prisoners. The most gun violence. The place where only those with money can have health care. We watch children play football even though <a href="http://mobile.nytimes.com/2016/02/04/sports/football/ken-stabler-nfl-cte-brain-disease.html?smid=tw-nytimes&amp;smtyp=cur&amp;_r=1&amp;referer=">grown men are dying from it</a>. We hate the media, even when they tell the truth. We ignore climate change, even as our <a href="https://weather.com/science/environment/news/great-salt-lake-drying-up">lakes are drying up</a>. We hate experts and praise winning at all costs. America is a land of violent, anti-intellectual, anti-other people who chose a man just like them as President.</p><p>It’s been there the whole time. I was just naive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=77d7bac5e367" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There is more than one problem in the world.]]></title>
            <link>https://medium.com/@thekaanon/there-is-more-than-one-problem-in-the-world-c39f22698e8f?source=rss-a4d31c5abf99------2</link>
            <guid isPermaLink="false">https://medium.com/p/c39f22698e8f</guid>
            <category><![CDATA[social-justice]]></category>
            <category><![CDATA[blacklivesmatter]]></category>
            <category><![CDATA[civil-discourse]]></category>
            <category><![CDATA[politics]]></category>
            <category><![CDATA[racism]]></category>
            <dc:creator><![CDATA[Kaanon MacFarlane]]></dc:creator>
            <pubDate>Fri, 15 Jul 2016 06:37:24 GMT</pubDate>
            <atom:updated>2016-07-15T08:43:40.630Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/840/1*m6NQUAtSI8o7zEOKGEO-_w.png" /><figcaption>chainsawsuit.com illustration</figcaption></figure><p>There was a great <a href="https://theringer.com/the-isolation-of-being-black-in-tech-2cc3977b7357#.e9794nidk">article</a> about loneliness in tech for Black folks. The first comment was about hiring. Important, but not related.</p><p>I read <a href="https://medium.com/@KatieS/an-open-letter-from-technology-sector-leaders-on-donald-trumps-candidacy-for-president-5bf734c159e4#.m7am0dp0q">one</a> about how tech leaders think Donald Trump is bad for innovation. First comment prompted to “hire more women and people of color”. True, but, again, not related.</p><p>It’s the same with Black Lives Matter. <em>Of course</em>, all lives matter, we’re just talking about our own right now. No one else will.</p><p><strong>I’m sick of seeing comments and responses that aren’t related to the topic at hand.</strong></p><p>The rents too damn high and we’re still at war (I think?) and the BART’s too slow and student loans are out of control and trucks are running into people in Nice, and we need more diversity in tech, and we need a competent president, pretty please, and immigration reform should happen, and there are still only 8 justices on the Supreme Court and Black people are getting killed by cops, and. And. And. And. And.</p><h4>When someone wants to discuss an issue, the fact that there are other issues should not discount the issue at hand.</h4><p>Black on Black violence does not mean we can’t talk about Blue on Black violence. The lack of X doesn’t mean that the lack of Y isn’t worth a conversation. Poor performance in one area by a company, person, group of people doesn’t mean their opinion on every subject is discounted.</p><p>Don’t get angry at people who point out an issue by referring to a separate issue. Instead, try to listen.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c39f22698e8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>