<?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 Johannes Hansen on Medium]]></title>
        <description><![CDATA[Stories by Johannes Hansen on Medium]]></description>
        <link>https://medium.com/@johanneshansen?source=rss-19752d572932------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dswhl9GPf3pI5jjXylB85A.jpeg</url>
            <title>Stories by Johannes Hansen on Medium</title>
            <link>https://medium.com/@johanneshansen?source=rss-19752d572932------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:00:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@johanneshansen/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[13 Essential Books for Tech Leaders and Software Engineering Managers]]></title>
            <link>https://medium.com/@johanneshansen/13-essential-books-for-tech-leaders-and-software-engineering-managers-3f6d9510ae5?source=rss-19752d572932------2</link>
            <guid isPermaLink="false">https://medium.com/p/3f6d9510ae5</guid>
            <category><![CDATA[leaders]]></category>
            <category><![CDATA[technology-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[books-recommendation]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Johannes Hansen]]></dc:creator>
            <pubDate>Fri, 04 Sep 2020 10:52:04 GMT</pubDate>
            <atom:updated>2020-09-04T10:52:04.277Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qWcbael28SiRtLa-JNTUwg.jpeg" /></figure><p>Whether you are in a leadership role for the first time or if you are an experienced leader who is looking to improve and grow to the next level, something always can be learned from the experience and writing of others. As Harry S. Truman observed:</p><blockquote>“Not all readers are leaders, but all leaders are readers.”</blockquote><p>On my own journey, I relied a great deal on books to establish myself in a leadership position within a technology environment. I strongly believe you need a special approach when you are managing mostly teams of engineers. The following is a comprehensive list of books I found to be most helpful. If you read these you will have a strong foundation for the (sure to come) challenges ahead.</p><p><strong>Management</strong></p><p><a href="https://www.amazon.de/Peter-F-Drucker/dp/0060833459/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=1FNOG69VIBOLU&amp;dchild=1&amp;keywords=effective+executive&amp;qid=1598112628&amp;sprefix=effective+ex,aps,173&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=df4a431de4644a45fcc9a00be6a27c6e&amp;language=de_DE">The Effective Executive by Peter Drucker </a>The fundamentals for managing knowledge workers. Still as relevant today as it was during publication in the 1960s.</p><p><a href="https://www.amazon.de/Andrew-S-Grove/dp/0679762884/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=22KM1J7DWFDJO&amp;dchild=1&amp;keywords=high+output+management&amp;qid=1598112674&amp;sprefix=high+outp,aps,166&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=83686880bf909eddb13747f8b997b088&amp;language=de_DE">High Output Management by Andy Grove</a> Andy Grove wrote the bible for managing engineers during his tenure at Intel. He heavily expanded on Drucker’s works.</p><p><a href="https://www.amazon.de/John-Doerr/dp/024134848X/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=2EAOD416IFW1G&amp;dchild=1&amp;keywords=measure+what+matters&amp;qid=1598112562&amp;sprefix=measure+what,aps,186&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=343400fa2bb2fb77b03b58ffae296b5d&amp;language=de_DE">Measure What Matters by John Doerr</a> A good and comprehensive guide for the management system of Objectives and Key Results, the most prevalent management system in technology organizations. Also, it is a direct expansion on Drucker and Grove.</p><p><strong>Leadership</strong></p><p><a href="https://www.amazon.de/Ben-Horowitz/dp/0062273205/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=TVIIATDVUN01&amp;dchild=1&amp;keywords=the+hard+thing+about+hard+things&amp;qid=1598112703&amp;sprefix=the+hard+thi,aps,170&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=8c03228af325a10692650cd1f086361e&amp;language=de_DE">The Hard Thing About Hard Things: Building a Business When There Are No Easy Answers by Ben Horovitz</a> A great resource on the hard decisions you have to make and how to make them when facing an existential crisis. Especially relevant in 2020.</p><p><a href="https://www.amazon.de/What-You-Do-Who-Are/dp/0008356114/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=YLSCO5M4NGRI&amp;dchild=1&amp;keywords=what+you+do+is+who+you+are&amp;qid=1598112769&amp;sprefix=what+you+do+,aps,174&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=664a92fc642e6b024f0ebe42d2dc4d52&amp;language=de_DE">What you do is who you are by Ben Horovitz</a> Another great resource on what constitutes culture with unusual examples from slave revolts in Haiti and prison gangs.</p><p><a href="https://www.amazon.de/gp/product/1473675987/ref=as_li_tl?ie=UTF8&amp;tag=twitter08-21&amp;camp=1638&amp;creative=6742&amp;linkCode=as2&amp;creativeASIN=1473675987&amp;linkId=4f83f67ae66d95df64ff2db81fc58e3a">Trillion Dollar Coach: The Leadership Playbook of Silicon Valley’s Bill Campbell by Eric Schmidt</a> On of the most fascinating profiles of Bill Campbell who acted as a leadership coach (among others) for Steve Jobs of Apple and Larry Page of Google. Full of invigorating details about his work ethic but also how he prioritizes his youth team practice session over a call from Steve Jobs (which went unanswered after he looked at his phone).</p><p><a href="https://www.amazon.de/Leaders-Eat-Last-Together-Others/dp/1591848016/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=1UD4Y6DXJGYVF&amp;dchild=1&amp;keywords=leaders+eat+last&amp;qid=1598209563&amp;sprefix=leaders+eat+last,aps,162&amp;sr=8-1&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=faaa4bca22a157618c1b1d9e1d992a83&amp;language=de_DE">Leaders Eat Last by Simon Sinek</a> My favorite introduction to Servant Leadership. In my opinion the most effective style for leaders in technology organizations.</p><p><a href="https://www.amazon.de/Servant-Leadership-Action-Achieve-Relationships-ebook/dp/B076663QPF/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=HH8II9VE6L5C&amp;dchild=1&amp;keywords=servant+leadership&amp;qid=1598112819&amp;sprefix=servant+le,aps,169&amp;sr=8-7&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=4a42a8b166bfe91b234b6f0521d63762&amp;language=de_DE">Servant Leadership in Action: How You Can Achieve Great Relationships and Results by Ken Blanchard and Renee Broadwell</a> A comprehensive list of real live examples on Servant Leadership. I recommend reading Leaders Eat Last beforehand.</p><p><strong>General concepts/good to know</strong></p><p><a href="https://www.amazon.de/Scrum-Doing-Twice-Work-Half/dp/1847941109/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=3GSQ9VKJXCOMI&amp;dchild=1&amp;keywords=scrum&amp;qid=1598355993&amp;sprefix=scrum,aps,172&amp;sr=8-3&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=468d39402273e2433362745b00f20095&amp;language=de_DE">Scrum: The Art of Doing Twice the Work in Half the Time</a> A very good handbook applying SCRUM and also being able to explain the benefits of agile methods to non-tech peers. Even worth a read if you are already an experienced practitioner.</p><p><a href="https://www.amazon.de/Innovators-Dilemma-Revolutionary-Change-Business/dp/0062060244/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=22386MILYLG8V&amp;dchild=1&amp;keywords=the+innovators+dilemma&amp;qid=1598356046&amp;sprefix=the+innovators+dilemma,aps,162&amp;sr=8-4&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=e7bea3dfd763cc68583769fbfa35b077&amp;language=de_DE">The Innovator’s Dilemma: The Revolutionary Book That Will Change the Way You Do Business</a> The fundamentals behind the heavily cited theory of disruption. The phrase is a bit overused in my opinion and having a good grasp of this basic concept in tech will carry you a long way.</p><p><strong>Biographies</strong></p><p>These biographies are in my opinion more on the “nice to have”-side than necessary reading. Each will provide you with details into a really well-performing organization and a unique style of tech leadership. The key takeaways: 1. You can have a vastly different style and still be effective and successful. 2. You can follow the model of servant leadership, although you are not perceived as a nice guy.</p><p><a href="https://www.amazon.de/Elon-Musk-Billionaire-SpaceX-Shaping/dp/0753557525/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=3IPE7DFR5R6N&amp;dchild=1&amp;keywords=elon+musk&amp;qid=1598356099&amp;sprefix=elon+musk,aps,167&amp;sr=8-5&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=dda7699b7b205c8a940fa71237626254&amp;language=de_DE">Elon Musk: How the Billionaire CEO of SpaceX and Tesla is Shaping our Future</a></p><p><a href="https://www.amazon.de/Steve-Jobs-Exclusive-Walter-Isaacson/dp/034914043X/ref=as_li_ss_tl?__mk_de_DE=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;crid=1PY4FM6BWAC9Y&amp;dchild=1&amp;keywords=steve+jobs&amp;qid=1598356147&amp;sprefix=steve+jobs,aps,165&amp;sr=8-4&amp;linkCode=ll1&amp;tag=rabattzauber-21&amp;linkId=625e472ca1200365fc8345f2873f81d5&amp;language=de_DE">Steve Jobs: The Exclusive Biography</a></p><p><a href="http://the%20everything%20store:%20Jeff%20Bezos%20and%20the%20Age%20of%20Amazon/">The Everything Store: Jeff Bezos and the Age of Amazon</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f6d9510ae5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[39 pieces of (unsolicited) advice for Software Engineering Managers]]></title>
            <link>https://medium.com/@johanneshansen/39-pieces-of-unsolicited-advice-for-software-engineering-managers-1d5b59f26bbc?source=rss-19752d572932------2</link>
            <guid isPermaLink="false">https://medium.com/p/1d5b59f26bbc</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Johannes Hansen]]></dc:creator>
            <pubDate>Fri, 07 Aug 2020 11:38:18 GMT</pubDate>
            <atom:updated>2020-08-13T19:47:01.865Z</atom:updated>
            <content:encoded><![CDATA[<h3>39 pieces of unsolicited advice for Software Engineering Managers</h3><p>Recently, I turned 39 during a global pandemic and had some time to reflect on what I learned during my time as a Software Engineering Manager (i.e. someone who manages a team of Software Engineers or even multiple teams). Much of it was acquired during the last 12 years and especially while building <a href="https://www.aviatar.com/">AVIATAR</a> for Lufthansa.</p><p>The following are 39 pieces of completely unsolicited advice for Software Engineering Managers — present and aspiring. This post is inspired by the great <a href="https://kk.org/thetechnium/68-bits-of-unsolicited-advice/">Kevin Kelly</a>.</p><figure><img alt="Software Engineering" src="https://cdn-images-1.medium.com/max/1024/1*0G1nuf0FmKw2ZN764hCZfw.jpeg" /></figure><p><strong>Software Engineering</strong></p><p>(1) Add some slack for technical debt. Technical debt is real. If you don’t account for it, sooner or later you will be treading water (i.e. declaring technical bankruptcy). Have a fixed amount of work (e.g. 10% or 15% of capacity) dedicated to paying back technical debt during each iteration and adjust if necessary.</p><p>(2) Use release frequency to measure speed and productivity. Story points are not a good measure. Lines of code are even worse.</p><p>(3) <a href="https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339/ref=sr_1_1?crid=2N7GPEN0P84RK&amp;dchild=1&amp;keywords=accelerate&amp;qid=1594823318&amp;sprefix=accelerat%2Caps%2C346&amp;sr=8-1">Accelerate</a> is a precious and helpful book. Read it.</p><p>(4) Create an environment where engineers get quick and visual feedback on their work.</p><p>(5) Introduce <a href="https://trunkbaseddevelopment.com/">Trunk Based Development</a> as it is probably the biggest lever to increase overall productivity.</p><p>(6) Make developers write their own tests. Tests should mainly be automated and run at every build. The time for testers is over.</p><p>(7) Employ (some) Software Engineers for operations. They are great at reducing tedious manual work by automation. Google calls it <a href="https://landing.google.com/sre/sre-book/chapters/eliminating-toil/">eliminating toil</a>.</p><p><strong>What to build / Product Management</strong></p><p>(8) Build only what cannot realistically be purchased or used. Modern software engineering resembles orchestration more than actual building.</p><p>(9) Avoid the <a href="https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X/ref=sr_1_1?crid=3P6B0NXW2K5VT&amp;dchild=1&amp;keywords=build+trap&amp;qid=1594823367&amp;sprefix=build+trap%2Caps%2C242&amp;sr=8-1">build trap</a> and get as close to a problem as possible and try to deeply understand the nature of the problem. No one else will do this for you. Also, read the book.</p><p>(10) Use the scientific method in problem space/user research — everything is an assumption until proven right (or better yet, wrong).</p><p>(11) Never rewrite working software from scratch unless you have a really good reason to do so. Not being able to understand the code is not a good enough reason. <a href="https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/">Source</a></p><p><strong>Organizational Structure</strong></p><p>(12) Employ product-driven organizational design as it is the best choice despite its trade-offs.</p><p>(13) Use the concept of self-organization only in mature teams. Self-organizing teams are enabled by experience. A bunch of entry-level engineers need more guidance, process, and structure.</p><p>(14) Move tasks/scope not people between teams. This ensures team dynamics work in your favor. Credit to Will Larson’s <a href="https://www.amazon.com/Elegant-Puzzle-Systems-Engineering-Management/dp/1732265186/ref=sr_1_1?dchild=1&amp;keywords=will+larson&amp;qid=1594901351&amp;sr=8-1">An Elegant Puzzle</a>. A fascinating read.</p><p>(15) Obey <a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conway’s Law</a>, it is real. From time to time it makes sense to change the organizational structure just to avoid some of the main pitfalls.</p><p>(16) Adhere to the fundamental principle of DevOps: “You build it, you run it, you own it.” It aligns incentives. You develop differently during regular working hours if you might be called on Saturday to fix a problem.</p><p><strong>Process</strong></p><p>(17) Use a textbook SCRUM process as the default. If a team has little cumulative experience it is certainly the best way forward and the easiest to implement. A team that knows what it is doing, can adjust the process accordingly.</p><p>(18) Use awards, belts, praise, leaderboards, or trophies for all kinds of things you want to incentivize that would not be implemented otherwise. Gamification is a powerful tool to incentivize common standards.</p><p>(19) Do not hate on Remote work. If your business is developing software, you already have all the tools to make it happen at your discretion. I was not convinced about this until I was forced to implement it.</p><p>(20) Use the <a href="https://engineering.atspotify.com/2014/03/27/spotify-engineering-culture-part-1/">Spotify Model</a> as a helpful starting point for effective organizational design. It goes into great detail explaining the trade-off between autonomy and alignment.</p><p><strong>Technology</strong></p><p>(21) Use the <a href="https://en.wikipedia.org/wiki/Lindy_effect">Lindy Effect</a> when evaluating technology. Things that have been around for some time, tend to stick around longer in the future.</p><p>(22) Use the labor market when evaluating technology. When you turn to the labor market you need supply. Niche technology might spell trouble later.</p><p>(23) Use a Benefit vs. Complexity analysis when evaluating technology, e.g. does introducing Kubernetes bring enough benefits to justify the effort to run it?</p><p>(24) Let Engineers choose their own tools. Technology standards should be enforced, but this does not include hardware, OS, and IDE’s. Developers are more productive when they can use what they know.</p><p><strong>Software Architecture</strong></p><p>(25) Do not architect for multiple cloud providers. Multi-cloud is a narrative created for corporate IT departments. Choose your cloud provider carefully, but then go all-in on their offering.</p><p>(26) Try to build a simple machine. What does not exist, cannot fail. Credit to <a href="https://freiheit.com/webinars/why-agile-is-not-enough/">Stefan Richter</a>.</p><p>(27) Invest in monitoring. Your monitoring system might be more important than your test suite. <a href="https://www.infoq.com/presentations/linkedin-architecture-stack/">Source</a></p><p>(28) Build complex and reliable architectures out of very stable primitives. <a href="https://www.infoq.com/presentations/linkedin-architecture-stack/">Source</a></p><p>(29) Avoid being the largest user of a certain piece of technology. You want other people to run into scaling issues before you and ensure a decent margin of safety.</p><p>(30) Implement microservices when you scale to multiple teams. They are kind of technical debt, but necessary to retain productivity at scale.</p><p>(31) If you do not plan to scale your team much, just build a monolith. The meaning of this being: Every engineer has a complete overview of the whole codebase. It can also be majestic and saves you some overhead. <a href="https://m.signalvnoise.com/the-majestic-monolith/">Source</a></p><p>(32) Reduce your time to restore. This is often more valuable than adding tests to prevent errors in the first place. <a href="https://www.infoq.com/presentations/linkedin-architecture-stack/">Source</a></p><p>(33) Try to test in production, if possible. There are surprisingly many situations where this is feasible. <a href="https://medium.com/@copyconstruct/testing-in-production-the-safe-way-18ca102d0ef1">Source</a> A coworker jokingly called it: “Only cowards test in staging”.</p><p>(34) Do not spend valuable engineering time on moving cloud workloads to your own datacenters. Cloud costs are nowadays table stakes. <a href="https://twitter.com/zackkanter/status/1269938660423503874">Source</a></p><p><strong>Leadership/Management</strong></p><p>(35) Be a servant leader. Servant Leadership is not modern or new or fashionable, it is simply effective and the best way to manage a software organization. Start with the original <a href="https://erl.ucc.edu.gh/dspace/bitstream/123456789/2989/1/%5BWalther_Ch_Zimmerli%2C__Klaus_Richter%2C__Markus_Holz%28BookZZ.org%29.pdf#page=81">Greenleaf article</a>.</p><p>(36) Provide psychological safety for your team. No one should fear harm when stating their opinion or being who they are at work. This seems obvious, but in reality, it rarely is.</p><p>(37) Measure things important to you. “What gets measured gets managed, what gets managed gets done.” Peter F. Drucker. Also, <a href="https://www.amazon.com/The-Effective-Executive-audiobook/dp/B01N51TCT1/ref=sr_1_1?dchild=1&amp;keywords=peter+drucker&amp;qid=1596799643&amp;sr=8-1">his book</a> is a classic on management.</p><p>(38) Read <a href="https://www.amazon.com/High-Output-Management-Andrew-Grove/dp/0679762884/ref=sr_1_1?dchild=1&amp;keywords=high+output+management&amp;qid=1594824242&amp;sr=8-1">High Output Management</a>. It is the most effective starting point when you want to learn the best practices of day-to-day management.</p><p>(39) Hire the best people you can. Not necessarily the best people in the world, but spent an enormous amount of blood, sweat, and tears in getting (and retaining) the best people possible. It pays off handsomely in the long run. <a href="https://www.joelonsoftware.com/2005/07/25/hitting-the-high-notes/">Source</a></p><p>Have a different opinion or want to add more things? Let me know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1d5b59f26bbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>