<?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 Yannick Schutz on Medium]]></title>
        <description><![CDATA[Stories by Yannick Schutz on Medium]]></description>
        <link>https://medium.com/@yann_ck?source=rss-ca99c1c04695------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C4t2q554713kAaX82T1SiA.jpeg</url>
            <title>Stories by Yannick Schutz on Medium</title>
            <link>https://medium.com/@yann_ck?source=rss-ca99c1c04695------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:02:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yann_ck/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[In a week]]></title>
            <link>https://medium.com/@yann_ck/a-journey-to-france-4b7d6b3eded?source=rss-ca99c1c04695------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b7d6b3eded</guid>
            <category><![CDATA[simple-living]]></category>
            <category><![CDATA[minimalism]]></category>
            <dc:creator><![CDATA[Yannick Schutz]]></dc:creator>
            <pubDate>Mon, 09 Jul 2018 13:19:20 GMT</pubDate>
            <atom:updated>2018-07-09T13:20:15.832Z</atom:updated>
            <content:encoded><![CDATA[<p>It has been two years, two years we are looking for a new place to live. A new place that would look more like us, that would allow us to live the life we want for us and for Tom. We knew we wanted to go in France, we knew we wanted to get off the city. We started looking for Burgundy, found nothing that matched us.</p><p>One day, in December, I sent a link to Cloé, a link that would change our life. It wasn’t in Burgundy anymore. I asked Cloé a real simple question: If you could pick, where would you live? Her answer was as simple as the question: By the sea. So I started looking in Brittany. And there it was. That new house, new life was in Brittany. 30 minutes from the coast, back to basics in a small hamlet.</p><p>Time to live a simpler life. Time to take care of ourselves and please ourselves with our own vegetables garden, our own fruit trees. Our own land! But life isn’t good if it isn’t shared. We plan to open a Bed and Breakfast on that land, welcome folks we know, but also share experience with people we don’t know yet.</p><p>It is a huge life change and we cannot do it without being stressed, we are leaving friends behind and jumping into the unknown. This is a big leap of faith but it is all ours. We know we will learn a ton, we know it is not gonna be easy. But should life be that easy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b7d6b3eded" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The effective engineer Notes]]></title>
            <link>https://medium.com/yann-ck/the-effective-engineer-notes-1237df7ed630?source=rss-ca99c1c04695------2</link>
            <guid isPermaLink="false">https://medium.com/p/1237df7ed630</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[soft-skills]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Yannick Schutz]]></dc:creator>
            <pubDate>Tue, 11 Oct 2016 22:20:13 GMT</pubDate>
            <atom:updated>2016-10-11T22:20:13.396Z</atom:updated>
            <content:encoded><![CDATA[<p>I just finished reading <a href="http://www.theeffectiveengineer.com/">The effective Engineer</a> by <a href="https://twitter.com/edmondlau">Edmond Lau</a>. This is a great book to read and wanted to share my notes about it.</p><p>Thanks a lot, Edmond to allow me to share them even if I find they go really in details 😋</p><h4>Adopt the right mindset</h4><h4>Focus on high Leverage activities</h4><p>The book is all about leverage. What it just means is having the more impact on what you do. 80–20 rule.</p><blockquote>Leverage = Impact Produced / Time Invested</blockquote><p>How to make more impact with what you are doing right now?</p><ul><li>Complete in less time</li><li>Increase the impact of the task through changes</li><li>Drop the task if not impactful and move on to a better one.</li></ul><h4>Keep learning</h4><p>You need to keep a growth mindset in order to continue evolving. If you don’t you’ll reach a plateau. If you do you keep more control. Investing in your rate of learning, keep learning everyday even just 1%, get a job that allow you to learn through people, on boarding or autonomy. Increased learning means more happiness</p><ul><li>How to dedicate time for new skills</li><li>20% of time, makers day</li><li>Via side skills useful for main skill</li><li>Read best engineers code</li><li>Write more code</li><li>Ask for code review</li><li>Enroll in class to improve</li><li>Participate in other projects discussions</li><li>What to do?</li><li>Read books</li><li>Learn a new languages</li><li>Learn high demand skills</li><li>Join discussion group or conferences</li></ul><h4>Prioritize Regularly</h4><p>Prioritization is a skill that requires a lot of practice Track all your todos in a single list, always write stuff down to not have to worry. Your estimations will often be wrong and on the road to a goal, you probably will add more items to do. Focus on the goal, on what will produce real value. Keep time to focus on the important and non urgent. Do not let daily interruptions drive our priorities otherwise the non urgent will be lost even if it might produce more value. Protect your schedule by learning to say no and limit what you have in progress. Fragmentation here helps boost productivity. Switching contexts a lot will reduce productivity. Fight procrastination with planning to avoid falling into a moment where you need effort to start something.</p><h4>Execute, Execute, Execute</h4><h4>Invest in iteration speed</h4><p>Moving fast through continuous deployment and fast learning. Invest into time saving tools for your workflow and shorten debugging and validation loops maybe through automation. Master your programming environment by making small improvements and making it yours. Prefer keyboard over mouse, automate workflows through script languages or knowing UNIX commands.</p><p><strong>Master is a process not an event</strong></p><p>To keep the speed high, don’t ignore your non engineering bottlenecks. Value communication and acknowledge that getting approval is slow. Find what the leaders care about and create a safe review and approval process through good coordination. Depending on other people add overhead and friction but it is necessary.</p><h4>Measure what you want to improve</h4><p>Drive progress via metrics. They help focus on the right thing, confirm objectives, guard against regression and measure effectiveness over time.</p><p>Picking the right metrics will help maximize impact. They need to be responsive but robust. They will serve as your north star.</p><p>Instrument all the things, even stuff you don’t need yet. This will add flexibility when trying to define the north star. What does not guide you will be helpful in day to day operation and forensics. Log more just in case.</p><p>Have some numbers internalized. Stuff that are generic and useful to compare to what you get and see if you are totally out of the right order of value.</p><p>Be skeptical about data integrity, it is easy to abuse numbers and make them lie. Never confuse correlation with causality. Have tooling to iterate on the data and expose them soon in the process to detect anomalies. If possible, cross validate.</p><h4>Validate early and often</h4><p>Don’t delay get feedback figure out what’s working. By iterating with small steps, it lowers the effort to validate. Start with the scariest part to demystify the project. This will allow to get valuable feedback early.</p><p>Start by a small prototype to validate and you can even fake parts of it just to provide the feel of what you do.</p><p>Building feedback loops for your decisions will allow you to stop guessing what you are doing and have more confidence.</p><p>AB test your changes for validation, you can then quantify the impact you are making more easily.</p><p>Never have a one person team, this will reduce the feedback and validation. Avoid gigantic reviews and commit early and often. Requesting reviews and accepting the feedback. Test your ideas through discussions with colleagues, Write the API first, a design doc and share the context.</p><p><strong>Do not work in isolation</strong></p><h4>Have better estimation skills</h4><p>Business needs the estimations for long term vision. Adapt and review them often. Do not take estimations for targets. And especially don’t let target change your estimations.</p><p>Provide accurate estimations by decomposing into granular tasks, long estimations hides high risks. Do not let someone else estimate your job. Treat them as probabilities and estimates a task through different angles. If the task is open ended, time box it.</p><p>Even with all this, budget for the unknown, most disasters are due to termites not tornadoes. Keep in mind that a month of work does not mean that it will be done in a month.</p><p>Define clear goals and milestones to avoid feature creep. With business and your team this will bring alignment.</p><p>Reduce the risk by tackling the hard part firsts. Maximize your learning and revisit the estimations.</p><p>Approach rewrite project really carefully, people tend to underestimate due to familiarity with the old project. Also this is where a lot of new features creep in. If you need to add features, it will go in both projects and add time. Keep it incremental.</p><p>Even if you are late, don’t sprint in the middle of a marathon. Productivity decrease with additional hours and you are probably already too late and behind schedule already. Sprinting will lead to burn out, will hurt team dynamics and increase tech debt and communication If you still decide to sprint, make sure people understand why the project slipped so far, develop a realistic plan and timeline and prepare to abandon the sprint if it is useless.</p><h4>Build long term value</h4><h4>Balance quality with pragmatism</h4><p>It happens often that we over invest in quality and lower the value we provide.</p><p>Keep a sustainable code review process that catch bugs early. Increase accountability and build a positive model on how to write good code. Share the knowledge of the codebase.</p><p>Have clear and simple primitives to reduce future maintenance and allow higher productivity in future improvements. Solves the hard problem once and build for reusability around it. Avoid early abstractions that might lead to complexity adding more features.</p><p>How to know about good abstractions? — Find popular abstractions read through them — Look through open source in big companies — Study interfaces of popular API</p><p>Automate testing all your projects to decrease the repetitive work and shortening the path to notice errors. See your tests as some kind of executable documentation of what you wrote. (Still maintain clear documentation)</p><p>Repay technical debt to avoid increased rates on repaying it later. Do not let the debt be out of control and payback the part with the highest leverage.</p><h4>Minimize operational burden</h4><p>Choose boring stacks, embrace operational simplicity. This lower taintenance costs of <strong>complexity</strong>. If you use too many technologies, paradigms and so on, your team expertise gets split into the different systems. This will increase the learning curve for new comers and lower your ability to switch context. You will have your efforts diluted across systems.</p><p><strong>Do the simple thing</strong></p><p>Build systems to fail fast it will help surface issues and allow fixing them faster, slow failing brings troubles debugging and hides causes.</p><p>Automate mechanical tasks over decision making, tackle smart decision automation later, prefer low hanging fruits. We often forget to automate due to lack of time, self interest in the pager rotation about fixing for us not the others, underestimating the frequency and missing the time saving opportunity. Make your batch processes idempotent or at least retryable. Run them more often than expected to surface errors.</p><p>Increase your ability to respond and recover quickly via playbook and operations. Reduce situations where emotions cloud our judgement and simulate failures to be prepared. Plan for the unexpected.</p><h4>Invest in your team’s growth</h4><p>Have a positive and smooth on boarding that will allow to be aligned with your team members, you will achieve more.</p><p>Hiring is everyone’s responsibility, screen for the type of candidates likely to do well on the team and get them excited about the team, missions and culture. Use high signal to noise ration questions and do some kind of starter project. Scan for red flags and match on team culture and code. Do not be afraid of unconventional approaches.</p><p>Design good onboarding process to increase team success. Ramp up engineers as quickly as possible, share the team values and culture and expose engineers to the team’s fundamentals. Integrate the new hires socially in the team to through code labs, talks, mentorship and starter tasks.</p><p>Share ownership of code increase the bus factor and avoid SPOF and bottlenecks. This is achieved by keeping the code readable, rotate type of tasks and projects, documenting all the things and talking about the projects.</p><p>Build collective wisdom through post mortems, pause To reflect on past project and think about what could have been done better Retrospectives will help you detect lack of playbooks and remediation. Ask the five whys and have honest conversations, do not blame and debrief.</p><p>Build a great engineering culture it will pay off, base it on what you just read and be positive.</p><h4>Conclusion</h4><p>Time is our most finite asset and leverage allows us to direct or time towards what matter most</p><h4>Books recommended</h4><ul><li><a href="https://www.goodreads.com/book/show/67825.Peopleware">Peopleware: Productive Projects and Teams</a></li><li><a href="https://www.goodreads.com/book/show/14514115-team-geek">Team Geek: A Software Developer’s Guide to Working Well with Others</a></li><li><a href="https://www.goodreads.com/book/show/324750.High_Output_Management">High Output management</a></li><li><a href="https://www.goodreads.com/book/show/1633.Getting_Things_Done">Getting Things Done</a></li><li><a href="https://www.goodreads.com/book/show/368593.The_4_Hour_Workweek">the 4 hour workweek</a></li><li><a href="https://www.goodreads.com/book/show/36072.The_7_Habits_of_Highly_Effective_People">the 7 habits of Highly effective People</a></li><li><a href="https://www.goodreads.com/book/show/1169674.Conscious_Business">Conscious Business</a></li><li><a href="https://www.goodreads.com/book/show/6899290-your-brain-at-work">Your brain at work</a></li><li><a href="https://www.goodreads.com/book/show/66354.Flow">Flow: The psychology of Optimal Experience</a></li><li><a href="https://www.goodreads.com/book/show/9744815-succeed">Succeed: How we can Reach our goals</a></li></ul><p><em>Cross-posted from </em><a href="https://blog.yannick.io/"><em>https://blog.yannick.io</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1237df7ed630" width="1" height="1" alt=""><hr><p><a href="https://medium.com/yann-ck/the-effective-engineer-notes-1237df7ed630">The effective engineer Notes</a> was originally published in <a href="https://medium.com/yann-ck">Just thoughts</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Synology, Let’s Encrypt and Nginx]]></title>
            <link>https://medium.com/@yann_ck/synology-lets-encrypt-and-nginx-ca89ed5e2f83?source=rss-ca99c1c04695------2</link>
            <guid isPermaLink="false">https://medium.com/p/ca89ed5e2f83</guid>
            <category><![CDATA[synology]]></category>
            <category><![CDATA[lets-encrypt]]></category>
            <dc:creator><![CDATA[Yannick Schutz]]></dc:creator>
            <pubDate>Thu, 15 Sep 2016 16:07:27 GMT</pubDate>
            <atom:updated>2016-09-16T12:44:36.044Z</atom:updated>
            <content:encoded><![CDATA[<p>I have a setup that allow me to have https on my Synology NAS using <a href="http://letsencrypt.org/">Let’s Encrypt</a> and built-in Nginx.</p><p>For the information I am using the latest version of DSM which is the 6.0.</p><p>I think the setup was easy once I understood one small issue:<br>Synology and let’s encrypt are not really verbose about the errors.</p><p>So if like me you see the error message when trying to generate the certificate, please add all your subdomains to your main DNS for the time of certificate generation. Use a short TTL and remove it after.</p><h3>What is the setup?</h3><ul><li>Add port forwarding to your synology for port 80 in your modem or local network.</li><li>Add a DNS entry per subdomain you want to use on the NAS. This step has to be done on DNS server associated with the domain name.<br> For example a subdomain for my unifi controller on <em>unifi.synology.yannick.io</em> and one for <em>synology.yannick.io</em>.</li><li>On your NAS, go to <em>control panel &gt; security &gt; certificate &gt; Add</em></li><li>Select <em>Get a certificate from Let’s Encrypt</em>, fill the domain name with the main one. Add all the other ones that you created in <em>Subject Alternative Name</em> and Apply. (This is where you get the error if DNS is misconfigured or port forwarding. But it won’t be a clear error message)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/635/1*ITvMwfaWqyUIntnnqTofDQ.png" /><figcaption>This is the message you can get</figcaption></figure><ul><li>You can now remove the entries from your DNS provider.</li><li>Update the nginx config for reverse-proxy to all your synology apps. Config is in <em>/etc/nginx</em>, I created <em>yannick.io.conf</em> under <em>sites-enabled</em> and the content is:</li></ul><pre>server {<br>  listen 80;<br>  listen 443;<br>  server_name unifi.synology.yannick.io;<br>  location / {<br>    proxy_set_header Referer “”;<br>    proxy_set_header X-Real-IP $remote_addr;<br>    proxy_set_header HOST $http_host;<br>    proxy_pass <a href="https://127.0.0.1:8443/">https://127.0.0.1:8443</a>;<br>    proxy_http_version 1.1;<br>    proxy_set_header Upgrade $http_upgrade;<br>    proxy_set_header Connection “upgrade”; <br>  }<br>}<br>server {<br> listen 80;<br> listen 443;<br> server_name synology.yannick.io;<br> location / {<br>   proxy_pass <a href="https://127.0.0.1:5001/">https://127.0.0.1:5001</a>;<br> }<br>}<br></pre><p>With this basic configuration I can access my NAS locally without the ports.<br>Nginx is used by default on Synology already.</p><p>Hope this will help you too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ca89ed5e2f83" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>