<?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 Loïc Masson on Medium]]></title>
        <description><![CDATA[Stories by Loïc Masson on Medium]]></description>
        <link>https://medium.com/@loicma?source=rss-29e48455c620------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kkJDsKkypuskXqP4AZV8Ew.jpeg</url>
            <title>Stories by Loïc Masson on Medium</title>
            <link>https://medium.com/@loicma?source=rss-29e48455c620------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 20:08:16 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@loicma/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[Alternate fiction and non-fiction books]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://loicma.medium.com/alternate-fiction-and-non-fiction-books-38863f51e545?source=rss-29e48455c620------2"><img src="https://cdn-images-1.medium.com/max/2600/0*LKRD7j-KuucpPetv" width="3936"></a></p><p class="medium-feed-snippet">After putting back &#x201C;Thinking, Fast and Slow&#x201D; ( it seems I am not everyone ) on my bookshelf next to all my other recent non-fiction books&#x2026;</p><p class="medium-feed-link"><a href="https://loicma.medium.com/alternate-fiction-and-non-fiction-books-38863f51e545?source=rss-29e48455c620------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://loicma.medium.com/alternate-fiction-and-non-fiction-books-38863f51e545?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/38863f51e545</guid>
            <category><![CDATA[fiction]]></category>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[books]]></category>
            <category><![CDATA[nonfiction]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Tue, 20 Feb 2024 13:57:09 GMT</pubDate>
            <atom:updated>2024-02-20T13:57:09.942Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Create a work-life bridge]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://loicma.medium.com/create-a-work-life-bridge-fb77f01411bb?source=rss-29e48455c620------2"><img src="https://cdn-images-1.medium.com/max/2600/0*XHKw6aWG5yIyTiJ5" width="6000"></a></p><p class="medium-feed-snippet">How to connect work and personal life</p><p class="medium-feed-link"><a href="https://loicma.medium.com/create-a-work-life-bridge-fb77f01411bb?source=rss-29e48455c620------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://loicma.medium.com/create-a-work-life-bridge-fb77f01411bb?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb77f01411bb</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[health]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sun, 22 Oct 2023 07:33:40 GMT</pubDate>
            <atom:updated>2023-10-22T07:33:40.337Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to migrate to “Enhanced Input Actions” in Unreal Engine 5.2 C++ for beginners]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://loicma.medium.com/how-to-migrate-to-enhanced-input-actions-in-unreal-engine-5-2-c-for-beginners-a63e9126dd73?source=rss-29e48455c620------2"><img src="https://cdn-images-1.medium.com/max/2600/0*ikE_uBv-8hTu_0qx" width="6720"></a></p><p class="medium-feed-snippet">While following a beginner&#x2019;s course in C++ and Unreal Engine, I got stuck on how to implement the input system.</p><p class="medium-feed-link"><a href="https://loicma.medium.com/how-to-migrate-to-enhanced-input-actions-in-unreal-engine-5-2-c-for-beginners-a63e9126dd73?source=rss-29e48455c620------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://loicma.medium.com/how-to-migrate-to-enhanced-input-actions-in-unreal-engine-5-2-c-for-beginners-a63e9126dd73?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/a63e9126dd73</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[beginner]]></category>
            <category><![CDATA[unreal-engine]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sat, 01 Jul 2023 06:59:05 GMT</pubDate>
            <atom:updated>2023-07-01T06:59:05.115Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[How to (finally) tackle your gaming backlog]]></title>
            <link>https://medium.com/half-dev-half-gamer-half-writer/how-to-finally-tackle-your-gaming-backlog-9ad7b25252d7?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/9ad7b25252d7</guid>
            <category><![CDATA[videogames]]></category>
            <category><![CDATA[passion]]></category>
            <category><![CDATA[lists]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Mon, 03 Oct 2022 16:20:30 GMT</pubDate>
            <atom:updated>2022-10-03T16:20:30.168Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A collection of old computers and gaming console" src="https://cdn-images-1.medium.com/max/1024/0*G8LL4UoHXPF0VNrF" /><figcaption>Photo by <a href="https://unsplash.com/@lorenzoherrera?utm_source=medium&amp;utm_medium=referral">Lorenzo Herrera</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>Disclaimer: playing video games should be a pleasure, not a chore. <br>This post is intended for people who want to feel progress towards their backlog instead of always returning to comfort games.</em></p><p>You just have beaten the final boss, and now the final cinematic is concluding the story. As soon as you exit the game, an existential crisis is looming. Time to say goodbye to the characters and the world you got attached to.</p><blockquote>What should I play next?</blockquote><p>Your screen shows you this cornucopia of abundance, your game library—a library accumulated from years of steam sales, humble bundles, and lack of time.</p><p>I faced this &quot;issue&quot; earlier this year. Many series of games I never managed to get around to playing, but I wanted to for a long time, like hitman, dark souls etc.</p><h4>My tip— having a backlog of games that I am looking forward to</h4><p>I came up with a simple system; when I play a game and have a craving to play another one, I just put it on a list.</p><p>Once my current game is <strong>finished</strong>, I proceed to the next one.</p><p>Simple right?</p><p>My current to-play list — with the estimated time they would take to finish and their genre :</p><ul><li>Deathloop — 23 hours — Action FPS</li><li>Control — 24 hours — TPS Action Adventure</li><li>Thronebreaker — 36 hours — Card game RPG</li><li>God of War — 32hours — Action Adventure RPG</li><li>Oblivion — 85 hours — RPG</li><li>Crusader Kings 3–172 hours — Simulation Strategy</li><li>Horizon Forbidden West — 60 hours — Open-World RPG</li><li>The Last of Us — 16+30 hours — Action Adventure</li><li>Diablo II — 47 hours — Hack&amp;Slash</li><li>Stellaris — 58 hours — Strategy</li><li>Diablo III — 43 hours — Hack&amp;Slash</li></ul><h4>What is a finished game?</h4><blockquote>Video-games are experiences.</blockquote><p>You can move on if you feel you got the most out of it.</p><p>A concrete example, I had this game on my list, <a href="https://store.steampowered.com/app/895870/Project_Wingman/">Project Wingman</a>. But after passing the tutorial and the 1st mission, I realized I don&#39;t like plane games. <br>For me, there was nothing else to experience. Or at least nothing positive.</p><p>If the experience you are looking for is to have 100% achievements, then go for it!</p><h4>Shuffle the list to introduce a variety</h4><p>If you played all the Call of Duty in a row, do you think you will be able to enjoy the latest entry as much? Or would you be fed up?</p><p>Once in a while, I revisit my backlog list to see if this order makes sense.<br>I ensure a good mix between action, strategy, AAA vs Indie and other criteria.</p><p>I do have exceptions. For example, I played all the dark souls in a row, as I wanted to experience them in one go.</p><h4>Building anticipation for the next game(s)</h4><p>Studies have shown that we can get as much happiness from the anticipation of the experience as the experience itself.</p><p>When I look at my list, I get excited to finish my current game as I am looking forward to playing the next one. And it builds anticipation for the entire inventory.</p><p>It creates a <strong>virtuous </strong>circle.</p><h4>Parting thoughts</h4><p>There is not enough time to play all the games ever made ( or that will be created). The same applies to movies, books, etc.<br>There is no right or wrong way to handle your backlog; my way is the one that is currently fitting my schedule and how much time I spend playing video games. And you should find your own.</p><p>I am interested in hearing your thoughts!</p><p><strong>Further reading:</strong></p><p><em>Gaming Backlog</em><br><a href="https://kotaku.com/how-to-chip-away-at-a-massive-games-backlog-1845794480">https://kotaku.com/how-to-chip-away-at-a-massive-games-backlog-1845794480</a><br><a href="https://www.digitaltrends.com/gaming/video-game-backlog-spring-cleaning/">https://www.digitaltrends.com/gaming/video-game-backlog-spring-cleaning/</a></p><p><em>Anticipation</em><br><a href="https://www.nytimes.com/2022/05/31/well/mind/anticipation-happiness.html">https://www.nytimes.com/2022/05/31/well/mind/anticipation-happiness.html</a><br><a href="https://exploringyourmind.com/anticipated-happiness/">https://exploringyourmind.com/anticipated-happiness/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9ad7b25252d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/half-dev-half-gamer-half-writer/how-to-finally-tackle-your-gaming-backlog-9ad7b25252d7">How to (finally) tackle your gaming backlog</a> was originally published in <a href="https://medium.com/half-dev-half-gamer-half-writer">Half dev, half gamer, half writer</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One-page rule.]]></title>
            <link>https://loicma.medium.com/one-page-rule-6747f44d2e19?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/6747f44d2e19</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[to-do-list]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sun, 22 May 2022 13:51:09 GMT</pubDate>
            <atom:updated>2022-05-22T13:51:09.488Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a massive fan of note-taking and to-do lists to know what I should focus on the current day or week.</p><p>Before, I used paper, but I was looking for something more modern that could also be an e-reader.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jc8mhyRHagflJ9EdcK_3MQ.jpeg" /><figcaption>Onyx Boox Air with Lamy pen</figcaption></figure><p>Even though I have an unlimited number of pages with this device, I decide to be strict with how much I can have there. With just a glance, I want to know which priorities I have.</p><h3>One-page rule</h3><blockquote><em>Whatever I do, my task list shall never exceed one page!</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2phh3F48tXH9x3-6WpLGUw.png" /><figcaption>The template I am using</figcaption></figure><h3>If I have space</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F9heP5yfrvuYgCwW4oN%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F9heP5yfrvuYgCwW4oN%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F9heP5yfrvuYgCwW4oN%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/ee3b61dced1753b798a4cd1b93f5610d/href">https://medium.com/media/ee3b61dced1753b798a4cd1b93f5610d/href</a></iframe><p>If something comes up, and I have space, it is easy; I add it there.</p><p>I might reorganise it if it has more priority than other tasks.<br>Either by moving things up and downs or adding numbers next to each item according to their priorities.</p><h4>Where do I add it?</h4><p>I have three sections, the work, the WIP and the daily area.</p><h4>Work</h4><p>I write on top of the page the focus for the week, so I know if there is one thing I should accomplish this week, it is this one.</p><blockquote>E.g. Prepare presentation for company weekly.</blockquote><p>This section could include just gibberish that I write while in a meeting to remember to do it afterwards.</p><blockquote>E.g. Contact X about Y. Organise this meeting.</blockquote><p>Looking at this work area gives me easy access to all the threads I need to follow. I can then jump straight back to one of them.</p><h4>WIP</h4><p>Items that I already invested some amount of work into.<br>Reasons they are in the WIP section:</p><ul><li>Something more pressing came up</li><li>Waiting for a design/product answer on a topic</li><li>Waiting for code review</li></ul><h4>Daily</h4><p>I have to prepare my dailies in advance to provide meaningful updates to my team. I also use the dailies to convey any organisation-wide news.</p><h3>If I don’t have space</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohs7IbZdguego5Jeg%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohs7IbZdguego5Jeg%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3ohs7IbZdguego5Jeg%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="435" frameborder="0" scrolling="no"><a href="https://medium.com/media/1f2b590f433ecf5da78495af7e1f466c/href">https://medium.com/media/1f2b590f433ecf5da78495af7e1f466c/href</a></iframe><blockquote>Two choices:<br>1. Do one of the tasks<br>2. Remove one of the tasks</blockquote><h4>Doing tasks</h4><p>Maybe there is a small win on my task list I can do.</p><p>Maybe someone I was waiting for an answer has time now, and I can finish one of the blocked WIP tasks.</p><p>Or finally, the time to get focus time to remove one of them.<br>When I finish the previous task, I can add the new one.</p><blockquote>Efficient to give you a sense of urgency if you were postponing a task.</blockquote><h4>Removing tasks</h4><p>Something <strong>HAS </strong>to go. <br>Balance everything you have and which one would be the most impactful.<br>Then let it go.<br>If it is essential, it will come again later anyway.</p><blockquote>Strengthen your discipline to only pick the most impactful tasks.</blockquote><h3>No cheating allowed!</h3><p>Writing the tiniest letter ever will only get me so far. If I catch myself doing that, if it is because I can’t decide on what I need to remove. And I need to be more strict.</p><blockquote>You are your worst enemy here.</blockquote><h3>Conclusion</h3><p>This method has been handy for me as it narrows my focus to what matters the most.<br>Of course, you have to live with all the tasks you dropped along the way.</p><p><em>Please let me know what you think of this method. <br>And share your best tips to handle your to-do list.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6747f44d2e19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My first few months as an Engineering Manager]]></title>
            <link>https://medium.com/codex/my-first-few-months-as-an-engineering-manager-d49594930b14?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/d49594930b14</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sat, 14 May 2022 12:39:14 GMT</pubDate>
            <atom:updated>2022-05-14T12:39:14.331Z</atom:updated>
            <content:encoded><![CDATA[<p>A few months ago, I transitioned from a Front End developer to an engineering manager at <a href="https://www.happeo.com/">Happeo</a>. Here is a collection of my thoughts.</p><figure><img alt="People standing at a peak of a mountain with no horizon in sight" src="https://cdn-images-1.medium.com/max/1024/0*EeeMzDgPO7AD0glK" /><figcaption>Photo by <a href="https://unsplash.com/@matthewwaring?utm_source=medium&amp;utm_medium=referral">Matthew Waring</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Context</h3><p>I always felt as much gratification when developing a new feature, helping a teammate, or contributing to a successful project. Overall I worked hard not just to deliver my work but to help improve the work of the team.</p><p>When my team lead left to join another company, I asked about the possibility of replacing him. After voicing my interest and an internal interview (a leadership presentation and an architecture diagram), I got offered the promotion.</p><p>At the same time, we were transitioning to more “focused” teams. <br>People would organise themselves in cross-functional teams with ownership of areas of the product and the associated codebase.</p><p>An engineering manager at Happeo to act as the technical representative of the team in collaboration with the product lead and the design lead.</p><blockquote><strong>Me in a new role <br>+ <br>A New team <br>+ <br>People who never worked together before <br>=<br> Catastrophe?</strong></blockquote><h3>First steps</h3><p>Before moving to the role, one important step was to ensure I would get support from my manager and other engineering managers. I was receiving tips and advice from people who have been crucial to speeding up the transition And way less stressful since it can act as a safety net.</p><p>The first thing I did was ease the team and make sure the transition from developer to a manager was smooth. I am glad that no one contested and that the team was pretty satisfied to have someone internally rather than a new person.</p><p>My team would be composed of two front-end, two back-end developers, one designer and one product manager. As we formed, we decided on our ways of working together. We settled on one weekly lightweight planning session, dailies and retrospective every three weeks.</p><h3>What changed: Meetings</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FUJS4fUKBaTc8o%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FUJS4fUKBaTc8o%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2FUJS4fUKBaTc8o%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="183" frameborder="0" scrolling="no"><a href="https://medium.com/media/bcfaaa5cf4f66c91a2834d6f46e1859c/href">https://medium.com/media/bcfaaa5cf4f66c91a2834d6f46e1859c/href</a></iframe><p>I know it is a common trope when moving from a developer role to a managerial position. But I went from an average of 7 hours per week to around 20hours per week. While still needing to be hands-on and have relevant opinions in technical conversation.</p><p>Another aspect that changed was that I am now the one to organise most of the meetings. I am attentive to who <strong>REALLY </strong>needs to attend and who needs to read the notes of the sessions. It is essential also to provide a schedule for the meeting so people don’t come “just in case”.</p><p>But overall, if I attend a one hour meeting that saves my teammates five hours, I save four hours for my team!</p><h3>What changed: Interaction with people</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FFgG0mlNs5B0CknOf7w%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2FHannahWitton-FgG0mlNs5B0CknOf7w&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2FFgG0mlNs5B0CknOf7w%2Fgiphy.gif%3Fcid%3D790b76119350fd7de8272a355505855cc92048623de2aed2%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="245" frameborder="0" scrolling="no"><a href="https://medium.com/media/f25d9ea573c641cf702e6251ef2ee8b9/href">https://medium.com/media/f25d9ea573c641cf702e6251ef2ee8b9/href</a></iframe><h4>One on one</h4><p>I had never been on this side of the table before; a new thing for me to learn.</p><p>I asked the other engineering manager how they were managing them.</p><p>The three main points I got:</p><ol><li>They should be at a regular interval, two weeks being the most common rhythm.</li><li>They are NOT a project status update.</li><li>Have a rolling document like a google doc where you write your notes at each meeting. This way, you don’t forget to make action points and follow through.</li></ol><p>Those meetings are going quite well with those simple rules.<br>Some days, I don’t have a particular topic, so we chat about personal life or coding, like new trends and which ones we could use at work.</p><h4>Grow people</h4><p>I have now six engineers to aid in orienting their careers and make them achieve their goals. To grow people doesn’t mean teaching them or being better than them. But it is to be an <strong>enabler </strong>and <strong>connect the dot.</strong></p><p>For example, if one project is coming up and fits an area one of my reports wants to learn/improve, I can nudge them there. I can also encourage pair programming, prototyping or developing POC and allocate time for them.</p><h4>A lot of cheerleading</h4><p>I feel like a pom-pom girl some days. But a happy team is a high-performant team and a more enjoyable one to work with.</p><p>Developers are bad at evaluating the impact of their work and how positive the effects are. You tend to forget the bigger picture when you start immediately working on the “next” thing.</p><p>I try to be honest and encourage people for the little things.<br><em>Did someone share a lovely snippet of code?</em><br><strong> Good job; looks useful!</strong><br><em>Someone else was proactive and noticed an issue in requirement? </em><br><strong>Good catch; thanks for saving us time!</strong><br>The little things compound fast.</p><h4>Hiring strategy</h4><p>I am also responsible for growing the team. While I already was part of the interview process, I had to take care of the entire end to end flow.</p><p>I am involved in reviewing the resumes up to sending the final offer.</p><h3>What changed: Commitment</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F2AQQWVCTtxuTwBvi9o%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F2AQQWVCTtxuTwBvi9o%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F2AQQWVCTtxuTwBvi9o%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/17d4923309cbd947681464e2d23ed32b/href">https://medium.com/media/17d4923309cbd947681464e2d23ed32b/href</a></iframe><h4>Aligning with product</h4><p>You need to align with the product vision of your team, both short term and long term. This way, you can always include tech debt along with feature work. <br>To enable that, you need a clear line of communication with your product manager ( or owner ) and settle on how you will agree on those topics.</p><p>In the team, we agreed on a 3 phases process before implementation.</p><p><strong>Phase 1</strong></p><p>Is research on problems, competition, benchmarks etc.<br>Done by-product<strong> lead</strong>, <strong>engineering lead</strong> and <strong>design lead.</strong></p><p><strong>Phase 2</strong></p><p>Is sharing that with the team, answering questions and together creating solution options.<br><strong>Leads</strong> + any other <strong>team member</strong> wanting to join.</p><p><strong>Phase 3</strong></p><p>Is tech research, POCs, architecture, wireframes.<br><strong>Leads</strong> + any other <strong>team member</strong> wishing to join.</p><p>We acknowledge that projects will always have unknowns, so projects are not linear. If needed, we can go back to phase 1 even after starting implementation.</p><p>We aim to have an alpha as soon as possible to reduce the unknown unknowns.</p><p>After a few successful releases, you start to build trust within the team and the organisation.</p><h4>Time management and workload</h4><p>We have some slots meant to be meetings-free to allow an extended period undisturbed. But it is only half the solution, as the time needs to be spent the most efficiently possible.</p><p>Engineers’ time is mainly spread out into three domains, bugs, reviews and feature work.</p><p>For <strong>bugs</strong>, I help groom them to have all the necessary elements to reproduce them. I try to find clues to know which team member would be the most appropriate to tackle it.</p><p>For the <strong>PRs</strong>, I improved the PR template so we would always have test notes, a checklist of regularly missed items, and screenshots before/after if a visual change is present.</p><p>For <strong>features</strong>, with the steps mentioned above, everyone would have had the chance to ask questions and challenge requirements.</p><p>Then, to provide value most quickly, we try to share our work with our teammates. That way, we can receive feedback and always be on track and in the correct direction.</p><h3>First successes</h3><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fa0h7sAqON67nO%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fa0h7sAqON67nO%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2Fa0h7sAqON67nO%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/ab38f4d6331ea3d9fbc2f1d6919794f0/href">https://medium.com/media/ab38f4d6331ea3d9fbc2f1d6919794f0/href</a></iframe><p>After two months in the role, I started to notice positive trends.</p><ol><li>More happiness, people were more casual, often smiling and joking quite a lot.</li><li>More ownership, people suggested improvements to the process and loved the democracy that reigned in the team.</li><li>With more alignment, all the disciplines ( front-ends, backend, design, product ) felt like they were on the same page and knew the general direction.</li><li>More quality, The project my team was working on was on track and had a successful alpha and beta. The confidence in the quality of the code and the project’s impact was certain.</li></ol><p>People were jelling together and were happy to be part of the same team. And they felt aligned.</p><h3>Miscellaneous</h3><p>Random things I noticed.</p><h4>Multitasking</h4><p>Some days my time not in meetings is only an hour. An hour is a concise amount of time to squeeze everything.<br>I then had to multitask: answer questions on the side, test what I was working on, etc.<br>It does impact the quality, both for the meeting I am attending and the current work I am doing.</p><p><em>Sidenote</em><br><em>A weird side effect is that I feel like I have a worse memory than before.</em></p><h4>Focus on and off</h4><p>When I do have focus time, even 20 min, I can almost immediately reach a flow state. <br>Which sometimes, was difficult for me if I had 4 hours in front of me.<br>It is a nice side effect :)</p><h4>Type of tasks</h4><p>I never work on feature work or any work with a fixed date to be finished. <br>I prefer to work on bugs, improvement and help my team in other ways. Focusing on the important but not urgent.</p><h4>Conclusion</h4><p>As a scale-up Happeo, my team will metamorphose itself in a few months. New people will join, and others will go to other teams.<br>I always felt at odds with “just” coding, but right now I feel I am where I am supposed to be in my career.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d49594930b14" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/my-first-few-months-as-an-engineering-manager-d49594930b14">My first few months as an Engineering Manager</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“Me-time” For Software Engineers]]></title>
            <link>https://medium.com/codex/me-time-for-software-engineers-951500578390?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/951500578390</guid>
            <category><![CDATA[focus]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[software]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sun, 06 Mar 2022 09:16:54 GMT</pubDate>
            <atom:updated>2022-03-06T09:16:54.019Z</atom:updated>
            <content:encoded><![CDATA[<h3>How to tap into what you truly believe in</h3><blockquote>If only I had two hours to focus on that, how good would it be.</blockquote><p>How often did you have a great idea that you wanted to try out, but you or your team didn’t have the availability to take it?</p><p>Or this deprecated package that has been nagging you for ages.</p><p>Or a command being frustratingly slow.</p><p>Imagine your next meeting is gone, and now you have 2 hours to work on one of those? No strings attached, no one to argue something else is more important, <strong>true liberty</strong>. What would choose to do?</p><p>Those are the most memorable moments in my career, and unfortunately, they mostly happened in my free time/overtime.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Bk18cjYmhMDeiOBh" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>What kind of tasks are good candidates for “me-time”</h3><p>Not all tasks are a good fit for me-time.</p><p>You need a goal, and you should have all the pre-requisites before starting.<br>You shouldn’t need to ask another developer, designer or administrator to provide something to you.</p><h4>Experiment and learn new things</h4><p>Learn and explore cutting edge techniques.<br>You have heard of this hot new library that claims to be four times faster than what your project currently has.</p><p>Go for it! Create an experiment branch or repository and see how far you can go in a few hours. Also good to share with your colleagues what you learned along the way.</p><h4>Improve the existing codebase</h4><p>Your current stack is good, but somehow some rough edges are bothering you.<br>Consistency is missing in some places.<br>Tests do not cover this in the code.<br>Comments are outdated.</p><blockquote>I find those taks therapeutic, like washing the dishes.</blockquote><h4>Add some automation</h4><p>Automation provides a sequence of high quality, repeatable and documented tasks. It removes time spent on the wrong thing.</p><h4>Investigate an odd behaviour somewhere</h4><p>You have those errors so common in your terminal that all ignore them.<br>It is time to investigate if it is a legit warning or something you can forget.</p><h4>Last-mile on a feature to give it some polish</h4><p>You managed to do 80% of your project, and the deadline is already here.<br>Thankfully you delivered the most value. The rest will mostly linger and stay under “Phase 2”. But among the remaining 20%, there was a feature you think was fantastic or worth it.</p><h3>How to get more of those moments</h3><h4>As a developer</h4><p>Emphasize you want to do what you were hired for, to make high-quality software.</p><p>Build the trust that you need for “me-time” to become commonplace.</p><p>Push to experiment with those dedicated time frames and measure their success. Show the value of those tasks.</p><p>E.g. how much time did we save, benefits of new libraries or new versions</p><h4>As a manager</h4><p>An engineer frustrated won’t stay in the company. Engineers are more expensive to hire than retain, so your team satisfaction is your priority.</p><p>Make sure your team feels solid ownership of their code. You are more willing to maintain your own home than a rental place.</p><p>Plan for the unexpected by having enough buffer time for feature work. If this buffer time is unused, you can use it for general improvement.</p><p>It is your job to explain the importance of that kind of work to the rest of the company. And ensure every discipline is aligned with what you are trying to achieve.</p><h3>Conclusion</h3><p>I believe that people deep down know what they should do or work on. Why hire smart people to tell them what to do? Just listen to them.</p><p>One day, I hope that no engineers will have to justify why they need to spend some time on things that “don’t bring” value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=951500578390" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/me-time-for-software-engineers-951500578390">“Me-time” For Software Engineers</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One Of The Things I Love About Software Development #1 — Diversity Of Domain]]></title>
            <link>https://medium.com/the-shadow/one-of-the-things-i-love-about-software-development-1-diversity-of-domain-e3fcac2033d0?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3fcac2033d0</guid>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Sun, 23 May 2021 20:37:29 GMT</pubDate>
            <atom:updated>2021-05-23T20:37:29.671Z</atom:updated>
            <content:encoded><![CDATA[<h3>One Of The Things I Love About Software Development #1 — Diversity Of Domain</h3><h4>I started a series named <a href="https://loicma.medium.com/one-of-the-things-i-hate-about-software-development-1-the-word-asap-25e68ba77ca3">“One of the things I hate about software development”</a>, and it seemed only fair to balance it with things I love in this industry.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h9nLCEYivhkrG6E5" /><figcaption>Photo by <a href="https://unsplash.com/@kazuend?utm_source=medium&amp;utm_medium=referral">kazuend</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><blockquote>I love the diversity you can find in Software development.</blockquote><p>In five years, I worked in the music industry, blood analysis, genetics and internal communications.</p><p>And I am not a professional musician, nor a doctor and not a specialist in intranets.</p><p>I am incredibly thankful for all those companies that allowed me to learn so much in such a short amount of time.</p><p>When you work as a software developer writing code is a mean to an end. The software you are building has no value until it improves, fixes, or solves one or many of the business problems.</p><p>But without understanding the domain you are in, you are not a driving force; <strong>you are just a blocker for people who know better.</strong></p><h3>Diversity of domain — a blessing or a curse</h3><p>The diversity of domains in Software development is exciting, and you can even explore your own interest.</p><p>While domain diversity is not only in the software industry, other profession like politicians, journalists, designers, etc., also have this opportunity.</p><p>But software engineers have to go to a deeper level to get their information to do their work. For example, if you work on a guitar tuner, you need to learn about sounds, frequencies, guitars, notes, and music in general.</p><p>(if you are curious, you can check this excellent <a href="https://jonathan.bergknoff.com/journal/making-a-guitar-tuner-html5/">link</a> on how to create a guitar tuner)</p><p>We are in a fast-moving industry, and adding to that, we have to learn a new domain of expertise every time we switch company can be daunting.</p><p>I recommend first to be humble. It isn’t easy to go from an expert in your previous niche domain to a beginner in another. It will take few weeks to few months to get a good grasp on what is happening. How to approach a new domain</p><h3>Ask questions</h3><p>It is intimidating when you are in a meeting room full of people using specific jargon and seeing everyone else nodding.</p><p>But don’t be scared to ask; sometimes, people forget that you are from outside their bubble and don’t know all the acronyms. You might even help the shy people in the room who didn’t feel it was important to ask.</p><p>If you don’t feel courageous, send an email after the meeting. Less intimidating, and you still get an answer!</p><p>On this <a href="https://gist.github.com/klaaspieter/12cd68f54bb71a3940eae5cdd4ea1764">matter</a>, I couldn’t agree more with Elon Musk.</p><p>Another important aspect is to challenge the current way of doing if it sounds weird or counterproductive.</p><p>It is effortless to work in automatic mode, put the blinkers on and do things the same way as we always did.</p><p>That’s where you can shine! Ask why, why this way and not that other way? Hopefully, there is a good reason, but it might be that the reason is now long gone, and things should change.</p><h3>Engineers are a crossroad</h3><p>You will be at some point in a meeting with a bunch of people from diverse backgrounds. And they all have a request for you.</p><p>At <a href="https://blueprintgenetics.com/">Blueprint Genetics</a>, it was common to meet with geneticists, laboratory specialists, customer support.</p><p>It gives you a unique insight into how different business unit sees the software you are building. Which issues are they facing? Are they all the same? Do they have conflicting needs? And most important, <strong>how can I help?</strong></p><p>Thanks to your position, you can learn faster and directly from the source — the knowledgeable people.</p><h3>Be curious</h3><p>While you will <strong>accidentally</strong> learn about the domain during your workday, curiosity can drastically improve the quality of your work.</p><p>Deliberate practice to grow your knowledge will also make you more engaged when picking up a new task, and you understand the <strong>WHY</strong> better.</p><p>Use all the good resources you can find online, you can find even in niche domains. Articles, videos or any books you can find can help.</p><p>Of course, you don’t need a PHD in the domain (even though it might help). But you will benefit by being at least comfortable in this field.</p><h3>And then enjoy!</h3><p>I like to think this is a big chance to be in this industry. Can be scary but incredibly rewarding.</p><p>I would have never thought that I could explore the health industry without a fancy degree. But I can do that! and so can you!</p><p>And so much more to still see! Just take a look at <a href="https://www.seedtable.com/startups-helsinki">Helsinki&#39;s</a> trendy startup and the variety of companies.</p><p>So keep on learning!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3fcac2033d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-shadow/one-of-the-things-i-love-about-software-development-1-diversity-of-domain-e3fcac2033d0">One Of The Things I Love About Software Development #1 — Diversity Of Domain</a> was originally published in <a href="https://medium.com/the-shadow">The Shadow</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[One of the things I hate about software development #1 — The word ASAP]]></title>
            <link>https://loicma.medium.com/one-of-the-things-i-hate-about-software-development-1-the-word-asap-25e68ba77ca3?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/25e68ba77ca3</guid>
            <category><![CDATA[best-practices]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Mon, 26 Apr 2021 16:03:15 GMT</pubDate>
            <atom:updated>2021-04-26T16:03:15.741Z</atom:updated>
            <content:encoded><![CDATA[<h3>One of the things I hate about software development #1 — The word ASAP</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mAkY8CxD4QpEsYB1" /><figcaption>Photo by <a href="https://unsplash.com/@brett_jordan?utm_source=medium&amp;utm_medium=referral">Brett Jordan</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Welcome to my new series of things I hate in software development.</p><blockquote>ASAP — As Soon As Possible</blockquote><p>A conversation happening right now on the planet:</p><p><strong>Random stakeholder:</strong> “I need feature X.”</p><p><strong>Naive dev</strong>: “When do you need it?”</p><p><strong>Random stakeholder:</strong> “ASAP.”</p><p><strong>Naive dev:</strong> “But what about Y, Z?”</p><p><strong>Random stakeholder:</strong> “I don’t care; just make it happen.”</p><p>Raise your hand if it happened to you ✋.</p><p>How likely is it that the developer will implement this feature with an incredible level of care and quality?</p><p>Simple, it won’t.</p><h3>The reasons I hate it</h3><h3>ASAP is lazy</h3><p>The person asking you this didn’t bother to provide an actual schedule.</p><p>What kind of scale is it? A day, a week, a month?</p><p>Did they agree with other stakeholders? Are they fighting to get attention from the software team, and asking urgent tasks is their move to do so?</p><p>“ASAP” might be the joker card not to do any of those.</p><h3>ASAP is bad</h3><p>“as possible” translate to “what is the quickest hack you can do to have this feature online now”.</p><p>It is a total disregard to the quality of the feature, the general codebase, or even the value the functionality would provide.</p><h3>ASAP is stressful</h3><p>Ok, you need to do this thing NOW.</p><blockquote><em>Hmm, but what about the others things you were doing? Should you finish these first? Weren’t they important tasks too?</em></blockquote><blockquote><em>What if doing this ASAP task would derail other plans?</em></blockquote><blockquote><em>Can you do more harm than good?</em></blockquote><p>You have a lot of questions and decisions to make, which can add stress.</p><h3>ASAP is wasting time</h3><p>Now you need to ask around if this “ASAP” task is urgent. If it is, then you need to shuffle the current backlog to make it fit. What if there are contradictory priorities? Then you might need to escalate this to someone who can decide for the team.</p><p>Do you know what you didn’t do when you are thinking about those? Some focused work.</p><h3>When is ASAP “ok.”</h3><p>If a fire appears. For example, your software has monumental bugs; no login, payments are failing, etc.</p><p>You do have to look into the matter <strong>immediately</strong>.<br>You were most likely already doing that.<br>Telling you so might be a waste of time and annoy you on top of that.</p><p>Another case will be if you have an unexpected opportunity.<br>Let’s say you are developing a mobile app, and Apple wants to display your app in their Apple store. They need a customized version of your app by the end of the week.</p><p>Those two scenarios are the ONLY ones where it would be ok.</p><p>But there are also <a href="https://blog.hubspot.com/sales/alternatives-asap">better alternatives</a> than using “ASAP”.</p><h3>Less haste, more speed</h3><p>It is tempting to succumb to the dark side, to want to help, and jump straight to fix this urgent issue.</p><p>But remember that whatever mess you will create would be your responsibility.</p><p>It is not ok to compress the deadline by:</p><ul><li>reducing the quality of your work or the codebase</li><li>not creating automatic tests</li><li>skipping manual testing</li><li>working overtime</li></ul><p>The only way to do something faster is to reduce the size.</p><p>The smaller, the quicker.</p><p>If you can’t agree with the stakeholders on removing a part of the feature, then put back your headset, go back to your initial work. You can wait for an actual request that exceeds four letters.</p><h3>Final words</h3><p>I often had to go against my own will to implement those urgent tasks.<br>What I rarely saw is the benefits of stretching myself to do so.</p><p>I prefer to now answer “ASAP” by “ASAD”, <strong>As Soon As it is Done.</strong></p><p>My definition of done.</p><p>What <strong>done </strong>means here:</p><ul><li>value is known and measurable</li><li>the task is well-groomed</li><li>my implementation follows the best practices (tests, clarity, readability, etc.)</li><li>developers review my code</li><li>to ensure no miscommunication happens, I demo the feature</li><li>The feature can be deployed and tested by all parties, the development team included. If everyone agrees to move forward, then it can be deployed.</li></ul><p>You can’t skip any of those.</p><p>If one of the steps “fails”, for example, a review detects a potential issue that lower the value this task is adding, you need to go back to the beginning.</p><p>So be strong! Resist the temptation to hack your way!</p><p><strong>References:</strong></p><p><a href="https://www.targetprocess.com/articles/speed-in-software-development/">https://www.targetprocess.com/articles/speed-in-software-development/</a></p><p><a href="https://softwareengineering.stackexchange.com/questions/178352/how-do-you-balance-between-do-it-right-and-do-it-asap-in-your-daily-work">https://softwareengineering.stackexchange.com/questions/178352/how-do-you-balance-between-do-it-right-and-do-it-asap-in-your-daily-work</a></p><p><a href="https://medium.com/serious-scrum/how-pressure-to-deliver-boils-scrum-with-technical-debt-d95ac872ccaf">https://medium.com/serious-scrum/how-pressure-to-deliver-boils-scrum-with-technical-debt-d95ac872ccaf</a></p><p><a href="https://xkcd.com/844/">https://xkcd.com/844/</a></p><p><a href="https://medium.com/mind-cafe/how-lateral-thinking-can-make-you-more-creative-and-better-at-learning-75a684b10ff">https://medium.com/mind-cafe/how-lateral-thinking-can-make-you-more-creative-and-better-at-learning-75a684b10ff</a></p><p><a href="https://crmbusiness.wordpress.com/2015/02/19/why-rushed-projectscode-doesnt-save-time-and-reduces-quality/">https://crmbusiness.wordpress.com/2015/02/19/why-rushed-projectscode-doesnt-save-time-and-reduces-quality/</a></p><p><a href="https://thehosk.medium.com/how-we-try-to-speed-up-it-projects-and-why-it-doesnt-work-ca3bdc5d7413">https://thehosk.medium.com/how-we-try-to-speed-up-it-projects-and-why-it-doesnt-work-ca3bdc5d7413</a></p><p><a href="https://www.wrike.com/blog/asap-hurts-your-team/">https://www.wrike.com/blog/asap-hurts-your-team/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25e68ba77ca3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Retrospective of my 2021 job search as a Software Engineer]]></title>
            <link>https://loicma.medium.com/retrospective-of-my-2021-job-search-as-a-software-engineer-d29ad6bc769d?source=rss-29e48455c620------2</link>
            <guid isPermaLink="false">https://medium.com/p/d29ad6bc769d</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[helsinki]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[interviews-and-insights]]></category>
            <dc:creator><![CDATA[Loïc Masson]]></dc:creator>
            <pubDate>Tue, 20 Apr 2021 15:43:12 GMT</pubDate>
            <atom:updated>2021-04-23T10:33:24.626Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qOQ2y5zbDfYka7NS" /><figcaption>Photo by <a href="https://unsplash.com/@markuswinkler?utm_source=medium&amp;utm_medium=referral">Markus Winkler</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>2020 was a weird year. 2021 is following its path.</p><p>But for software engineers, it is (almost) the same routine, only with comfier pants at home.</p><p>This article is my retrospective on my job hunt in 2021. You can use this as a guide for your potential job search.</p><p>I am living in Helsinki, Finland and am looking for work only in this area. It is an excellent choice for a software engineer. Helsinki is the <a href="https://ec.europa.eu/commission/presscorner/detail/en/IP_19_2991">most innovative region in the EU</a>, and the <a href="https://www.hel.fi/helsinki/en/administration/enterprises/competitive/international+comparisons/quality-of-life">quality of life is exceptionally high.</a> And if you want to work for a start-up, you will <a href="https://www.seedtable.com/startups-helsinki">find something that interests you</a>.</p><h3>Before looking for a new job</h3><p>It is a good idea to know the reason(s) of the transition to a new position. Are you probing the job market? Been fired, and money is an urgent issue? In need of a change?</p><p>The last one is my situation.</p><p>Time to update my resume, Linkedin and switch “Open for hire” on my profile and get started!</p><h3>What am I looking for?</h3><p>I defined a triangle (<strong>PDT</strong>), people-domain-tech, of which aspects are important to me.</p><h4>The people</h4><p>I want to work with great people who are competent in their position. If I can also get along well with my new colleagues, then perfect!</p><p>Everyone is remote this year still, but I hope we will be back at the office one day. When you are in the office with talented people is when the magic happens.</p><p>You produce values at a <strong>sustainable </strong>pace, work you can be <strong>proud </strong>of with people you <strong>trust</strong>. A team flow state is addictive and the kind of environment I want to be involved.</p><h4>The domain</h4><p>The domain of the company is significant to me. It can be of two categories:</p><ul><li>sounds exciting, like cutting edge genetics, VR, satellites, etc.</li><li>can sound “boring” but has a novel approach to the topic or the execution is well made</li></ul><p>Because even if the idea sounds “cool”, the implementation can be lousy and vice versa.</p><h4>The tech</h4><p>I am not concerned about which programming languages the company is using. I am confident in my abilities to learn. I like to ask:</p><ul><li>which process they are following</li><li>is their technical debt under control</li><li>their test coverage</li><li>deadline philosophy, if they have a sustainable pace or if it is a constant death march</li><li>how they pick, implement and review features. Are they a feature factory, or do they assess how much value they add to their software?</li></ul><h3>My plan</h3><p>I prefer to find a job in a short period. I want to go full speed as much as possible.</p><p>I set myself a deadline: to receive offers around the beginning of March. (spoiler: I was close!). And I sent the first application at the end of January.</p><p>It is essential to be a master in introducing yourself. Sometimes you have to do it in 5–10 minutes, other time in 2 minutes — you need to keep it flexible.</p><h3>Different steps I went through</h3><p>The most common pattern I had when applying to a company was:</p><ol><li>Sending application</li><li>Introduction / Motivation call</li><li>Call with the hiring manager</li><li>Technical assignment</li><li>Technical interview</li><li>Offer</li></ol><p>The order could be different or with extra steps. Interviews will be either on the phone or in video calls due to covid restrictions.</p><blockquote>If you don’t have a webcam at home, you can use <a href="https://www.dev47apps.com/"><em>https://www.dev47apps.com/</em></a><em> and use your smartphone as a webcam.</em></blockquote><p>It is also worth asking for an agenda before any of the interviews.</p><h3>Sending applications</h3><p>You can apply to a company via job listing websites, Linkedin or specific companies website. I looked at startups that were interesting nearby and applied via their Career page.</p><h3>Intro calls / Motivation calls</h3><p>Those calls are usually “easy” because the company wants to gather information for the next steps. It will include a short intro to the company, your current situation and what you are looking.</p><p>It is essential to ask about their hiring process, the number of steps and how long it can take.</p><p>These calls are around 30 min.</p><p>Good practice to review what the company is doing and the job description to be fresh in memory. Also, to ask questions.</p><h3>Call with the hiring manager</h3><p>A hiring manager can have a different role. It can be a recruiter, a team lead, a human resource person. The content of the interview will differ depending on which one it is.</p><p>This interview will focus on the position and what the team you are applying to does in the organisation.</p><p>High-level questions are about your way of working, past experiences, previous roles.</p><blockquote>e.g. How many years of experience with this framework?</blockquote><h3>Team introduction</h3><p>It is a group call with several people, either technical only or a mix of different expertise.</p><p>The interview is about the team’s narrative, their approach and more concrete day to day tasks. The questions here were to pinpoint which kind of team member I was.</p><blockquote>It is vital to stay true to yourself. If you “fail” this step, it might mean this company was not a good fit for you.</blockquote><h3>Technical interviews and assignments</h3><h4>High-level technical interview</h4><p>A high-level interview will focus on your prior knowledge of languages and frameworks. How many years, personal preferences, for which scenario, etc.</p><h4>Low-level technical interview</h4><p>Those kinds of interviews are focusing on more concrete questions.</p><p>How would you code thing A or B? Specific questions about the frameworks you used before.</p><p>Review the job posting since it contains the technical skills the company is looking.</p><h4>System analysis</h4><p>I got this type of exercise only once, but it is worth mentioning here. Some documentation about a fake existing system will be sent ahead of the interview, with current problems and a list of wanted new features. Then you have to think in advance about how you would put it in place.</p><h4>Code pair interview</h4><p>You will connect on a live session for pair coding on a brief exercise. The way you think and communicate is as important as your coding skills.</p><h4>At home technical assignment</h4><p>At home, technical assignment is a common step in the hiring process. Unfortunately, they are not standardised. You will never know what you will get, how long it will be, or even which technologies you will have to use.</p><h4>Code review</h4><p>Those are my favourite technical assignments because they reflect better what you do every day and are short in scope and in time investment. You will either receive a review before the interview or be a live exercise.</p><h3>CEO interview</h3><p>Depending on the type of company you are applying to, you might have an interview with the company’s CEO.</p><p>Don’t neglect those.</p><p>A CEO is a good vitrine on how the company was, is and will be. They will be the best to answer your questions about the company and its future.</p><h3>Tips for sending applications</h3><h4>Apply even if if you don’t have all the requirements</h4><p>You are not a senior? You don’t know X, Y and Z? Apply anyway. Rejection is possible if the company only does basic CV scanning, but you might also pass this step.</p><p>A solid software engineer knows how to learn, about the technologies, about the domain.</p><blockquote>It will be more difficult for a junior developer, but don’t give up!</blockquote><h4>Wave approach</h4><p>I usually do it in two waves, with the third one in reserve.</p><p>1st wave of applications includes all my top choices. I apply to those on the spot, then wait from a few days to a week.</p><p>If I don’t receive any news, I will send a new batch of applications to the other companies that interest me.</p><p>3rd wave is in case I don’t receive enough positive answers after a month or so. I never had to use it. But I still gather a list of potential companies for this case.</p><h4>Send a continuous flow of applications</h4><p>5–8 applications per week is a good amount to send. Keep sending applications even if you are in the process with other companies.</p><p>Companies tend to take between a few days to several months to answer you, and there is no way of knowing. I still receive initial answers from months ago.</p><p>You don’t know if any will accept you during their process, so you have to have other options in the funnel.</p><blockquote>If you get rejected, it is ok to be disappointed, especially if it was your top choice. Ask for feedback; who knows, maybe you will try again to apply there in a couple of years.</blockquote><h3>How to survive technical steps?</h3><p>For a software engineer, these will be the trickiest to pass. They can also be at time be stressful and impacting your self-worth when you are failing at those.</p><p>I only prepare for the low levels interviews, and my past experiences are enough.</p><p>This low preparation was sometimes the cause of rejection. But if the agenda of the meeting doesn’t specify any preparation, the company is at fault..</p><blockquote>e.g. When an interview is supposed to be a team meeting I don’t expect specific Angular questions.</blockquote><h4>At home assignment</h4><p><strong>Choice of technologies</strong></p><p>The choice of technology might be mandatory.</p><p>In this scenario, use well-known frameworks that would fit your needs the best.</p><p>For one assignment, I had to re-learn Python. I decided to use Flask, as I used it in the past, and I have friends who are familiar with it and could assist me.</p><p>If the choice is up to you, don’t go crazy with trying an entirely novel tech stack from what you are comfortable with. But feel free to experiment as well.</p><p>I didn’t have the chance to use Hooks or Context in React before in my current position. While the implementation I did was not excellent, I still passed. And even if I had failed, I would have at least learnt something new.</p><p>Spend time polishing the first assignment, as you can reuse some code for another test.</p><p><strong>During the assignment</strong></p><p>For long assignments, it is necessary to split your tasks well. You can pick a short piece of work if your day has been too exhausting, but you still need to move forward.</p><p>Try to have an actual focus time at home if possible. If you can’t focus, take notes for yourself with a lot of details. When you start, you will go straight to implementation and don’t have to think about how to do it.</p><p><strong>Before submitting</strong></p><p>Make sure you don’t have apparent bugs. Inspect the instructions to be sure you didn’t miss anything.</p><p>For a more significant assignment, I asked friends to review it. Like in a real-life scenario. They often have excellent points, especially if they know the technologies better than me.</p><p>I try to address the most critical or the fastest to fix issues since I can’t spend more time on the assignment.</p><p>Then submit and move on to another assignment.</p><h4>How to manage your time</h4><p>Time management is crucial, especially if you are like me you want to sign a new contract as fast as possible.</p><p>Here is an example of my calendar during the busiest month.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NjsVp2K8pqaeQPjNPN439w.png" /></figure><p>February 2021 — Loïc Masson</p><p>Some weeks were hectic.</p><p>The assignments started to come from the 15th of February, ranging from few hours to few days.</p><blockquote>It is ok to say no to an assignment when it is too long.<em><br>One company’s technical test was three days long.<br>I told them this barrier of entry is too high as I don’t wish to spend that much time when the interview I am interested in is to meet the team.<br>They scheduled a short call with some team members. After that, I was convinced, and I did the assignment (and passed).</em></blockquote><p>My days looked like this:</p><ul><li>do my daily tasks at my job</li><li>have interviews in the middle</li><li>compensate the amount of time I spent in the interview process for my work</li><li>take a nap</li><li>start working on the assignments</li><li>rinse &amp; repeat</li></ul><h4>Don’t neglect your current company</h4><p>You still have responsibilities there. It is ok to have interviews during the workday but compensate for those.</p><h4>Manage your energy well</h4><p>The busiest week, I had around 70 h of work.</p><p>37.5 from my actual job and the rest dedicated to interviews and assignments.</p><p>The thing that saved me was taking a lot of naps.</p><p>One nap after the workday during the week and a couple per day at the weekend. Without those, my focus and productivity would have been much lower.</p><p>Be careful not to burn out; It is ok to have a rest day and not do any additional work after your workday and have free time for your hobbies.</p><h3>How to make a choice when you have many offers</h3><p>It is 1st world problem to have, but a problem nonetheless.</p><p>Sometimes it is a clear cut, but other times they might all be excellent offers. Take a week to reflect on it. You will change your mind a lot. On top of my <strong>PDT</strong> triangle, I made a list of the extra points:</p><ul><li>Do they meet your salary request?</li><li>How far is their office? (one day we will go back to the office)</li><li>How was their interview process?</li><li>Was there a good atmosphere during the interviews?</li><li>Were they answering you in a timely manner?</li></ul><h3>Ask for some time out between jobs</h3><p>I planned a month to relax before starting at my new position. It’s great to have some closure time to breathe and spend on whatever hobby or personal project you have.</p><p>Make sure it is clear for the new company as well. It might be a red flag if the company can’t even delay a new employee joining a few weeks or a month.</p><h3>The outcome</h3><p>I sent my first application on the 26th of January.</p><p>I received the offer from my new company on the 5th of March, and I signed my new contract on the 16th of March.</p><p>Mission accomplished!</p><p>While I am generally satisfied with my search, I did overlook some points.</p><h4>A new level of experience</h4><p>I didn’t expect that five years of experience would make such a positive difference. I guess that when recruiters are reading my resume, I check one more box than usual.</p><p>I received 2–3 times more attention than my previous job search two years ago. It is an excellent problem to have, but it also means I should have sent fewer applications.</p><h4>Remote interviews</h4><p>Due to all interviews being remote and me being at my desk, I could schedule interviews any time. Not having to go to each company’s office for interviews saved a lot of time and hassle.</p><p>But it had the side effect of me scheduling too many interviews.</p><p>Some weeks I had 6–8 interviews. The sweet spot would have been 4–5.</p><h3>Closing thoughts</h3><p>While finding a new job is never an easy task, nor a stressless one, I am pretty happy to be over with it.</p><p>Now I can enjoy a month-long holiday! While the excitement to learn a new domain and a new tech stack builds up.</p><p>I hope you had a great read, and feel free to share your experience with the job search in the software industry!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d29ad6bc769d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>