<?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[Bluestem Tech Blog - Medium]]></title>
        <description><![CDATA[Brain Dumps from the Bluestem Tech Crew - Medium]]></description>
        <link>https://medium.com/bluestem-tech-blog?source=rss----cff05ff1528c---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Bluestem Tech Blog - Medium</title>
            <link>https://medium.com/bluestem-tech-blog?source=rss----cff05ff1528c---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:09:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/bluestem-tech-blog" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Code As Art]]></title>
            <link>https://medium.com/bluestem-tech-blog/how-to-become-a-beautiful-coder-6e9cb735a78e?source=rss----cff05ff1528c---4</link>
            <guid isPermaLink="false">https://medium.com/p/6e9cb735a78e</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Teddy Kim]]></dc:creator>
            <pubDate>Mon, 01 Oct 2018 15:01:01 GMT</pubDate>
            <atom:updated>2018-10-01T17:11:21.193Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1015/1*OHoMfVNiI_u9rNovX-BXQg.png" /></figure><p>Years ago I saw Marcel Molina give a talk at RubyConf that blew my mind. The title of the presentation was “<a href="https://www.youtube.com/watch?v=eutF6GbJohY">What Makes Code Beautiful?</a>”</p><p>Marcel uses a heuristic for beauty borrowed from a Medieval philosopher named Thomas Aquinas. In <em>Summa Theologica</em> Aquinas wrote that a beautiful thing possesses three characteristics:</p><p>1. Proportion: its parts are in proportion to each other and the whole<br>2. Clarity: its purpose is transparent and easy to understand<br>3. Integrity: nothing is missing; the thing is complete</p><p>Students of medieval history know that Aquinas’ formulation of beauty was critical in the design and construction of churches.</p><p>Strange indeed that a centuries-old formulation of aesthetics should re-emerge at a 20th century software conference, in a presentation about beautiful code!</p><h4>A Latticework of Mental Models</h4><p>Famed investor Charlie Munger would call Marcel’s presentation a <em>latticework of mental models</em>.</p><p>You may not have heard of Charlie Munger, but you have surely heard of Berkshire Hathaway, the investment vehicle that has returned around 2,000,000% of its initial value under Munger’s guidance.</p><p>Two million percent! How is this possible?</p><p>Munger attributes Berkshire Hathaway’s success to his continual thirst for knowledge. An avid learner, Munger has accumulated mental models from numerous problem domains including physics, economics, and philosophy.</p><p>Munger isn’t an oddball. Many luminaries including Bill Gates and Barack Obama have attributed their success to the practice of deliberate learning.</p><p>Continual learning and success are so tightly linked that the linkage has become codified as the so-called <a href="https://medium.com/the-mission/the-5-hour-rule-if-youre-not-spending-5-hours-per-week-learning-you-re-being-irresponsible-791c3f18f5e6"><em>five-hour rule</em></a>.</p><p>The five-hour rule says that the secret to success is to carve out one hour per weekday to read, think, and experiment.</p><p>The question is why?</p><p><em>Why</em> does deliberate learning give you an advantage? How precisely, does it contribute to your success?</p><p>In practical and tangible terms, why should <em>you</em> invest in a latticework of mental models?</p><h4>Plod or Leap</h4><p>Most mornings the only thing that gets me out of bed is that I’m annoyed by the coding problem I couldn’t figure out the day before.</p><p>Being a software engineer is hard, and the job keeps getting harder. Tech refreshes every year so whatever you learn today may be completely worthless tomorrow.</p><p>If you are early in your career, when you get stuck, (and you will get stuck) you have to solve problems through deduction, which is a long, tedious process of logical analysis based on facts and direct observation.</p><p>Deduction is grueling and time-consuming. That’s why it takes weeks for a junior engineer to do the same task that a senior engineer can do in minutes. Everyone I know who quit tech could not evolve past this stage.</p><p>The other way to solve engineering problems is inference. You get to the same destination as you would through deduction but you get there faster, because you are reasoning to a conclusion based on things you already know. In other words, inference is <em>a mental leap</em>.</p><h4>How Inference Works</h4><p>In my first comp sci class we learned how to write bubble sorts. The bubble sort gets its name from the way items “bubble” to the top of a list. You don’t need to know anything about code to be able to visualize bubbles rising to the surface. If you’ve ever seen a bubble, you get the gist of the bubble sort.</p><p>That’s how inference works. It gives you a mental shortcut that you already paid for with prior knowledge. Pretty sweet!</p><p>Here’s a more current example. At Bluestem Brands we spend a lot of time trying to make our systems as resilient as possible. We use Hystrix and other goodies to implement circuit breakers in components that are vulnerable to network timeouts. When a circuit is broken, the component will stop trying to do something that is likely to fail.</p><p>The point is, you don’t need to know the details of how Hystrix works. If you know basic electronics, you get the gist of how a software circuit breaker works.</p><p>In other words, knowledge from one problem domain allows you to make a mental leap in another problem domain.</p><p>You could have gotten there through deduction, but the time and cost involved would be enormous.</p><p>Deduction plods. Inference leaps.</p><p>You need to leap.</p><h4>Beautiful Code</h4><p>And that brings me full circle to beautiful code.</p><p>The most successful and sought-after engineers I know all have one thing in common. Namely, they are incredibly opinionated. The most effective engineers are not just passengers dozing off on the bus to Janky Town. They are minutely engaged in the aesthetics of their code <em>as well as its function.</em></p><p>Code as art requires a mental leap that is impossible if you are intellectually confined to 1’s and 0’s. To get to beautiful code, you need to actively look across problem domains. You need to weave a latticework of mental models that will allow you to <strong>form your own opinions</strong> about proportion, clarity, and integrity.</p><p>Otherwise, everything you do will look and feel like a paint-by-numbers kit.</p><p>So step away from the keyboard. Put down your cool side project. Instead, pick up a non-technical book. Enroll in a class. Learn a new sport. Diversify your investment in yourself!</p><p>We’re hiring! Search <a href="http://www.bluestem.com/careers/search-jobs/">our openings</a> at <a href="http://www.bluestem.com/careers/">Bluestem Careers</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e9cb735a78e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluestem-tech-blog/how-to-become-a-beautiful-coder-6e9cb735a78e">Code As Art</a> was originally published in <a href="https://medium.com/bluestem-tech-blog">Bluestem Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Be a Tech Lead]]></title>
            <link>https://medium.com/bluestem-tech-blog/how-to-be-a-tech-lead-ac1829d3480c?source=rss----cff05ff1528c---4</link>
            <guid isPermaLink="false">https://medium.com/p/ac1829d3480c</guid>
            <category><![CDATA[rowing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Teddy Kim]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 13:48:07 GMT</pubDate>
            <atom:updated>2018-08-20T15:49:02.573Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Recently a dear friend received a well-deserved promotion to lead engineer. After years as a single contributor, he had trouble getting his bearings as an engineering leader. When his first major project started a death spiral, he reached out to me for advice. This is the email I sent to him, reprinted with his permission.</em></p><p>Hello Sam,</p><p>Don’t give up. Things might seem bleak right now, but things will get better. I think that your problems can be solved, rather easily, with a relatively minor adjustment in mindset.</p><p>If you can humor me, I’d like to present the following analogy.</p><p>Since you grew up on the East Coast you probably know something about crew, or the sport of rowing. In crew there are several different boat and crew configurations, but the most well known boat is an “eight” which accommodates eight crew members sitting in a row.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ccskCk6-g5JU3asfl8qRWA.jpeg" /></figure><p>Rowers are typically selected for physical attributes. The best rowers have long arms and legs and a seemingly infinite appetite for pain. Rowers are incredible physical specimens whose brawn propels the boat through the water.</p><p>At the stern of the boat is a diminutive figure with a megaphone calling moves to the rowers as the boat cuts through the water. This person is the coxswain. Many coxswains weigh less than 140 pounds, because extra weight creates more drag on the boat, and more work for the rowers.</p><p>The coxswain cannot be deadweight. His or her job is too important.</p><p>Because the coxswain sits in the stern, facing forward, he or she is the only person who can see where the boat is headed. So part of the coxswain’s job is to steer while responding to the environment and managing the feel of the boat on the water.</p><p>The coxswain is also the only person on the planet who can see the faces of the crew. Therefore, the cox is the only person who can respond to their pain. The cox knows when a rower has more to give and he knows when the rower is close to breaking. The cox knows how to motivate the crew to overcome adversity and defeat the competition.</p><p>A boat without a good coxswain faces certain disaster. The rowers will be out of sync. They will row without power or rhythm. The boat will run aground and the competition will leave them behind.</p><p>Right now your team is a boat without a coxswain. By all accounts everybody is working their asses off. But without someone to focus and direct that power, your entire team is just leaking energy and burning out. Pretty soon your best devs are going to bounce. Once those floodgates open your job is going to become <em>much</em> harder.</p><p>So here’s what you have to do. If you want to turn your team around (and save your sanity) put down your oar. Move to the stern of the boat. Pick up your megaphone. Get your head around the idea that you’re not a rower anymore. Become the coxswain your team needs.</p><p>If that’s too abstract for you, let’s put the analogy aside.</p><p>The biggest mistake you’re making is that you’re trying to write code like you did before you became a lead.</p><p>Why is this a mistake?</p><p>Coding by its nature requires deep and intense concentration for long periods of time. Every time you indulge yourself in heads-down focus work you are incurring massive opportunity cost:</p><ul><li>You can’t observe the faces of your team, so you lose touch with how they are feeling. You can’t motivate your team when you’re not connected to them.</li><li>You can’t see where you are in relation to your competition. Is your team applying force to tech that will drive growth and revenue? Or are you just doing resume-driven development?</li><li>You can’t steer away from obstacles and pitfalls. Remember, projects don’t fail because of the unforeseeable. Projects fail when the people at the wheel aren’t paying attention.</li><li>You can’t find and exploit force-multipliers. Without force multipliers your team can never scale to meet the mountain of work coming down your pipeline.</li></ul><p>To confront the brutal reality, your boat is running aground and your crew is burning out. You have problems that <em>cannot be solved with code</em>. Until you reorient yourself and start to steer the boat, coding is the <em>last</em> thing you should be worried about. Let the crew deal with the coding. You need to start steering.</p><p>Am I saying that as a lead engineer you <em>can’t ever </em>code? No. I am asserting that a lead engineer <em>earns the right</em> to code by having an optimized team.</p><p>Your team is definitely not optimized, but with your leadership, it can be.</p><p>Hang in there!</p><p><em>p.s. I forgot something important. To the spectators, the coxswain is just a little person with a megaphone. But everyone in the sport knows that the coxswain is the linchpin of any winning crew.</em></p><p><em>Oddly, though the coxswain is under constant scrutiny by the rowers and coach, he or she does not get credit when a crew wins. Can you be okay with that?</em></p><p>We’re hiring! Search <a href="http://www.bluestem.com/careers/search-jobs/">our openings</a> at <a href="http://www.bluestem.com/careers/">Bluestem Careers</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac1829d3480c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/bluestem-tech-blog/how-to-be-a-tech-lead-ac1829d3480c">How to Be a Tech Lead</a> was originally published in <a href="https://medium.com/bluestem-tech-blog">Bluestem Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>