<?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 Rushi Luhar on Medium]]></title>
        <description><![CDATA[Stories by Rushi Luhar on Medium]]></description>
        <link>https://medium.com/@rushi-luhar?source=rss-5802d247f2ad------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*baBpKQZ77jeS-fY0-VDWIQ.png</url>
            <title>Stories by Rushi Luhar on Medium</title>
            <link>https://medium.com/@rushi-luhar?source=rss-5802d247f2ad------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 03:37:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rushi-luhar/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[Mostly Harmless — No More..]]></title>
            <link>https://rushi-luhar.medium.com/mostly-harmless-no-more-72e190d3b7e4?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/72e190d3b7e4</guid>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 21:11:39 GMT</pubDate>
            <atom:updated>2026-04-21T21:11:39.910Z</atom:updated>
            <content:encoded><![CDATA[<p>I have moved my writing to my blog — which you can find <a href="https://thinking.luhar.org/">here</a> and the occasional post on Substack — which you can find <a href="https://theforge.substack.com/">here</a>. You will see me pop up here on Medium as I will write on Jeavio’s Engineering Blog, but otherwise see you around!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=72e190d3b7e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mikel Arteta — A Case Study in Radical Candor]]></title>
            <link>https://medium.com/mostly-harmless/mikel-arteta-a-case-study-in-radical-candor-a6efe84bc453?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6efe84bc453</guid>
            <category><![CDATA[arsenal]]></category>
            <category><![CDATA[radical-candor]]></category>
            <category><![CDATA[high-performance-team]]></category>
            <category><![CDATA[people-management]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Mon, 29 Aug 2022 18:24:43 GMT</pubDate>
            <atom:updated>2022-08-29T18:26:17.951Z</atom:updated>
            <content:encoded><![CDATA[<h3>Mikel Arteta — A Case Study in Radical Candor</h3><h3>Introduction — All or Nothing</h3><p>Managing and supporting a team is a difficult job. A manager is often a coach, disciplinarian, a surrogate parent, and cheerleader — all rolled into one. I am always on the lookout for ways to be a better supporter of my teams. Over the last few days I discovered a fortunate intersection in my interests in sport and in management.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*-Qg8E4tKVUkPbJG7-2KMiw.jpeg" /><figcaption>All or Nothing: Arsenal is a 2022 Sports Documentary Series on Amazon Prime</figcaption></figure><p>I am a fan of the Arsenal football club. Like many other Arsenal fans, I have been watching and enjoying the Amazon Prime show “All or Nothing: Arsenal,” which follows Arsenal through the 2021–2022 season. We get a close look at how Arsenal’s manager Mike Arteta works with his players and his management team and motivates them over a challenging 45-game season.</p><p>At 38 years old, Arteta is currently the youngest manager in the English Premier league. He has been at the helm since 2019. The Arsenal squad also has the youngest average age in the Premier League — this season, the first team averages just 25.2 years old.</p><p>Arteta’s reign has seen the club slump to 8th place in the 2019 and 2020 seasons before having a marked improvement in form to finish 5th in 2021.</p><p>Arteta comes across as an intense, detail-oriented and hands-on manager. I realized that Arteta’s approach to management was something I had come across before. It is strikingly similar to that described in Radical Candor by Kim Scott — one of my favorite books on building high-performance teams.</p><p>In this post, I will summarize the Radical Candor approach through the lens of Arteta’s unique take on people management.</p><h3>What is Radical Candor?</h3><p><a href="http://radicalcandor.com/">Radical Candor</a> is a book by <a href="https://twitter.com/kimballscott?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor">Kim Scott</a> published in 2017. It focuses on <strong>creating a culture of guidance, building an effective and cohesive team, and driving results collaboratively.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ZeftkBg2tcQKnGdoO8QIg.jpeg" /><figcaption>Radical Candor is a 2017 book by Kim Scott</figcaption></figure><p>The book’s central thesis is that <strong>effective leadership requires direct, clear, truthful, and kind feedback, </strong>even when difficult. Scott believes getting to know each person in your team personally is essential to understanding their desires and motivations.</p><p>The book offers tactical and strategic advice to leaders on building high-performing teams in an open, healthy, and productive environment. I strongly recommend Radical Candor for those looking for an <strong>authentic and modern approach to people management</strong>.</p><p>We see Arteta speaking candidly and passionately with his players throughout the season. He is generous in his feedback when things go well. When things go poorly, Arteta is <strong>direct, passionate, and emotional</strong>. While he doesn’t mince words, he doesn’t humiliate his players in the dressing room or in front of the media.</p><h3>Caring Personally while Challenging Directly</h3><p>The 2X2 below shows “Radical Candor” as giving feedback by caring personally while challenging directly. It also covers some dysfunctional ways of giving feedback — obnoxious aggression, ruinous empathy, and manipulative insincerity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*14d4twbWY4uEScCbQj_9bw.png" /><figcaption>2X2 Taken from Radical Candor by Kim Scott</figcaption></figure><p>Ted Lasso aside, football managers are not known for their <strong>empathy</strong>. Indeed, the likes of Sir Alex Ferguson are revered for their ability to drive performance through aggression and intimidation. Ferguson’s proverbial “hairdryer treatment” would probably end up in the “Obnoxious Aggression” quadrant above.</p><p>While he is partial to the odd F-bomb, Arteta’s <strong>open displays of emotion and vulnerability</strong> inspire his players, as seen in <a href="https://youtu.be/13dSuAfhEds">this clip</a>. At the end of a run of poor results in April at Crystal Palace and Brighton, we see a manager who cares about the results and is <strong>passionate</strong> about wanting to make things better. He calls out a lack of <strong>intensity</strong> from his players and gives specific feedback on the training pitch and in the dressing room.</p><p>This combination of <strong>caring personally and directly challenging poor performance</strong> is right out of the Radical Candor playbook.</p><h3>Building Resilience Through Trust</h3><p>The Radical Candor approach is <strong>built on a foundation of trust</strong>. Trust is difficult to gain and easy to lose. The key to building trust is to be <strong>transparent and authentic, clear and concise in communication, and consistent in your actions.</strong></p><p>Arteta calls out his “<a href="https://www.bbc.com/sport/articles/c6yp3lv65zeo">non-negotiables</a>” in explaining his management philosophy: <strong>respect, commitment, and passion</strong>. Throughout the show, we see Arteta embodying these values.</p><p>This results in significant friction with his star player Pierre-Emerick Aubameyang who does not meet Arteta’s high expectations around discipline and accountability. Aubameyang is the club captain and is a popular member of the squad.</p><p>Arteta ends up stripping Aubameyang from the captaincy of the team. This could have destabilized the team, but it seems to have the opposite effect. Arteta does not criticize Aubameyang, and his team is made aware of how important trust and <strong>accountability</strong> are to their manager. By showing <strong>consistency in his actions</strong> and <strong>clarity in his communication</strong>, Arteta builds trust and <strong>resilience</strong>, resulting in outstanding results on the pitch in the second half of the season.</p><h3>Managing Rockstars and Superstars</h3><p>In Radical Candor, Scott describes Rockstars as stable employees who are happy and effective in their roles. These are folks who are aware of their talents and limitations and can <strong>consistently perform</strong> at a high level. On the other hand, Superstars are on a steep career trajectory and can be <strong>change agents</strong>. They are ambitious and want new opportunities. A high-performing team usually has both rockstars and superstars.</p><p>Given his young team, Arteta works with plenty of players on steep growth trajectories. Bukayo Saka, Emile Smith Rowe, and Eddie Nketiah are all young and eager to learn and perform at the highest level. However, he also has players like Rob Holding and Mohammad Elneny. While experienced pros, they have specific roles and are not guaranteed a place in the starting lineup. Holding and Elneny are the rocks (and Rockstars) that provide a stabilizing influence in the dressing room and on the pitch while laying a foundation for the more flamboyant players up front.</p><p>As a manager, Arteta has to ensure that the players like Holding and Elneny <strong>feel valued</strong> and are ready to perform when called upon while the ambition and talents of the young Gooners are nurtured. You can see this come together towards the end of the season. Holding and Elneny perform well after being called into the starting eleven after injuries. He also gives the ambitious Nketiah an extended run. He repays his faith by scoring five goals in the last seven games.<br>Arteta and his team need to understand each player’s <strong>mentality</strong> and ensure they feel <strong>motivated</strong> to <strong>perform</strong> when needed.</p><h3>Conclusion</h3><p>All or Nothing is entertainment and has been edited to push a narrative and maximize engagement. Mikel Arteta has come under intense criticism for being uncompromising and stubborn at times — especially with how he has managed high-profile players like Aubameyang and Mesut Ozil. But, the little glimpse we get in the documentary shows a young manager trying to build a successful team.</p><p>Plenty of books like Radical Candor have come out of Silicon Valley, and the content often reflects the author’s experience working in technology companies. The strength of a book, especially in the crowded management genre, is <strong>how applicable the message is across different domains.</strong></p><p>Managing Arsenal presents quite different challenges from managing a software engineering team. However, I hope the lessons of Radical Candor and All or Nothing are valuable to managers looking to build and support a high-performance team.</p><h3>Further Reading</h3><p>From my blog:</p><ul><li>George Saunders on<a href="https://rushi.luhar.org/blog/2022/07/george-saunders-on-feedback/"> giving feedback</a></li><li>Check out my <a href="https://theforge.substack.com/">newsletter</a></li><li>I cover technology, AI, people management, and books on my <a href="https://rushi.luhar.org/blog">blog</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6efe84bc453" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/mikel-arteta-a-case-study-in-radical-candor-a6efe84bc453">Mikel Arteta — A Case Study in Radical Candor</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[On Modern Web Development]]></title>
            <link>https://rushi-luhar.medium.com/on-modern-web-development-48e6df5aca1?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/48e6df5aca1</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[complexity]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Fri, 28 May 2021 13:46:38 GMT</pubDate>
            <atom:updated>2021-05-28T13:46:38.522Z</atom:updated>
            <content:encoded><![CDATA[<p>Tom MacWright wrote a <a href="https://news.ycombinator.com/item?id=23136688">much discussed</a> <a href="https://macwright.com/2020/05/10/spa-fatigue.html">article</a> on the state of modern web development a couple of weeks ago.</p><p>He states that the current default of building a Web Application as a SPA using React, or something similar, in the frontend and an API on the backend is overkill.</p><p>This is both an opinionated survey on the current state of web development and an extremely contrarian take on current accepted wisdom on how to build modern web applications. It’s worth a read.</p><p>His premise is that we are adding additional levels of abstraction such as Virtual DOMs, Server Side Rendering, Bundle Splitting, etc. He even goes on to say that trying to generic, purely REST-ful APIs is a bit like tilting at windmills, since we end up having them tightly coupled with frontend code anyway.</p><p>I am sympathetic to this point of view — mainly because I am rapidly transiting to “grumpy old man” phase of my career, and I find modern web development workflow terrifying complex. I had to work on a React application a couple of years ago. It made me want to run back into the warm embrace of Java Swing development (oh beautiful Java Swing).</p><figure><img alt="Gratuitous screenshot of a Java Swing UI" src="https://cdn-images-1.medium.com/max/644/1*M1HUKz6fthU2Gx_Tb2_nfw.png" /><figcaption>Java Swing — When men were men and UIs were UIs.</figcaption></figure><p>But, I also want to note that software engineering is pretty fashion driven where we bounce around between too much and too little abstraction. Every generation has this battle — Java didn’t have enough features so we ended up with Java EE, Java EE was too bloated so we ended up with Swing, the Java language was too complex so we built Go. Go is missing Generics so we will go ahead and add them. The pendulum keeps swinging and we have a complexity crusade every 5–7 years or so. Unsurprisingly, it has been just about 5 years since React has become the defacto way of building web applications. Time for the backlash!</p><p>I am sure we are going to be back at folks writing pure HTML and FTP-ing to an Apache server day now ;-)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=48e6df5aca1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Psychology of Money — Morgan Housel]]></title>
            <link>https://medium.com/mostly-harmless/the-psychology-of-money-morgan-housel-d4892e39add3?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/d4892e39add3</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[money]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[review]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Mon, 15 Mar 2021 01:30:44 GMT</pubDate>
            <atom:updated>2021-03-15T01:32:19.889Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Psychology of Money — Morgan Housel</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qNVP1wnUeu52luTHjVUxiA.jpeg" /></figure><p>I read Morgan Housel’s “The Psychology of Money” towards the end of last year. I found it an insightful book that took a more personal and nuanced look at money and building wealth. It is not a “how to get rich quick book.” <br>Its core advice is to take advantage of compounding and take a reasonable approach to risk — hardly rocket science. However, it explores some of the more common pitfalls and anti-patterns when people think of money. <br>While I would strongly recommend everyone to read the book — it is fantastic, here is a quick summary of my notes from reading (and enjoying) the book. I hope you find it helpful!</p><h3>A more personal view of money</h3><p>People think of money as an abstract. We think about and are taught about money like we are taught physics. We assume that money is governed by rules and laws. Yet, psychology, with its study of emotions and nuance, may offer a better way to think about money.</p><p>Most people make financial decisions by taking the information that they have access to and plugging it into their mental model of how the world works. But these mental models are driven profoundly by personal experience.</p><p>Mr. Housel’s book takes a personal and intimate approach to understand how money works and illuminates some of the difficulties we face when making money decisions.</p><h3>How to get rich and stay rich</h3><p>Compound growth is the key to growing wealth. There is plenty of material available that describes viable strategies for becoming wealthy. However, Mr. Housel states that there is only one way to stay wealthy — “some combination of frugality and paranoia.”</p><p>If one can stick around for a long time without wiping out or being forced to give up, the power of compounding comes into play and helps generate wealth.</p><p><strong>The key to a successful investment strategy is to not risk what you have and need for what you don’t have and don’t need.</strong></p><h3>The importance of sensible optimism</h3><p>Successful investors take an optimistic view that, in the long run, the odds are in their favor, and over time things will balance out to a good outcome even if what happens in between is filled with misery.</p><p>But the optimism must be balanced with a healthy dose of paranoia. This means accepting nuance and understanding that the key to exploiting long-term optimism is survival.</p><p>It is critical not to get swept up in short-term momentum or get giddy about short-term gains or losses. <strong>The most effective long-term strategy is to not get overly influenced by short-term events.</strong></p><h3>Understanding wealth</h3><p>When most people think about becoming a millionaire, they think of the ability to spend a million dollars. However, the true meaning of wealth is the ability to deploy money towards living a life that lets you do what you want, when you want, with who you want, where you want, for as long as you want. So, <strong>true wealth is financial assets that haven’t yet been converted into consumption.</strong></p><p>The ability to save is also critical to building wealth. Savings are a hedge against life’s inevitable ability to surprise the hell out of you at the worst possible moment. The most potent way of increasing savings is not to raise your income but to raise your humility.</p><h3>Making reasonable financial decisions</h3><p>Financial decisions making is thought of as making coldly rational decisions in the light of available information and knowledge of the past. However, history is primarily the study of unanticipated events.</p><p>Therefore, relying on history as an unassailable guide to the future is risky. It is important to consider the past but to look at it in terms of generalities.</p><p>So, one must not be overly influenced by history and take a reasonable and pragmatic approach when making financial decisions. Having savings gives a buffer to absorb short-term volatility. Having a realistic and flexible approach to financial decisions makes it likely to stick with your investment strategy in the long run.</p><h3>The role of skill and of luck</h3><p>Money constantly changes returns. If an asset has momentum, a group of short-term traders will assume it will keep moving up. We have seen this play out in recent times with the GameStop saga.</p><p>It is not an unreasonable strategy for the short term. Executing such short term strategy doesn’t really require much skill but does need some luck in timing the strategy just right. Plenty of traders both lost and made huge amounts of money trying to time their GameStop trade. It was all about momentum.</p><p>The mistake we are susceptible to is focusing solely on what we want to do and have the ability to do. We ignore the plans and skills of others whose decisions might affect our outcomes. We also focus too much on the causal role of skill and neglect the role of luck. This makes us overly confident in our beliefs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d4892e39add3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/the-psychology-of-money-morgan-housel-d4892e39add3">The Psychology of Money — Morgan Housel</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Less Certainity, More Enquiry]]></title>
            <link>https://medium.com/mostly-harmless/less-certainity-more-enquiry-25c5995da1e0?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/25c5995da1e0</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[poker]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[mindfulness]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Wed, 30 Dec 2020 21:29:50 GMT</pubDate>
            <atom:updated>2020-12-30T21:35:35.513Z</atom:updated>
            <content:encoded><![CDATA[<h3>Less Certainty, More Enquiry</h3><h3>Lessons from Maria Konnikova’s The Biggest Bluff: How I Learned to Pay Attention, Master Myself and Win</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/1*myDqebDSFzSr-RJRherDTw.jpeg" /></figure><p>Maria Konnikova is a journalist, writer, and professional poker player. I came across her an interview with her on the excellent <a href="https://fs.blog/knowledge-project/maria-konnikova/">Knowledge Project podcast</a>. She intrigued me enough to want to know more about her journey, so I picked up her book, “The Biggest Bluff: How I Learned to Pay Attention, Master Myself and Win.”</p><p>The Biggest Bluff is Ms. Konnikova’s account of going from being a complete poker novice to a tournament-winning pro. The book is not a “how-to” guide to making millions in Vegas. It is instead a meditation on learning, paying attention, and making decisions.</p><p>I enjoyed following Ms. Konnikova on her journey. Here are some things I took away from the book.</p><h3>Paying Attention to the Present</h3><p>Poker is a game of simple rules but complex behaviors. Success relies on luck and the ability to understand and predict what other players on the table might do. Ms. Konnikova had to pay attention to the cards on the table and how the other players had played throughout the day and tried and figured out what their tells were.</p><p>She also had to learn to pay attention to herself and identify when she was fatigued, and take appropriate action when going off course.</p><p>John Von Neumann describes poker as the perfect game of incomplete information. But, by paying attention, it is possible to identify when emotions get in the way of sound decision-making and to try and predict your competitors’ actions and consequences.</p><p>In life, just like in poker, paying attention to the present is table stakes.</p><h3>Intuition vs. Process</h3><p>Ms. Konnikova is dismissive of intuition or “gut feeling.” She says we have intuitions all the time, but we are terrible at telling the right ones from wrong. She suggests that we trust our intuition only if we are an expert in the area.</p><p>As a novice poker player, she had to work hard to identify and suppress false confidence. She did this by learning to distinguish the action and the outcome from the thought process. In the short term, it didn’t matter if she won or lost a hand provided she was thinking through things correctly. In the long run, this focus on process meant that she would have better inputs and eventually the right conclusion with more experience.</p><p>I agree with the author that we are terrible at linking <strong>outcome</strong> to <strong>process</strong>. Luck, both good and bad, always adds noise. But by having a thought-through strategy, we can avoid false confidence and learn to avoid the pitfalls of relying on unreliable intuitions.</p><h3>Avoiding going Full Tilt</h3><p>In poker parlance, “tilting” is when a player lets irrelevant emotion cloud their thinking. You start tilting when another player or an aggravating circumstance gets under your skin and makes you emotional.</p><p>As one of very few professional female poker players, Ms. Konnikova dealt with misogynistic behavior from her fellow players. From being called “little girl” to being propositioned on the poker table — these unpleasant experiences did end up getting under her skin and affected her game.</p><p>She came up with techniques to become mindful of her emotions. She wanted to experience them but be self-reflective and not let them affect her thought process.</p><p>Humans are emotional. We experience life through emotions and can never be purely rational. Ms. Konnikova says the key is to identify irrelevant feelings and develop strategies to ignore them — avoiding going full tilt.</p><h3>Making Good Decisions</h3><p>Poker forces a player to place a monetary value on the opinions driving decisions at the table. Having a flawed decision-making process makes going broke a likely outcome.</p><p>As she became a better poker player, Ms. Konnikova became less confident in her opinions. This may seem counter-intuitive — surely becoming more experienced means becoming more confident in your opinions! But Ms. Konnikova made better decisions when she forced herself to question her assumptions. Her decision-making process relied on paying attention, not relying on flawed intuition, and having a well-practiced process.</p><p>Judging the success or otherwise of a decision-making process is more straightforward in poker than in real life. If you lose money consistently, you might want to either stop playing or take a close look at how you are playing. Judging success in other domains may not be easy, but having a clear decision-making process remains crucial.</p><h3>Conclusion: Less Certainty, More Inquiry</h3><p>We often end up making decisions on auto-pilot. We take received wisdom and our intuitions for granted. When bad things happen, we attribute them to bad luck, crappy circumstances, or other external factors.</p><p>But, as Ms. Konnikova’s mentor advises her, it is better to be less certain about things and always inquire, ask questions, and to think through things for yourself.</p><p>To have any chance of success in complex domains, it is essential to be aware of blind spots, pay attention to what is happening, and have a deliberate and well-understood decision-making process.</p><p>The Biggest Bluff is an entertaining, well-written, and thought-provoking book. Ms. Konnikova’s journey pushed me to take a closer look at how I make decisions and to ponder where my blind spots lay.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25c5995da1e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/less-certainity-more-enquiry-25c5995da1e0">Less Certainity, More Enquiry</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cultivating Range: Lessons for Startups in a Wicked World]]></title>
            <link>https://medium.com/mostly-harmless/cultivating-range-lessons-for-startups-in-a-wicked-world-dcb385f7725b?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/dcb385f7725b</guid>
            <category><![CDATA[lessons-learned]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[books]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Mon, 12 Oct 2020 17:28:08 GMT</pubDate>
            <atom:updated>2020-10-12T22:49:02.436Z</atom:updated>
            <cc:license>http://creativecommons.org/licenses/by/4.0/</cc:license>
            <content:encoded><![CDATA[<h3><strong>Introduction</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/362/1*XpnvvCx8Vfga3vAnlpsXiw.png" /></figure><p>I recently read David Epstein’s book <a href="https://davidepstein.com/the-range/">Range: Why Generalists Triumph in a Specialized World</a>. The book focuses on how to cultivate broad thinking strategies to learn effectively. Epstein’s focus is on individuals. As I made my way through the book, I saw that the points made in this book apply equally well to teams.</p><p>I work with and advise early stage technology startups. I learnt a lot while reading “Range”. In this post, I explore how the lessons from “Range” can benefit technology startups or teams looking to launch a new product.</p><h3>Thriving in Wicked Environments</h3><p>Epstein introduces the concept of <strong>Kind</strong> and <strong>Wicked</strong> environments. A chessboard is a kind environment: the rules are clear, and actions are deterministic. Strategies that work in one situation should work well in similar cases. However, in the real world there are feedback loops and second-order consequences that are difficult to predict. It is a rapidly changing Wicked environment. Strategies that worked well in the past can stop working due to changes to the external environment or the market’s reaction to your previous actions.</p><p>We see this pattern repeatedly in the world of startups. Ideas that seem destined for success fail because they attempt to solve a problem that is no longer important or serve a market that no longer exists.</p><p>To thrive in a Wicked environment, a team may need to take conceptual knowledge from one problem domain and apply it to an entirely new one. The ability to think broadly and to be able to deploy flexible solutions to complex problems could be the difference between a successful product launch and complete failure.</p><h3>Creating Innovative Products Through Analogical Thinking</h3><p>Epstein describes <strong>Analogical Thinking</strong> as —</p><blockquote><em>“The practice of recognizing conceptual similarities in multiple domains or scenarios that may seem to have little in common on the surface.”</em></blockquote><p>Barriers to entry in the information economy are low. While anyone can launch a software product or service, successful companies frequently bring together ideas from different fields to build a compelling product.</p><p>Uber brought together logistics, mapping, mobile experiences, and access to an entirely new labor market to create a transformational service. <a href="https://www.snowflake.com/">Snowflake</a>’s recent success is another example of a business built on the convergence of industry and technology trends. They successfully executed a simple, in hindsight, idea — cloud-only data warehouses.</p><h3>Building a Successful Team</h3><p>In <a href="https://www.amazon.com/dp/B015LYZGW6/">Superforecasting</a>, Philip Tetlock quotes the Greek poet Archilochus: <em>“the fox knows many things, but the hedgehog knows one big thing.”</em> Hedgehogs are specialists — they love to focus on one problem and usually work within their specialty’s confines. Foxes tend to work across various disciplines and work under ambiguity and contradictory conditions.</p><p>Epstein cites Tetlock’s research in forecasting and shows that in the face of uncertainty, individual breadth is critical. Similarly, teams that were open-minded and embraced a wide range of experience outperformed teams of narrow specialists.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RqKxGTcuM7iMrXJkSPTqvQ.png" /><figcaption>A Team of Foxes may be more effective in a startup</figcaption></figure><p>Early-stage teams need to be open-minded and willing to change their assumptions and pivot when circumstances demand it. As a company matures, it may become useful to include specialists to refine a product and idea. However, having too many specialists at an early stage could lead to tunnel vision.</p><h3>Choosing a Technology Stack</h3><p><a href="https://en.wikipedia.org/wiki/Gunpei_Yokoi">Gunpei Yokoi</a> was a legendary video game designer at Nintendo. He designed the Game Boy. In Range, Epstein talks about Yokoi’s concept of <strong><em>“Lateral Thinking with Withered Technology.”</em></strong></p><blockquote>The heart of his philosophy was putting cheap, simple technology to use in ways no one else considered. If he could not think more deeply about new technologies, he decided, he would think more broadly about old ones.</blockquote><p>You can still see this philosophy in play at Nintendo today.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*YZW_7PQZiLQFjV1_aTKxjQ.png" /><figcaption>The Nintendo Gameboy — A Lateral Application of Withered Technology</figcaption></figure><p>This lesson is of particular importance for startups with technical founders. It is tempting to be on the cutting edge of technology. But few customers will pay to use a product because it uses a fashionable technology stack. The ability of the company to solve the customer’s problem is way more important.</p><p>It may be more productive and faster to build a product using battle-tested, well-understood technology that is quickly and cheaply available. Just like Nintendo, a startup must cultivate a relentless focus on delighting the customer. Technology choices should come second.</p><h3>Deploying Data Carefully</h3><p>Startups are encouraged to be data-driven. They optimize for metrics such as customer behavior metrics, sales funnels, infrastructure costs, etc. The danger for the startup here is relying too much on data to make decisions without considering the market or whether the data is relevant to the vision of the company. As Epstein says — the critical question to ask is:</p><blockquote><em>‘Is this the data that we want to make the decision we need to make?’</em></blockquote><p>A dogmatic data-driven approach may lead to doing the same thing in response to the same challenges over and over until the behavior becomes so automatic that it is no longer recognized as a situation-specific tool.</p><p>An over-reliance on data can lead to actions that may improve the metrics the team relies on, but may not help the company in the long run to achieve their strategic objectives.</p><h3>Making the most of External Advisors</h3><p>Formal or informal advisors can play a critical role to the founding team in a startup. The most effective advisors are outsiders who may be removed from the company’s problem but may help reframe the problem that unlocks the solution.</p><p>Epstein notes —</p><blockquote><em>‘A key to creative problem solving is tapping outsiders who use different approaches so that the “home field” for the problem does not end up constraining the solution.’</em></blockquote><p>An outside advisor may offer solutions to a problem the founding team may not even consider because they are too close to the problem.</p><h3>Knowing when to Give Up</h3><p>Thirty percent of startups will go under within two years. Fifty percent will fail within five. Running out of money is the most common reason for failure. If a startup keeps trying to execute the same plan despite not gaining traction, it will fail.</p><p>Startup culture venerates hard work and not giving up. But here, Epstein provides an essential quote from <a href="https://www.sethgodin.com/">Seth Godin</a>:</p><blockquote><em>‘We fail when we stick with tasks we don’t have the guts to quit.’</em></blockquote><p>The best, most thought-through plan may fail when it comes up against external conditions — like a global pandemic. Persevering through difficulty can be a competitive advantage, but knowing when to quit can also be a significant strategic advantage. As a startup, it is vital to define and understand the conditions in which it is clear that Plan A has failed, and it is time to try something else.</p><h3>Conclusion</h3><p>Building and running a startup is exciting, scary, and can be extremely challenging. It rewards being able to adapt to complex, changing environments. It is vital to pick the right problem to solve, identify the correct tools to solve the problem, and build a team that learns how to make the most of diverse skill sets. Leveraging data and being metric driven can help guide, but must not constrain decision making. Leaning on external advisors and investors is essential to help keep the team grounded and provide different perspectives to solve tricky problems.</p><p>Finally, success is not just about persevering through difficult times; it also involves knowing when to quit and when to pivot. A battle may be won simply by disengaging at the right time.</p><p>Range is a fantastic book and one that I strongly recommend. The lessons in the book are important not just for individuals but also for teams.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dcb385f7725b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/cultivating-range-lessons-for-startups-in-a-wicked-world-dcb385f7725b">Cultivating Range: Lessons for Startups in a Wicked World</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[BioWare & Anthem: A Cautionary Tale]]></title>
            <link>https://medium.com/mostly-harmless/bioware-anthem-a-cautionary-tale-bfd5c15b574a?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd5c15b574a</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 21:48:00 GMT</pubDate>
            <atom:updated>2019-04-03T21:48:00.546Z</atom:updated>
            <content:encoded><![CDATA[<p>I love playing video games. My favourite game series is called <a href="https://en.wikipedia.org/wiki/Mass_Effect">Mass Effect</a> made by a game studio called <a href="http://www.bioware.com/">BioWare</a>.</p><p>I am a huge fan of BioWare’s games and I was looking forward to trying out their new game <a href="https://www.ea.com/games/anthem">Anthem</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6MOsnc1Fn0p7CrJF6aEWSg.jpeg" /><figcaption>Anthem — Landed with a thud (Copyright BioWare)</figcaption></figure><p>Anthem came out in early 2019 to <a href="https://www.metacritic.com/game/pc/anthem">universally poor reviews</a>. The game was half finished, had poor gameplay and did not respect the player’s time. I ended up giving it a miss.</p><p>This week, <a href="https://kotaku.com/">Kotaku’s</a> Jason Schreir has an excellent <a href="https://kotaku.com/how-biowares-anthem-went-wrong-1833731964">article</a> about what went wrong with Anthem. It turns out Anthem’s development was troubled, and the development team faced the same sort of problems (some self-inflicted) that I have seen a few times in my career. I suggest you take some time to read the excellent article linked above. It is a wonderfully researched and well-written piece.</p><p>So what went wrong? Schreir’s article talks about game studio politics, financial pressures and many other contributed factors. I want to focus on what went wrong with Anthem as a <em>software project</em>. Here are some of my thoughts on this cautionary tale that I think may apply to many software development teams.</p><h4>Building a product for a market you don’t understand</h4><p>BioWare is famous for making role-playing games (also know as RPGs). The core team for Anthem had made well-loved games such as Mass Effect — single player, immersive, story-driven experiences. They were asked, by their owner EA, to build a multi-player, online, <a href="https://www.giantbomb.com/loot-gathering/3015-161/games/">loot</a>-driven shooter such as <a href="https://en.wikipedia.org/wiki/Destiny_(video_game)">Destiny</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/275/1*XYca3n4DgS9ySiOFSwOnIw.jpeg" /><figcaption>Destiny — Doing Loot Well (Source*)</figcaption></figure><p>These games made money through micro-transactions; charging players small amounts of money to buy in-game items. The Anthem team did not understand the fundamentals of the product they were being asked to create. Basic mechanisms such as loot drops (where players get rare items for completing missions) did not work well. YouTube is full of players ranting about Anthem’s lack of loot.</p><h4>Not being clear about the scope of the product</h4><p>The Anthem lead team were slow in making decisions about critical features. Flying: a fundamental gameplay feature was added and removed multiple times. The team was only aware that flying was in scope following a demo to an EA executive who decreed that the game must allow it. This is like building a desktop app and not being sure whether mouse input should be enabled. It makes things difficult for the design and development teams.</p><h4>Being forced to use a technology stack by decree</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/250/1*GvjLt6UwyxyhCsxU3plfKQ.jpeg" /><figcaption>Mass Effect — Built using the Unreal Engine (Copyright BioWare)</figcaption></figure><p>Most modern games are built using game engines such as <a href="https://unity.com/">Unity</a> or <a href="https://www.unrealengine.com/">Unreal Engine</a>. EA mandated that all its games, including Anthem, must be built using the in-house <a href="https://www.ea.com/frostbite">Frostbite</a> engine. They wanted to cut costs and re-use resources by not having to pay a licensing fee. Apparently, the Frostbite engine, while used successfully in games like the Battlefield series, was poorly documented and not suited to a game like Anthem. The development team struggled to make it work, and productivity suffered.</p><p>The same team that had made the Mass Effect series using the Unreal engine.</p><h4>Inflexible deadlines &amp; Developer burnout</h4><p>Anthem was in pre-production since 2012 but didn’t go into full-scale development until 2018. They had shown off an early beta to a rapturous audience at <a href="https://www.youtube.com/watch?v=ZH59LK5vUJI">E3 in 2017 </a>. Commercial pressures meant the team had to have the game out by 2019. This was ambitious for a project already beset with problems. The gaming industry is notorious for treating it’s developers badly, but the Anthem team started a brutal ‘crunch’ period that ended up with many developers going on extended sick leave due to stress. Developers left Bioware in droves because of the miserable working conditions.</p><h4>Shipping before being ready</h4><p>A YouTube reviewer I follow mentioned that the game played as if the developers hadn’t even bothered playtesting their own game. The article talks about unstable builds and unavailable test environments. There was no time left for a thorough quality assurance process. When the game did come out, players complained about interminable load times and repetitive missions. There were also hard crashes and un-usable inventory systems: a big problem for a looter shooter.</p><h4>In conclusion..</h4><p>Anthem is a failure and has resulted in Bioware losing credibility as a game studio. I think it failed because it was a poorly managed software project. It was a poorly thought out product released in a broken state by a confused and stressed development team. This pattern is not unique just to the video game industry. I am sure software engineers of a certain vintage have seen this play out in a variety of industries.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd5c15b574a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/bioware-anthem-a-cautionary-tale-bfd5c15b574a">BioWare &amp; Anthem: A Cautionary Tale</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The 4 Waves of AI — And why they matter]]></title>
            <link>https://medium.com/mostly-harmless/the-4-waves-of-ai-and-why-they-matter-51d545164e03?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/51d545164e03</guid>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Fri, 15 Feb 2019 17:45:42 GMT</pubDate>
            <atom:updated>2019-02-15T17:45:42.693Z</atom:updated>
            <content:encoded><![CDATA[<h3>The 4 Waves of AI — And why they matter</h3><p>I can’t open a newspaper or visit my friendly local bookstore without coming across a think piece about why AI is a *BIG DEAL* and how it changes everything. The tone of most of the material that I have come across is aptly summed up in this classic <a href="https://imgs.xkcd.com/comics/robot_future.png">xkcd panel</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/611/1*Pc3iwbsdxITiAr5jf7RTCQ.png" /><figcaption>Copyright — xkcd (https://imgs.xkcd.com/comics/robot_future.png)</figcaption></figure><p>In January 2019, I read Kai-Fu Lee’s fantastic <a href="https://aisuperpowers.com/">book</a> “AI Super-Powers: China, Silicon Valley, and The New World Order.” Mr. Lee is a thoughtful, even-handed guide to what is going on in the field of Artificial Intelligence (specifically Machine Learning) and how it may impact our future. The book is also an eye-opening account of the Chinese startup eco-system — but perhaps more on that another day.</p><p>Early in the book, Mr. Lee talks about how the spread of AI is happening in four waves. These waves are:</p><ol><li><strong>Internet AI</strong></li><li><strong>Business AI</strong></li><li><strong>Perception AI</strong></li><li><strong>Autonomous AI</strong></li></ol><p>Let’s take quick a look at each of these waves.</p><h3>Internet AI</h3><p>We deal with Internet AI every time we shop online, scroll through our social media feeds or Google something. From <em>AI Superpowers:</em></p><blockquote>Internet AI is mainly about using AI algorithms as recommendation engines: systems that learn our personal preferences and then serve up content hand-picked for us.</blockquote><p>Examples of Internet AI include online advertising optimization, personalized news feeds, and algorithmic content recommendation.</p><h3>Business AI</h3><p>Advances in machine learning have allowed businesses to take advantage of labeled, structured data that resides in data repositories and train algorithms to outperform humans on clearly defined optimization tasks. Some examples here include automated credit scoring, fraud detection, algorithmic trading, and supply chain optimization. While not the most exciting topic, in the short term, Business AI has the potential to have a significant impact in the way we work and more potently, what <em>*types of work*</em> make sense to automate.</p><blockquote>Business AI is about optimising and generating value from structured data.</blockquote><p>Business AI has the potential to make what were once stable professions like accountancy, insurance, and medicine obsolete in their current form. It also has the potential to generate vast and lucrative new opportunities. More on this later.</p><h3>Perception AI</h3><p>Perception AI is about the “Digitisation of the physical world.” It is about using real-world data captured from IoT devices, cameras, smartphones, and other devices to blur the lines between the online and offline worlds. We already see applications of facial recognition and machine translation technology enhance offline experiences such as shopping and travel as well as enrich experiences such as education.</p><blockquote>Perception AI is about blurring the lines between the online and offline world</blockquote><p>Augmented reality (AR) devices and applications increase merging of the offline and online world. Perception AI also has worrying implications around surveillance, privacy and data protection.</p><h3>Autonomous AI</h3><p>Autonomous AI represents the culmination of the three preceding waves of AI. What was once science fiction is slowly becoming mundane. Autonomous AI is about fusing the ability to optimize from extremely complex datasets and integrate them with powerful sensory abilities resulting in machines that can understand and shape the world around them.</p><blockquote>Autonomous AI results in machines that can understand and shape the world around them.</blockquote><p>We already see some limited applications of Autonomous AI in the fields of self-driving cars, automated factories and pollinators.</p><h3>What does it all mean?</h3><p>Ben Evans, a partner at the storied VC firm <a href="https://a16z.com/">Andreessen Horowitz</a>, talks a little about the implications of advances in AI in the November 2018 presentation <a href="https://www.ben-evans.com/benedictevans/2018/11/16/the-end-of-the-beginning">“The End of the Beginning”</a>. He says:</p><blockquote>“Tech is building different kinds of businesses, and so will take different shares of that opportunity, but more importantly change what those industries look like.“</blockquote><p>He says further that a combination of high internet penetration, changing consumer expectations and a general “unbundling” of supply chains are creating business models that in turn are enabled and accelerated by AI. The breaking apart of tightly coupled logistics supply chains is just one example of this phenomenon.</p><p>At my work with Jeavio’s portfolio companies, I can already see this in action. We support entrepreneurs who are working in diverse fields such as customer experience analytics, construction and high tech agriculture. In each of these various fields, we see applications of Business AI that have the potential to disrupt existing models and generate tremendous value.</p><p>In my previous career working in high-frequency algorithmic trading, I have seen technology disrupt financial markets. Advances in AI are now doing the same in a wide variety of fields.</p><p>While AI cannot by itself generate new business models, it is already a potent force multiplier, which when deployed effectively, can increase efficiency and help businesses capture more value. We may not worry about our Robot Overlords just yet; we should keep an eye on the disruption and opportunities presented by the four waves of AI.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51d545164e03" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/the-4-waves-of-ai-and-why-they-matter-51d545164e03">The 4 Waves of AI — And why they matter</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do you know your dependencies?]]></title>
            <link>https://medium.com/mostly-harmless/do-you-know-your-dependencies-bf91d953b3d3?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf91d953b3d3</guid>
            <category><![CDATA[startup-lessons]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Tue, 27 Nov 2018 00:06:06 GMT</pubDate>
            <atom:updated>2018-11-27T00:06:06.532Z</atom:updated>
            <content:encoded><![CDATA[<p>A contributor on GitHub finds an abandoned, but popular JS library and commits code that targets a Bitcoin wallet made by a particular company. Hundreds of other libraries use this library making this vulnerability affect thousands of applications since it is a transitive dependency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2e_iASsJHXVeLlyW5wfH0w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/JZ8AHFr2aEg?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Bryson Hammer</a> on <a href="https://unsplash.com/search/photos/chain?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>NPM (and <a href="http://npmjs.com/">npmjs.com</a>) provide a valuable service in hosting JavaScript dependencies. By blindly upgrading to latest version of libraries, developers can open themselves to malicious attacks similar to those described below.</p><p>I would recommend developers understand how npm’s package lock mechanism works. This will ensure that your dependencies are reproducible and force the use of known and trusted modules instead of downloading the latest version.</p><p>This is not a problem just with the JavaScript eco-system. Python (via pip or conda) and Java (via maven &amp; gradle) have similar issues. However my, totally subjective and un-scientific, observation is that JavaScript libraries tend to have way more dependencies (see the “left-pad” debacle for example)..</p><p>Ars Technica has a good write up about this particular issue: <a href="https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/">https://arstechnica.com/information-technology/2018/11/hacker-backdoors-widely-used-open-source-software-to-steal-bitcoin/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf91d953b3d3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/do-you-know-your-dependencies-bf91d953b3d3">Do you know your dependencies?</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Computer Says No]]></title>
            <link>https://medium.com/mostly-harmless/on-th-aac65d1fbc58?source=rss-5802d247f2ad------2</link>
            <guid isPermaLink="false">https://medium.com/p/aac65d1fbc58</guid>
            <category><![CDATA[human-centred-design]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[startup-life]]></category>
            <category><![CDATA[empathy]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Rushi Luhar]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 21:24:16 GMT</pubDate>
            <atom:updated>2018-11-15T22:47:55.546Z</atom:updated>
            <content:encoded><![CDATA[<h3>Computer Says No..</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d9F4DWKvmZT3qdCs17pykw.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/5otlbgWJlLs?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Andre Hunter</a> on <a href="https://unsplash.com/search/photos/frustration?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Everyone has dealt with a “Computer Says No” situation. You call up a customer services agent hoping for a quick resolution to a perfectly reasonable query. But “computer says no”. You go through a convoluted questionnaire, answer the questions as best you can, but “computer says no”. The customer service agent shrugs saying that they can’t do anything because the system won’t let them.</p><p>It is tempting to call the customer service agent a jobsworth, or someone who doesn’t care about their job. To hang up in frustration and curse the status of the customer service industry.</p><p>So why is modern customer service so bad? Why do we dread calling up a help line or deal with an online customer support agent (who may or may not be a bot)?</p><p>Atul Gawande’s recent New Yorker <a href="https://www.newyorker.com/magazine/2018/11/12/why-doctors-hate-their-computers">article</a> on why medical professionals hate their computers may have an answer. Dr. Gawande is a surgeon. In the article, he talks about how the medical informations systems used in his hospital make it difficult to really look after his patients.</p><p>Hospital systems in the US (much like the NHS in the UK) have spent billions of dollars to make medical care more efficient. But when we go visit our local general practitioner, we find them struggling with their PC more than talking to us. Instead of empathy, we get distracted clicks and frowns while the doctor tries to figure out how to massage the conversation into a bunch of drop downs and radio buttons. It is a terrible experience for everyone involved.</p><p>I am an engineer, I like efficiency. I like measuring the performance of the code I write and love reading articles about how to optimise software. In this pursuit of perfection, I fear that we have optimised ourself into a corner. Our systems are optimised, everything is measured — except the misery that they inflict on those who actually have to use the system every day. Human conversations and problems cannot be modelled so easily into a workflow. Improved throughput and the need to be more efficient drive design decisions more than the need to solve a problem. So we end up systems that their users hate. These systems and workflows lead to dis-engaged employees and ultimately to terrible customer service.</p><p>The next time that someone talks about having poor customer service, don’t blame the agent. Blame the analyst who designed the convoluted workflow in the software they use and the engineer who implemented it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aac65d1fbc58" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mostly-harmless/on-th-aac65d1fbc58">Computer Says No</a> was originally published in <a href="https://medium.com/mostly-harmless">MOSTLY HARMLESS</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>