<?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 Lorenzo Pieri - 404answernotfound on Medium]]></title>
        <description><![CDATA[Stories by Lorenzo Pieri - 404answernotfound on Medium]]></description>
        <link>https://medium.com/@404answernotfound?source=rss-10e319d1479------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*J908iNMbmfTQsTuq_6168g.png</url>
            <title>Stories by Lorenzo Pieri - 404answernotfound on Medium</title>
            <link>https://medium.com/@404answernotfound?source=rss-10e319d1479------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:38:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@404answernotfound/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[A guide to observability at Birdie]]></title>
            <link>https://medium.com/engineering-at-birdie/a-guide-to-observability-at-birdie-29b3459c9a78?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/29b3459c9a78</guid>
            <category><![CDATA[observability]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[monitoring]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Thu, 07 Sep 2023 10:16:19 GMT</pubDate>
            <atom:updated>2023-09-07T10:16:19.562Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fABMfTV15p56VE5X" /><figcaption>Photo by <a href="https://unsplash.com/@etiennegirardet?utm_source=medium&amp;utm_medium=referral">Etienne Girardet</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Let’s close our eyes for a minute and imagine a world where everything just makes sense and if it doesn’t, well, no worries, because we still have the chance to find meaning on any event, based on all the clues and cues that surround us.</p><p>From an Engineering perspective it might sound too good to be true but indeed, this is the power we rely on at Birdie whenever we want to make an informed choice or need to gather relevant informations about choices that we have already taken.</p><p>A decision, in simple terms, is something that might affect the way a business responds to events or how external factors could respond to these business decisions. Sometimes a decision can be dependent on a hunch or a feeling from someone inside a company but most of the times it really depends on data but where does this data come from?</p><p>Well, we could just say that most businesses are what we can call “data driven” and all the decisions are taken based on relevant outcomes from this “data driven approach”.</p><p>“Alright Lorenzo, but you are very well aware that Data, most of the times, is just a garbage collection thrown into very spacy baskets with no one looking into them”.</p><p>Well, <em>Troy</em>, you are right, most of the times that is exactly what happens but we should also be aware that that’s not the expected way to deal with this. Afterall, why would you bother collecting data at all, if you don’t want to make use of it. You should understand that this action of “collecting” any sort of information does bring a little overhead to any request carried out by our systems, so why collect anything at all?</p><p>“Well, everyone does logging!” — you might argue, <em>Troy</em>.</p><p>That’s not a reasonable answer, <em>Troy</em>.</p><p>Why would we collect any data at all? T<strong><em>o make informed decisions that align with the company values and objectives</em></strong>. That is good but how do we do that?</p><p>At <em>Birdie</em>, as Engineers, we rely upon flows of data that get collected, sampled and aggregated in our systems to be sent to other applications that make use of these to extrapolate meaning and show us how our system fares based on latest changes to the codebase, the number of requests that we receive and so many more valuable insights. This is what we define as <em>an observable system</em>.</p><p>We are also making heavy use of Event Sourcing, as such every event that is generated by the system can be used as <em>audit trail, data payload and as part of a snapshot to rebuild the system (and its aggregates) at any point in time</em>. This is not an article about Event Sourcing but I am sure that you can already sense the deeper understanding of the system and the data that we can have if we use Event Sourcing and Observability in conjunction.</p><p>As per the definition stolen by a dear colleague, <em>a system is observable if we are able to, without making any code changes, ask questions about the running system, understand how it behaves and identify issues</em>. Sounds delightful, but, it takes time, knowledge and a lot of pressure to build a diamond out of carbon, doesn’t it? And that’s exactly what happened at Birdie and, I’m sure, at many other companies out there, after all, you don’t want to start over-engineering by default, do you <em>Troy</em>?</p><p>At <em>Birdie</em>, not unlike many others, we started our journey into Observability with a simple yet very dependable logging system called <em>Bunyan</em>. Now, <em>Bunyan</em> is surely a recognised and famous tool used everywhere in the industry. It’s a fast and simple JSON logging module that you can inject anywhere in your Nodejs applications and it will just work. This approach works decently and it’s possibly one of the fastest.</p><p><em>Spoiler alert: there is an even faster one with time and space complexity O(0). Not collecting logs at all. Mind you, not the best choice.</em></p><p>The way pretty much everyone deals with this type of logging systems is to wildly hoard any logs and then cat logs.txt | grep &quot;any text in the logs&quot; which is completely fine but I’m sure, <em>Troy</em>, we can agree there must be a better system. One that is more reliable than the one we just described.</p><p>We can also agree on the fact that this kind of logging doesn’t come easy with correlation and causality between the different logs that get added to the mix. Just like a bowl of cereal, you just throw everything in and enjoy. This approach screams something like: “Send it all in, we’ll figure it out later!” and don’t get me wrong, it’s a fine approach for any starting points but if you feel your apps are beyond that, then you might be interested in relating this events to one another and be able to rebuild a story out of them, <em>a trail</em> of how log A generated log B up to log X, whatever that might be. That’s Observability, mostly.</p><p>With an observable system you, the <em>incredible engineer</em>, will be able to rebuild this trail of events based on all the hops that were generated between single interactions. This is powerful enough in Monolithic systems but just try to think of the insights that you might be able to gather in architectures like <em>Micro services.</em></p><p><em>Just like an onion</em>, each hop (in the system or in the network) will generate an additional layer of knowledge that will embrace the previous request and it will be up to you to scout for answers in what is a very precise, concise and knowledgable piece of information.</p><p>This piece of information is called <em>a trace</em> and a trace will contain all the information you need about how a process interacted with your systems and which events were generated based on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-9cs7DutvSHxPvtzPTcuiA.png" /></figure><p>A <em>Trace</em> is usually made up of 3 things:</p><ol><li>The Trace ID, which is shared between all <em>spans</em> that belong to that trace</li><li>The Span ID, which is the ID of the single spans</li><li>The Parent ID, which starts as undefined and changes for each subsequent span, based on the previous one. This is what we can refer to as the <em>causality</em> of the current span.</li></ol><p>Yes, it’s practically a <em>linked list of knowledge except that it’s not. It’s more like a tree. Which tree? A Baobab. You are welcome.</em></p><p>You might already be thinking: <em>Wow, this is incredible. I’ll get to it immediately.</em> Of course you will, <em>Troy</em>, but that’s not all there is to it, so read on!</p><p>With such a system in place we now have the granularity of the single logged <em>event</em> (which again, is a span) wherever it happens in our services. <em>Orwell would be so proud of us</em>. We can now see the trail of an event from start to finish, and that’s because every single <em>span</em> also describe itself as a log comprised on the span information, <em>the duration</em> of the span and <em>a timestamp</em> of when the span occurred.</p><p>“Alright, I’ll just delete all my console.logs and add Tracing to my systems!”. Yes, <em>Troy</em>, but also no. Very much no.</p><p><em>Tracing</em> and <em>Logging</em>, just as <em>Metrics</em> (which is another one of their buddies when talking about Observability) are really powerful when together so you don’t really need to choose one over the other, you just need to make sense of all of them and make good use of this new found knowledge at your disposal.</p><p>“Again, I get it, now stop being a bother and tell me <em>how</em> to implement this in my systems!”. Love the energy <em>Troy</em>.</p><p>As many answers by engineers that have reached <em>senior level and beyond</em>: it depends.</p><p>What I can tell you is that there are many ways to build an Observable system and at Birdie we used more than one approach and built up from there, little by little. There were many <em>Application Performance Monitoring</em> systems (APM from now on) to choose from and we also built our internal packages to deal with <em>tracing</em> using HTTP headers as well but now we are actively using <em>OpenTelemetry SDK</em> which is the <em>de facto standard</em> (which is the <em>de facto way of making something sound very important</em>) to collect traces in Distributed Systems like the ones we operate every day.</p><p>Traces (along with their spans) get collected and <em>refined</em> through an open source sampler proxy called <em>Refinery</em>. Sampling happens heuristically and relies on the amount of events that were sampled up to that point.</p><p>The basic gist of it is that we collect <em>all 500s</em> and a sampled amount of HTTP codes in the 200s, 300s and 400s range. After all, the most important information we can get is based on the errors that our systems might output.</p><p>But collecting is not enough and that’s where Monitoring tools and APMs come into play. We are just switching to a new monitoring system called <em>Honeycomb</em> which we found out to be very simple to get used to. With Honeycomb we can ask the right questions to the system at any point in time and we can configure and build these questions based on all the informations we have collected. Through this system, we are also able to visualise how our services are keeping up, the amount of requests they receive and if any issues are happening <em>in real time</em>.</p><p>Another important aspect of <em>Honeycomb</em> is that we can build personalised dashboards to check on our internal and external SLOs/SLIs/SLAs (Service Level IN (”objective”, “indicator”, “agreement”)) and <em>error budget</em> that we have as squads working in autonomous teams.</p><p>At Birdie, we are very much invested in bringing the best services and service levels to our end users and we care deeply for our systems. That is why we make ourselves accountable through the usage of SLOs and <em>error budget</em>, allowing us to be more aware of the scope of our applications and demystify all the processes that are part of our systems.</p><p>Thank you for taking the time to read through this with me and <em>Troy</em>! Happy Observability!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29b3459c9a78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/engineering-at-birdie/a-guide-to-observability-at-birdie-29b3459c9a78">A guide to observability at Birdie</a> was originally published in <a href="https://medium.com/engineering-at-birdie">Engineering at Birdie</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Humanely AI, a hope]]></title>
            <link>https://medium.com/@404answernotfound/humanely-ai-a-hope-81e7d1bfe484?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/81e7d1bfe484</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[social-media]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Mon, 16 Jan 2023 20:06:37 GMT</pubDate>
            <atom:updated>2023-01-16T20:06:37.718Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-SjKpelYsFMyMgZt4d64Q.jpeg" /></figure><h3>I started this blog post like many others. Opened a few pages, sprinkled the idea, wrote a basic input on a particular Notion page and collected more resources to gather more insights and knowledge about what I wanted to write.</h3><p>The thing is, today I could have just wrote the prompting message and deliver it to what’s been on everyone’s homepage lately: <em>chat-gpt3</em>, also known as <em>the AI that will steal our jobs, kill us or use us as milking cows until we are too old of age</em>.</p><p>Probably went a little bit overhead with this last naming convention <em>but</em> one should know that even the strongest of mind and belief are faltering a little bit once caught in the endearing endeavours of this mighty technology.</p><p>I too have succumbed to the flattering promises of a lightweight solution and ease of prompt. I too have had the fun to input the most hilarious, or distasteful, or misogynistic, or philanthropic, or racist, or exquisite questions or remarks to this astonishing piece of ars tecnica. I have tried many ways to trick the AI to give answers that were far from perfect. Some of them far from decent. It’s an AI.</p><p>It is far from perfect and sometimes it can help us peek into the known and unknown worlds of human knowledge and interactions. The language model of <em>chatgpt-3</em> is built upon human literature of all kinds, after all. Be it blogs, social media platforms, books, reviews, papers, conversations, movie dialogues, audios. Whatever it is, it moulded this AI into what it is. Depending on the inputs there are ways to collect views that are all but nice and human.</p><p>I am sure you might have seen code generation where the examples are based upon parameters that might discriminate through the output. I will leave to the user the search for such examples as I find them very sad and disheartening given that these answers are based upon training that was “cooked” by humans.</p><p>Despite the many uninteresting articles that were released into the wild during this last month I still am very fond and entertained by this new powerful ally we have now at everyone’s hands. This led to questions, that led to more questions which featured questions that ended in questions. I guess there is no good answer to this.</p><p>The starting question is:</p><h3>Is humanity good enough for AI?</h3><p>Usually it goes the other way around but this time I am wondering whether or not we deserve as specie to be able to use such a powerful and versatile instrument.</p><p>As we learnt to use primeval tools, we started making weapons. We could have ended at hunting weapons, we didn’t.</p><p>As we learnt to use fire, we searched for ways to capture its essence. We could have warmed our houses and yet we went in many other places with this ability tho, not all of them great.</p><p>As we learnt to use the internet, we tinkered with its many secrets. We could have built a new era for humans but what we created, amongst many things, were phishing, smishing, vishing and hacking in general.</p><p>Don’t get me wrong. Hacking is great if you think of yourself as <em>an actual hacker</em>. Trying to f*%k with people’s life and making them miserable is not what a hacker does. That’s another thing.</p><p>One might argue that with any invention or discovery there’s going to be blacks and whites. There’s going to be middle grounds, the famous grey areas.</p><p>I concur and yet this is exactly what makes me wonder whether or not humans are deserving of such powerful instruments. History luckily has nice ways to remind us of how stupid and colossally outrageous we can be as a specie. Think Atomic Bombs. Think Nuclear Bombs. Think many other things. Do we have to put “Bombs” anywhere we invent? I hope not.</p><p>But I am digressing from our question. Is humanity good enough for AI? I think that we can be, with the right attitude.</p><h3>What is possible?</h3><p>I am no scientist of the Artificial Intelligence field. I’d love to learn more about data science and algorithms of the sort in general but for now I will write about how I see this moving forward as a human being and not as a professional.</p><p>Let’s make a small list of the most sophisticated public AIs that are available right now for everyone to use:</p><ul><li><em>chatgpt-3</em>, we all know</li><li><em>midjourney</em>, an AI that can generate images based on user prompt</li><li><em>deepfake</em>, not an AI but rather a technique to generate fake imagery that looks real</li><li><em>DALL-E</em>, another image generator</li></ul><p>There are many more AIs that are becoming public each day and some models are also open sourced and available at anytime to anyone. This is fantastic but also scary.</p><p>Look for <strong>VALL-E</strong>, a <strong>Speech Synthesizer</strong> AI that can generate real human voice. That’s not scary at all.</p><p>Depending on the usage one could do a great amount of damages to a great amount of people and companies.</p><h3>Let’s focus on the brighter side</h3><p>I started this article with a nuance of bitterness and without trust in the human spirit but in reality I believe that we are fundamentally good, at least in the higher percentage of population on the planet. We cannot control what’s good and what’s bad as it is perceived directly by each and everyone of us and it’s strongly dependent on so many factors that would make it not ideal for a calculation.</p><p>Let’s pretend that everyone is good for a moment tho, at least for what generally is thought of as “a good human being”.</p><p>What would you do with this fast evolution of the technology?</p><h3>Humans are fundamentally made to connect</h3><p>I’d like to think that this evolution of AI would enable us humans to become even more connected, allowing us to exchange thoughts, processes and feelings with beings and other humans that are not necessarily present.</p><p>I imagine an AI that will be able to take inputs from literature, sounds, voice files, recordings, videos, images and so much more. These inputs would then be used to generate an entity that could resemble a person not only in imagery but also in character, personality and knowledge.</p><p>I imagine the possibility to talk with the greatest minds of past times or with someone who is no longer with us but somehow their memory still exists.</p><p>I am not talking about immortality of the person or immortality of the mind. I am far too scared of such a concept and I find it unnatural, unrealistic and also very wrong.</p><p>I am talking about shared knowledge and history, emotions that are never to be lost in time, voices that can be heard at any moment.</p><p>I imagine that a good AI will be as good as the collective knowledge and feelings of humanity.</p><p>What about you? What do you think?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81e7d1bfe484" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Codemotion Experience 2022]]></title>
            <link>https://medium.com/@404answernotfound/the-codemotion-experience-2022-1bc7934062e9?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bc7934062e9</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[carbon-footprint]]></category>
            <category><![CDATA[climate-change]]></category>
            <category><![CDATA[codemotion]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Mon, 24 Oct 2022 16:01:47 GMT</pubDate>
            <atom:updated>2022-10-24T16:01:47.099Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*olimxNPIoOglrhy8" /></figure><p>This year I had the incredible opportunity to participate at the conference <a href="https://www.codemotion.com/"><strong>Codemotion 2022</strong></a><strong> </strong>as a Speaker and it’s been such a formative experience. Given the chance, I decided to talk about a subject that matters not only to me or to the software engineering industry, but really interests all of us, and by all I mean all.</p><p>I had a few talks ready, which you can find on my <a href="https://github.com/404answernotfound/talks">Github repository</a>, but, as many other friends and colleagues, I portrayed <em>web sustainability</em> to be a much better and more interesting subject of our times.</p><h3>What is Web Sustainability?</h3><p>Web Sustainability is the practice of <em>actually taking care</em> about the code we write, the designs we implement and the algorithmic solutions that we build inside our products or base our projects upon.</p><p>If you would like to know more about this topic I invite you to visit <a href="https://envirotechnical.eu/">environtechnical.eu</a> website where I collected all the resources that I used to confirm the datasets used inside the talk/slides and other really nice websites that can help you perceive your services’ <em>carbon footprint</em> better.</p><p>Free tip: taking care of <em>carbon footprint</em> actually makes your websites and apps faster and more performant as they will be using less resources, less bandwidth and less CPU cycles. Also, <em>time to first byte</em> is drastically improved which goes a long way in terms of better SEO and UX.</p><p>If you would like to peek at the slides, <a href="https://docs.google.com/presentation/d/1w1YCHrYT_qXhAdCUVlmnDWerqdwgqjSG/edit#slide=id.g162ac6e011f_0_0">feel free to do so at this link</a> and let me know if you have any feedback, which is always appreciated!</p><h3>Why envirotechnical</h3><p>I was actually building the slides for the talk at Codemotion 2022 Milan when I realized that I wouldn’t have enough time (<em>it was a lighting talk, 12 minutes of talk and 3 of Q/A</em>) and space to gather and show all the resources that I thought would be influential and useful to the readers and listeners. <em>That’s when it clicked</em>.</p><p><a href="https://twitter.com/KrasimirTsonev/status/1580265878071152640">I was reading from a friend’s Twitter feed</a> that he would buy domains long before even starting working on a project (<em>do you do the same?</em>) and thought: why not, why not actually share a link to a lot of resources!</p><p><a href="https://envirotechnical.eu/">https://envirotechnical.eu/</a></p><p>And so envirotechnical (which started out as environtechnical) came along on a Saturday morning. Took 3 hours to make and build and get all the resources together and it was super fun. I built it using nextjs as I really enjoy the DX on that product and alongside tailwind it made it so simple to have a tidy looking website that would also be responsive out of the box.</p><p>The term is pretty simple, I guess: <em>enviro</em> stands for environment, <em>technical</em> stands for, well, tech. I liked the semantic and the sound of it and that’s how this new project started to have its own life.</p><h3>What are the plans for envirotechnical</h3><p>I plan to continue gathering resources and studies on the subject to allow for a more thoughtful and precise understanding of the implications that tech definitely has on the environment. If you would like to share any pages or documents or media about this, please feel free to contact me on Twitter or LinkedIn at any time!</p><p>Ideally <em>web sustainability</em> will not be just a fancy wording but an actual valuable battle that we can all fight together, one byte at a time.</p><h3>Big rounds of applauses</h3><p>I would like to thank my good friend <strong>Andrea Amilcare</strong> who is also working in the website design and development industry and was actually him that got me started on this very interesing and important journey on sustainability in general. You can find his article <a href="https://amilkare.it/siti-web-sostenibili/">at this link</a>.</p><p>A big thank you also goes to my friend and industry colleague <strong>Angela Busato</strong> whom wrote a beautiful piece about her experience at Codemotion 2022 which inspired this very blog post, so thank you Angela! You can find her <a href="https://medium.com/@busato.angela/my-first-codemotion-ba490f4a2572">codemotion experience here</a>.</p><p>I should also thank the new friends that I made at this event from which I learnt and continue to learn so much about the industry that I’m proudly part of.</p><p>Special thanks to <strong>Emanuele Bartolesi</strong>, <strong>Luciano Mammino</strong>, <strong>Francesco Sciuti</strong>, <strong>Mara Marzocchi</strong>, <strong>Michele Riva</strong>, <strong>Simone Sanfratello</strong>, <strong>Luca Colucci</strong>, <strong>Michela Bertaini</strong>, <strong>Mauro Murru</strong>, <strong>Luise Freese</strong>, <strong>Gabriele Santomaggio</strong>, <strong>Fabio Biondi</strong>, <strong>Edoardo Dusi</strong>. These amazing individuals are an ever growing inspiration for me.</p><p>Another round of applause goes to the community that I’m part of, <a href="https://www.schrodinger-hat.it/">Schrodinger’s Hat</a>. This group of outstanding people are taking the meaning of “community” to another level and I’m proud to be part of the SH fam as co-organizer.</p><p>And a final thanks goes to you, the reader. If you will take the time to read through the resources and the slides on <a href="https://envirotechnical.eu/">envirotechnical.eu</a> we will be one step ahead in the fight to climate change.</p><h3>The goodbye</h3><p>I hope you found this article useful and to your liking and if you have any requests, drop a message on one of my social media accounts or open an issue/start a discussion on github, on this <a href="https://github.com/404answernotfound/community/discussions">repository</a>!</p><p>As always you can find me on <a href="https://twitter.com/404answnotfound">Twitter</a>, listen to my <a href="https://open.spotify.com/show/0d3hBsVITjcFRxPRqvNtCQ?si=e060235591d54152">Podcast on Spotify</a> and add me on <a href="https://www.linkedin.com/in/lorenzopieri/">LinkedIn</a> to talk professionally (<em>yeah, right</em>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bc7934062e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The interview processes for Software Developers, a manager’s guide]]></title>
            <link>https://medium.com/@404answernotfound/the-interview-processes-for-software-developers-a-managers-guide-3a7793e20851?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a7793e20851</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[jobs]]></category>
            <category><![CDATA[interview]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[life]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Thu, 09 Jun 2022 10:01:51 GMT</pubDate>
            <atom:updated>2022-06-09T10:01:51.931Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*4INZXJoDmBQ8Mv6Ierqh8Q.jpeg" /><figcaption>Developer Interview process — 404answernotfound — Picture by <a href="https://unsplash.com/@mkvandergriff">https://unsplash.com/@mkvandergriff</a></figcaption></figure><p>As a Senior Developer and Head of Development at my current company I had the pleasure to conduct interviews with candidates at all levels, junior to senior.</p><p>This article wants to portray some key points that I think might be helpful to the future you if you ever find yourself interviewing candidates in the tech community, so, here’s my list of do’s and don’ts</p><h3>Developers that are interviewed are there to get a job at your company and they probably applied because they like the idea of working there, so, do your best to make sure they are feeling at ease during most of the process.</h3><p>Is there a point in time where you want to make sure they are not at ease? There could be, but that’s an entirely different context. If you want to test the candidates under pressure, you should use specific questions and scenarios that can prove whether they can or cannot withstand pressure.</p><p><em>So, the takeaway here is</em>:<strong> interview for what you are looking for</strong>, don’t just bluntly follow some list of questions that’s used by hundreds of companies just for the sake of using it. Make your own interview process and make it as tailored to your company as possible.</p><p>Should you whiteboard candidates like MAANG do? I don’t think you should, but that’s a choice you will have to make. Instead, make your own lists of requirements and interview for those. Search in the candidates the things that your company or office cares about.</p><p><strong>Candidates all differ from one another in so many ways and there is no magical trick to find the one that fits the best with your company’s profile, mission and values but what can be done is</strong>:</p><ol><li>Have a defined selection process to screen the candidates resumés based upon your search criteria, but also remain open and dynamic to the information you collect. Some candidates might not be perfect on paper but can prove to be game changers if given the chance</li><li>Decide whether you would like the technical interview to take place on a live coding session or if you would rather give the developer a take home assignment. I like the second option the best as it shows how the developer would usually work. Also, you are going to review the assignment together so you can ask questions about it.</li><li><strong>Don’t look for perfection. It doesn’t exist</strong>. The candidates will do their best but they will become “<em>perfect for the company</em>” only once they start working <strong>with</strong> the company.</li><li>If it’s a live interview, be kind. Remember when it was you being interviewed — “<em>Be the senior you always wanted to be your senior</em>”</li><li>Kindness and gentleness can go a long way. Don’t ever forget this.</li></ol><p>I hope this article can be useful for your interview processes and if you have any questions or would like to discuss this further, write in the comments or reach out to me on my website <a href="https://404answernotfound.eu/">https://404answernotfound.eu/</a> or on Twitter <a href="https://twitter.com/404answnotfound">https://twitter.com/404answnotfound</a></p><p>Have a great day and stay kind! ❤</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a7793e20851" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React is double rendering your components and it’s good]]></title>
            <link>https://medium.com/@404answernotfound/react-is-double-rendering-your-components-and-its-good-d3317aa1f848?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3317aa1f848</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[hooks]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Fri, 03 Jun 2022 11:10:58 GMT</pubDate>
            <atom:updated>2022-06-03T11:10:58.447Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="React 18 double rendering is good" src="https://cdn-images-1.medium.com/max/1024/1*MOYJZ07npQzv4HhHBzDPcA.jpeg" /><figcaption>Picture by Unsplash, all credits to Fotis Fotopoulos</figcaption></figure><p>One day you woke up with your project in development mode, you put a little console.log inside a <em>useEffect</em> with zero dependency and you expected it to run exactly as a class component would have if you were to develop a <em>componentDidMount</em> lifecycle method.</p><p><strong>WRONG</strong></p><p>React 18 has a StrictMode which you can opt-in and out of which, during development, encapsulates the entire application.</p><p>What this does is that it tells React to try and kind of <em>fake a page transition</em> that <strong>mounts</strong> and <strong>unmounts</strong> a component. There is no actual transition but this ensures that your components and your state are resistant to weird state problems that might arise if you were<strong><em> not not clean your useEffects during unmount</em></strong>.</p><p>I wrote an article about it where I go into more specifics, if you are interested in reading more about this. <a href="https://404answernotfound.eu/blog/react-useeffect-double-rendering-fix-and-why-you-should-stop-crying-about-it">Link here</a>.</p><p>If you have any doubts about fetching inside a useEffect hook, you should check out what <strong>Dan Abramov </strong>answered me on twitter <a href="https://404answernotfound.eu/blog/react-useeffect-double-rendering-fix-and-why-you-should-stop-crying-about-it#how-to-fetch-data-with-useeffect-with-react-18">which I reported here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3317aa1f848" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A programmer’s boredom]]></title>
            <link>https://medium.com/@404answernotfound/a-programmers-boredom-1759804eed40?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/1759804eed40</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[life]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Fri, 27 May 2022 16:42:32 GMT</pubDate>
            <atom:updated>2022-05-27T16:42:32.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SQ5QYYBFo2t3K_3g-wbQZg.jpeg" /><figcaption>Bored Professional by Johnny Cohen (https://unsplash.com/photos/ubQyvYf2Fqs)</figcaption></figure><p>This is <em>the true story of programmers</em> that feel they are wasting their time when they have no work to do on their hands.</p><p>In my personal opinion, <em>this just doesn’t feel right</em>.</p><p>I remember there was a time when I was a junior developer and it happened that my seniors didn’t have anything for me to work on for some hours or even days but I didn’t just “wait” for things to come out.</p><p>When you are a Junior, it is expected of you to empower yourself with every possibility of learning, be it through direct learning with your Seniors or on your own. If you “can’t find things to do at work”, look closer. Same applies to Senior developers but this is a lesson that most of them learnt already.</p><p>Here are a few things you could try and think about:</p><ol><li><strong>Talk</strong> and <strong>learn</strong> with and from your coworkers</li><li><strong>Ask</strong> other departments what they are building while you’re on a different team</li><li><strong>Celebrate</strong> the company’s culture by asking people’s stories. There’s so much you can learn from someone else’s life on so many levels.</li></ol><p>Want to be more technical about it?</p><ol><li>Check out the new versions of libraries, dependencies and packages your team is using in the projects you are working on.</li><li>Check for dependency security updates and read why they are important</li><li>Write some documentation to help you and everyone else get a better understanding of your code</li></ol><p>This list could go on and on but I guess the most important thing to take home is: <strong>don’t just get bored by dependency</strong>, get free by alternatives.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1759804eed40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s a Framework or library in Javascript?]]></title>
            <link>https://medium.com/@404answernotfound/whats-a-framework-or-library-in-javascript-75146a50d12?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/75146a50d12</guid>
            <category><![CDATA[vue]]></category>
            <category><![CDATA[framework]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[angular]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Mon, 23 May 2022 08:12:34 GMT</pubDate>
            <atom:updated>2022-05-23T08:12:34.108Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Framework and Libraries in Javascript by 404answernotfound" src="https://cdn-images-1.medium.com/max/1024/1*BeOkCznhzNnfooQe4K8TBw.jpeg" /></figure><p><a href="https://open.spotify.com/episode/2kKdD3gpkUCVNuC29U5Qas?si=nvIZRRObQ8KKklNjvH9fhA"><em>Link to the latest episode here</em></a></p><p>And here we are with another brand new episode of <strong>404answernotfound</strong> Podcast in writing. It’s been a few days since our last episode and today I would like to be your chaperon in the world of well known and even lesser known frameworks and libraries in the Javascript ecosystem and the difference between those two terms.</p><p><strong>React</strong>, <strong>Angular</strong> and <strong>Vue</strong> but also mentions to <strong>Preact</strong>, <strong>Solid.js </strong>and why those alternatives came to exist in the first place.</p><p>And now, let’s go ahead and start.</p><p>Welcome to <strong>404answernotfound</strong>, I am Lorenzo, your host, digital techy nerd creating content for probably unexistent listeners and readers, and a finder of problems to known solutions. You can <a href="https://404answernotfound.eu/">check out my blog here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BeOkCznhzNnfooQe4K8TBw.jpeg" /></figure><p>Today’s episode is about Frameworks (or libraries, just so that React afecionados don’t get mad at me for not being very clear about this).</p><p>What do I mean by that?</p><p>Well, both <em>libraries</em> and <em>frameworks</em> have something in common: they are written by someone who wants to solve one or more issues and make this solution a portable one. Both libraries and frameworks can also be shared with the public, but they can also be private (think internal tools in private companies as an example).</p><p><strong>So how can we differentiate and classify between the two?</strong></p><p>To keep it simple yet I would say that a library is a tool belt with one or more tools in it that you can use to build up your applications and ideas without “giving away” your opinions on how the build should be done.</p><p>On the other hand, Frameworks are much more complete as they are opinionated. What do I mean by that? Well, before you had a tool belt, now you have an entire factory.</p><p>It can sound amazing, but remember, you can grab, move and change tools in the tool belt anytime you like. <em>Can you do the same with a factory?</em></p><p>Think of all that incredible machinery and processes that output your applications so easily and without too much effort in the making! But that’s not all shiny diamonds, there’s a cost to that.</p><p>While you are being incredibly fast in outputting your ideas into the world you are abandoning the possibility to make tangible changes to the blueprint <em>and of course you are</em>, there’s a process in the factory that must be followed, you can’t change your mind on whim, can you?!</p><p>Well, spoken like these it makes frameworks look terrible but they really aren’t.<strong><em> It’s all about choice. Always has been.</em></strong></p><p>When you decide to go for a Framework instead of a Library you are definitely making a choice for your project. And that’s normal. Picking a framework means that you probably read the documentation (<em>yeah right</em>) and thought that the framework’s way of thinking and building apps lines up with your ideas of how an app should be built. That’s what makes a framework more opinionated than a library (which can also be opinionated by the way).</p><p>But what’s “opinionated” anyway? As the word implied it’s about the presence or absence thereof of an opinion that the framework or library is built upon. The stronger the opinion, the lesser the freedom that the developer is going to have in the building process of the application.</p><p>Want one more example?</p><p><strong>Think of Scrum</strong>. It’s a framework based on Agile methodologies with very strong and defined opinions. You are either doing Scrum or you’re not doing it.</p><p>But what if you want to use kanban boards for your projects? What if you follow some of the Agile methods without actually signing up for the whole deal? That’s your Agile library, right there.</p><p>Is there a better choice or worse choice? There isn’t. It all depends on your opinions and how you feel about these frameworks, ideas and methodologies.</p><p><em>But now let’s get back to technical speaking and talk about what we all love and is definitely better than all the other technical choices one might think about: React.</em></p><p>Don’t just leave! I was joking! Although React is my favorite frontend library to work with UI, not gonna say it’s not.</p><p>Today’s episode is about frameworks and libraries and their difference but we should bring a few examples to the imaginary table and discuss those further. I am a Developer of the Web so in this podcast we’re discussing Frameworks and Libraries that stem from Javascript.</p><p>In today’s arena:</p><ul><li>“<strong>Angular</strong>”, the gonna-do-it-all framework</li><li>“<strong>React</strong>”, the just-a-ui-library-with-fancy-components library</li><li>“<strong>Vue</strong>”, the im-just-here-for-the-popcorns framework</li></ul><p>Who’s gonna win? Which choice is the best choice?</p><p>Well, we just said there’s no best choice so the question is nullable. But, there are differences that would make me choose one over the other, so let’s go with those.</p><p>Angular is a framework released in 2010 but changed substantially in 2016 with the release of the second version. Before that, it was known to everyone as AngularJs. This framework is very complex and complete and comes with its own ideas and opinions about how things should work and how logic should flow in your application. Is it everyone’s favorite cookie? It’s not. But people love to use Angular and the promise of a well designed and opinionated framework is gold for those that would rather ship their application fast without thinking too much about structuring the underlying logic for the app to work from the grounds up. Don’t get me wrong, this doesn’t make Angular a monolith that cannot be changed or played with, but to tamper with Angular’s internal is not everyone’s favorite thing and it’s mostly unnecessary if you like how Angular makes you think about programming and building apps “the Angular way”. It should be noted that Angular uses typescript out of the box, which is something that people really like.</p><p>Vue.js is a framework with incremental opinions on how you should build your applications. It comes from one of the users of AngularJs, Evan You, whom was using AngularJs while working at Google.</p><p>In fact, Vue does retain some similarities with AngularJs before the big change in 2016, when Angular2 was released, branching away from the previous version in almost everything.</p><p>On the official website it defines itself as an approachable, performant and versatile framework for building web user interfaces. As with Angular, you can do pretty much anything with Vue, from enhancing static HTML to creating single page applications with web components.</p><p>Vue.js is “The progressive framework” and it’s usage has skyrocketed over the years thanks to its amazing and growing community.</p><p>I do not have a lot of technical experience with Vue but we are using it for quite a few projects and our website with the <strong>Schroedinger’s Hat community</strong> of which I’m actively part of. Big shoutout for our friends over <strong>Schroedinger’s Hat</strong>! Go and checkout the discord channel of the community, links on the website <a href="https://www.schrodinger-hat.it/">https://www.schrodinger-hat.it/</a></p><p>Another strong point that Vue.js acquired from its sibling Angular is the two-way data binding which makes the developer’s life so much easier but also more prone to errors in the design of web apps.</p><p>And now comes my favorite cookie! React!</p><p>Now, you can like it or not but I think history is telling us that React did a pretty good job as a UI library.</p><p>Because React is not a framework, it’s a library built for creating user interfaces with logic and interactivity.</p><p>One of the key selling points of React is the fact that it’s completely component based, with single components managing their own state but yet composable to build complex UIs.</p><p>I mentioned that history is proving the React way to be a fair way to follow because Angular and Vue also recently added a more “reactive” way on how to approach their components. It’s not a war about frameworks or libraries and I actually think it’s amazing that some ideas that can make products better are shared between the parties so that the community can make the best out of those products.</p><p>React is a library instead of a framework because it’s not as opinionated and it doesn’t make choice in your stead. This can sometimes lead to a slower building process but it also gives the user complete control on feature development and technology stack without being stuck on opinions from other frameworks. The newest versions (from 16 to now 18) made is incredibly performant, at first with React Fiber and the reconciliation algorithm (which we will talk about in future episodes or on the blog) and now with a new approach on batched updates and concurrent rendering of the components.</p><p>So, is there a best choice? Again, there’s not. There are choices and those choices should come from acknowledgement of all the strengths and weaknesses so that we, as developers, can make a valid point on why we went for one technology over the other. The same can be said when we are choosing one language over the other.</p><p>At the start of the episode I mentioned a few other libraries that are very similar to React, like Preact, Svelte or SolidJs.</p><p>Those libraries implement some things in a different way but their approach to the development phase is similar to that of React. What changes is the underlying structure and choices that were made when building the library.</p><p>As an example, React uses the Virtual Dom and a diffing algorithm to reconcile all changes made to the virtual dom to the real DOM, allowing for good performance and cost effective changes. Solid on the other hand ditches this approach while retaining the real DOM by updating in a reactive way (which React doesn’t, funnily enough).</p><p>So, we discussed frameworks and libraries and hopefully you have a good understanding of the differences between those two terms.</p><p><em>I hope you enjoyed this episode and remember that you can find me on twitter @404answnotfound, on Github as </em><strong><em>404answernotfound</em></strong><em>, cause, you know, more characters and there’s always my blog, </em><a href="http://404answernotfound.eu/"><em>404answernotfound.eu</em></a><em> (as in Europe) where I writing almost daily blog posts and where you can find interesting technical reads with ease-of-mind attitude.</em></p><p><em>Thank you again for joining me and happy hacking! See you in the next episode of </em><a href="https://open.spotify.com/episode/2kKdD3gpkUCVNuC29U5Qas?si=nvIZRRObQ8KKklNjvH9fhA"><em>404answernotfound Podcast</em></a><em>!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75146a50d12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[18 What’s new with React 18?]]></title>
            <link>https://medium.com/@404answernotfound/18-whats-new-with-react-18-a463484aa0c9?source=rss-10e319d1479------2</link>
            <guid isPermaLink="false">https://medium.com/p/a463484aa0c9</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Lorenzo Pieri - 404answernotfound]]></dc:creator>
            <pubDate>Tue, 17 May 2022 15:23:00 GMT</pubDate>
            <atom:updated>2022-05-17T15:24:29.915Z</atom:updated>
            <content:encoded><![CDATA[<h3>What’s new with React 18?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KKYZK_GTHja7MIKqVO26Sw.jpeg" /></figure><p>React 18 has been released a few weeks ago and people had the chance to try the new changes. Someone had to deal with problems on the useEffect hook but that&#39;s mainly caused by the new &quot;concurrent mode&quot; that React 18 brings with it&#39;s new major versioning.</p><p><em>Original article can be found on my blog</em>, <a href="https://404answernotfound.eu/blog/react-18-is-out-whats-good-about-it"><strong>404answernotfound.eu</strong></a></p><h3>React 18 is out</h3><p>React 18 has finally shipped and sailed the seas of change in the <em>mare magnum</em> of all libraries on NPM. The team behind React has been very friendly on the adoption side of the new version, allowing users to <em>opt in</em> on any new feature the library brings on.</p><p><em>Gradual adoption</em> being of the uttermost importance, let’s see what’s new and what’s troubling about this new release and most importantly, how we can break production code without even trying!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/577/0*bfb0rK9qXo1tXHxU" /></figure><p>Alright, so you want to upgrade your <em>React</em> installation because all the cool kids are using the new Concurrent Mode and, although you have no idea what that’s all about, you still wanna play with it.</p><pre><em># You can also avoid specifying the @18</em><br>npm i react@18 react-dom@18</pre><p>And also, if you are migrating an existing React project from version 17 (or prior to that) to version 18, you should take care of the entry point of your application.</p><pre><em>// Old way, prior to version 18</em><br>ReactDOM.render(&lt;App /&gt;, document.getElementById(&#39;root&#39;))</pre><pre><em>// New root binding, this is for version 18 if you want to upgrade</em><br>const root = ReactDOM.createRoot(document.getElementById(&#39;root&#39;))<br>root.render(&lt;App /&gt;)</pre><p>Not so much of a difference here, just a few changes and you’re set to go.</p><p>I love how the React blog clearly states that their best addition to the library is <em>something they hope you’ll never have to think about</em>. Makes a lot of sense to me. That’s good engineering.</p><p>All the fuss around React Concurrency and all you actually need to know to start using it is just:</p><ol><li>Upgrading to version 18</li><li>Do the same stuff you used to do before version 18</li></ol><p>Concurrency in React 18 can be thought of a new invisible mechanism that works behind the scenes and <em>just works</em>.</p><p>What it does is it prepares multiple versions of your amazing and well engineered UI (<em>who are we kidding</em>) and it does so, well, <em>concurrently</em>, thus allowing for a boost in performance without you doing actually nothing but leaving you with all the bragging that comes with performance boost.</p><p>With Concurrency being the most important under-the-hood boost for this library, there are also quite a few interesting additions that one might care about.</p><h3>New Hooks in React 18</h3><p>React 18 comes with a series of useful hooks that you might consider pretty much as utilities to grunt some work and offload you from installing third-party dependencies.</p><p>useId is a hook that brings uniqueness in generating random IDs both on client and server side React.</p><p>useTransition can set updates as <em>not urgent</em> allowing React to schedule state updates accordingly, boosting performance.</p><p>There are also useDeferredValues, useSyncExternalStore and useInsertionEffect which appear to be low level and a good entry point for future adaptations by libraries. For more informations you can read about those hooks <a href="https://reactjs.org/blog/2022/03/29/react-v18.html">here</a></p><h3>React 18 Strict Mode</h3><p>With React 18 also comes a double rendering of components which is actually <em>not as true</em> as it seems. React 18 has introduced a new dev-only check that whenever a component gets mounted it will get unmounted and remounted.</p><p>You will not lose state or anything and it actually gets stripped during production build.</p><p>So what’s about it?</p><p>Well, some use cases are being <em>broken</em> by this, like the empty dependency array trick to simulate the <em>componentDidMount</em> cycle.</p><p>What people are doing to solve this “<em>issue</em>” is to create a <em>ref</em> to integrate with the previous behavior, what people should be doing instead is to avoid leaving the dependency array empty as it will always be dependent on something, even something that doesn’t change.</p><p>A beautiful article from Dan Abramov has <a href="https://overreacted.io/a-complete-guide-to-useeffect/">a great explanation on the mental model behind useEffect</a>.</p><p>But if you want to keep the dependency array empty and continue with the <em>almost similar</em> componentDidMount life cycle, <a href="https://dev.to/ag-grid/react-18-avoiding-use-effect-getting-called-twice-4i9e">take a loot at this article from AG Grid</a>. You should know that this is just for development purposes only so you can probably not care about it and use React as you always had.</p><h3>The goodbye</h3><p>I hope you found this article useful and to your liking and if you have any requests, drop a message on one of my social media accounts or open an issue/start a discussion on github, on this <a href="https://github.com/404answernotfound/community/discussions">repository</a>!</p><p>As always you can find me on <a href="https://twitter.com/404answnotfound">Twitter</a>, listen to my <a href="https://open.spotify.com/show/0d3hBsVITjcFRxPRqvNtCQ?si=e060235591d54152">Podcast on Spotify</a> and add me on <a href="https://www.linkedin.com/in/lorenzopieri/">LinkedIn</a> to talk professionally (<em>yeah, right</em>)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a463484aa0c9" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>