<?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 Miki Lombardi on Medium]]></title>
        <description><![CDATA[Stories by Miki Lombardi on Medium]]></description>
        <link>https://medium.com/@thejoin95?source=rss-dab2a46eef7e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*N4bsUGgvH6AZluIy3SC1UA.jpeg</url>
            <title>Stories by Miki Lombardi on Medium</title>
            <link>https://medium.com/@thejoin95?source=rss-dab2a46eef7e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:05:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thejoin95/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[Upgrading to React18 is easy]]></title>
            <link>https://medium.com/growens-innovation-blog/upgrading-to-react18-is-easy-f4c41b0b74a1?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4c41b0b74a1</guid>
            <category><![CDATA[micro-frontends]]></category>
            <category><![CDATA[npm]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Tue, 20 Sep 2022 13:55:50 GMT</pubDate>
            <atom:updated>2022-09-20T13:55:50.654Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="On the right with there’s an SVG illustration from unDrawn of a person a list of things to do in his hand. At the same time, they are watching a representation of a white 16:9 screen with a white arrow facing up on a violet circle background because they need to make sure that the settings are updating correctly. On the left of this image there’s written “Upgrading to React18 is easy” and under there’s the category of the article that is “Tech innovation”. Everything is on a violet background." src="https://cdn-images-1.medium.com/max/1024/1*gmzkmqfqBwkglNpINBuFjg.png" /></figure><p>We read that a lot of people and companies are having issues with the migration from a previous version of React library to the latest version, the React18, and we thought it would be hard to <strong>upgrade our micro frontend applications</strong> from React16 to React18, with RecoilJS and all the tests.</p><p><em>It turns out that no, it was not that hard, actually </em><strong><em>it was pretty easy</em></strong><em>!</em></p><p>We did it fast, without breaking anything, migrating the whole application to the latest react, recoil and testing library version without experiencing any issues.</p><p><em>In this article we are going to analyze the actions that we took in order to </em><strong><em>get an easy migration</em></strong><em> to a newer version of the library.</em></p><h3>What’s really new in React18?</h3><p>React-dom API is changed, this is the fastest answer to the question.</p><p>This article is <strong>not meant to be an in-depth journey</strong> into React18, because a lot of things were limited or deprecated before this version came out, and the other features provided just small changes (such as renderToPipeableStream or useEffect or StrictMode).</p><p>Of course, we are reflecting all of these changes from our point of view (react16 codebase), where we are already using <em>functional components </em>for an easier usage of the hooks such as useEffects.</p><h3>Migrating to React18 in few easy steps</h3><p><em>Again, this is our personal experience, it might be different for others or in other environments.</em></p><p>First of all we needed to <strong>clean all the old dependencies</strong> and check for security issues for the others via npm audits. It’s always about the node modules.</p><p>After this “pre-hook”, we verified the official <a href="https://reactjs.org/blog/2022/03/29/react-v18.html">React changelogs</a>, then <strong>upgraded the React package</strong> and started to get the errors we planned to see, such as the ReactDom package that changed its API:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/988/0*J40K3OsnDz8ilx7N" /></figure><p>Even in the test env as it follow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/994/0*7rvhWpBe7ScHor-m" /></figure><p>By analyzing these errors we changed the deprecated render method and also updated the testing-library/react in order to still get unit test run successfully.</p><p>Since we were already using functional components, the useEffects minor changes didn’t affect us, but we added the newest StrictMode to verify that (it’s available only in dev mode).</p><p>Another major change in this React version is related to the Suspense usage and its tree, that is now always consistent. We were not experiencing any issues.</p><p>Lastly, we needed to <strong>upgrade RecoilJS</strong> to the latest version in order to support the latest React version, otherwise the App would crash as soon as it got the first state.</p><p>And here it was, <strong>our migration was complete</strong>.</p><p>We needed to upgrade these few things to get our migration process done for all our micro frontends applications.</p><p>This process was made easy by our foresight in bringing the latest version of the packages that we were using, <strong>without any fear</strong> under any respect, e.g. time, effort or boring stuff that needed to be done.</p><h3>Takeaways: always manage to upgrade your dependencies and approaches</h3><p>As I said, we were migrating from a codebase in React16.</p><p><em>How many of you are updating their dependencies any time a new major version is released?</em></p><p>A good way to reduce the effort and hard times during migration is to <strong>schedule an “upgrade task”</strong> during the sprint as a tiny workload, in order to avoid a bulk upgrade that may lead into a huge waste of time.</p><p>Of course, we need time to make the updates but it’s more under control to update a few things instead of a full codebase.</p><p><em>“Yeah, ok, but my manager/PM does not let me schedule these maintenance tasks!”</em></p><p>Unfortunately, I heard a lot of people experiencing this issue. <strong>Speak to your manager</strong> in order to let him/her understand the importance of being up to date with your tech stack, also for security reasons.</p><p><em>“I hate upgrading or auditing my dependencies, it’s boring and very hard to accomplish!”</em></p><p>This feeling should not exist in a good environment.</p><p>Sure, it’s not fun to audit and update dependencies, but it’s part of our job and our responsibilities.</p><p><em>Be a better developer, upgrade your deps.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4c41b0b74a1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/growens-innovation-blog/upgrading-to-react18-is-easy-f4c41b0b74a1">Upgrading to React18 is easy</a> was originally published in <a href="https://medium.com/growens-innovation-blog">Growens Innovation Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Optimize the User Experience and Performance via Node.js and Lighthouse]]></title>
            <link>https://medium.com/better-programming/optimize-the-user-experience-and-performance-via-node-js-and-lighthouse-bfd8107fe248?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfd8107fe248</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nodejs]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Wed, 17 Aug 2022 17:17:16 GMT</pubDate>
            <atom:updated>2022-08-17T17:17:16.295Z</atom:updated>
            <content:encoded><![CDATA[<h4>Tips to improve both at the same time</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/1*VPt7aKTugk3VXntCp0mhsQ.png" /><figcaption>Photo by <a href="https://unsplash.com/@nhoizey?utm_source=medium&amp;utm_medium=referral">Nicolas Hoizey</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a> | image height altered</figcaption></figure><blockquote>Just think about it: why should you concentrate your energy in optimizing the user interface and the user experience of your application instead of focusing on the performance side of the whole thing?</blockquote><p>I believe that UX/UI improvement can lead to better performance. The product lead and tech people are the ones that will enjoy the benefits.</p><p>Recently, I implemented an automatic post-build pipeline to automate visual and performance testing through Lighthouse. We were collecting metrics, screenshots, testing, and performance results, and after manually analyzing those, we were achieving some changes, some UX improvement, some features removals, and so on.</p><p>We achieved a lot of improvements and a good historical chart over the Grafana Dashboard of any kind of release in our frontends code base (we are using a micro frontend architecture).</p><p>Let’s dive into it these improvements.</p><h3>What Is the Scenario?</h3><p>I worked for a popular Italian email marketing platform that is a top-quality multichannel cloud platform used by more than 10,000 customers to improve their email and SMS marketing strategies.</p><p>We were working to give the best experience to the end user by improving the performance, the user interface, and the user experience.</p><p>The platform has many features and pages used daily, and because of this, every release counted. We were working on a micro frontend architecture and delivered more than 30 releases per project per week.</p><p>Apart from e2e, a/b testing, stress test, etc., we wanted to monitor every frontend release to check if we made an improvement on the UI/UX or the client-side performance.</p><h3>Which Is the Best Solution for Our Case?</h3><p>We thought a lot and proposed many hypothetical solutions with pros/cons. We finally ended up with a custom implementation in our Jenkins pipelines of Lighthouse, using Node.js, Puppeteer, Prometheus, and Grafana.</p><p>We were using Lighthouse metrics to monitor the new development, porting tasks, UI/UX improvements, performance, and so on.</p><p>By collecting those metrics, we could also have historical data to compare the “old” and the “new” via Prometheus and Grafana. Of course, everything should be portable, so we used Docker under the hood to be portable and deploy everything on our cloud provider (AWS).</p><h3>What Technologies Were Used?</h3><p>All the proposed technologies were open source libraries. Here’s what we used:</p><p>Puppeteer — a node library that provides a high-level API to control Chrome or Chromium over the DevTools Protocol. So, you have a Chromium instance running in the background with full control!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Eq_Y5YZS9GOe2iEx" /></figure><p>Prometheus — an open source system for data modeling and time series DB. We used this as data provider for Grafana.</p><p>Grafana — an open source analytics and monitoring solution. It permits you to build your dashboard and boost the observability of your apps.</p><p>Lighthouse — an open source, automated tool for improving the quality of web pages made by Google. Its architecture is built around Chrome Debugging Protocol which is a set of low-level APIs to interact with a Chrome instance. It interfaces with a Chrome instance.</p><p>The Audits came from the new modern web standards such as First Contentful Paint on page, render time, etc. You can find more on <a href="https://web.dev/measure/">https://web.dev/measure/</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/0*p6KMhXblcc9D7Epc" /></figure><p>We chose open source projects because we truly believed in open source. Our project will soon be available on an open source repository.</p><h3>How We Implemented the Solution</h3><p>We tried a lot of different architecture and implementations, and we ended up doing the following:</p><ul><li>building our solution on a node instance</li><li>executing a web server for our APIs within a headless browser (puppeteer) running in the background</li><li>getting the Lighthouse metrics</li><li>writing the metrics on S3/disk</li><li>collecting them via Prometheus so we could finally retrieve it from Grafana</li></ul><p>Here is our architecture schema:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/751/0*1kpCWiWlNlY2B0uc" /></figure><p>Our node instance served our endpoint to collect the metrics from our Jenkins pipeline via the cURL bash command.</p><p>The API executed the lighthouse test on the URL passed as a parameter in the request so we could redirect our browser (via a puppeteer instance) to the correct page.</p><p>Of course, our platform had a form authentication, so we needed to authenticate to our demo platforms in the first place. To give you an example of the solution, I will show you a snippet of our authentication flow through puppeteer and Node.js.</p><p>As we used Puppeteer, we reproduced any kind of actions of a real user. So we would click on the button, type in the inputs, and move the mouse to a direction on the page to simulate the users’ actions.</p><p>In the following snippets of code, you can see how we implemented the signIn function and how the puppeteer API worked:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d6a56ca130a980e31e42b78dea14de59/href">https://medium.com/media/d6a56ca130a980e31e42b78dea14de59/href</a></iframe><h3>What Are the Results of This Project?</h3><p>We managed to build our solution and attach our automation to every micro frontend application via a post-build trigger in Jenkins. This would trigger an API for collecting metrics for any page or feature.</p><p>Here is an image from our local dashboard retrieving a page metrics, its score, times, audits, and so on:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*v0MdCUx9ImjuG4lD" /></figure><p>By using this tool, we permitted the product and design team to control their customer journey and user flow / UX performance. We enabled the tech team to understand whenever there was an issue in a specific release or a big improvement in terms of performance.</p><blockquote>Funny story: we changed the way a CDN was caching and delivering the assets and we managed to see the change in our metrics thanks to Grafana historical charts.</blockquote><h3>Takeaways</h3><ul><li>We believe that Lighthouse is a great tool for analyzing and monitoring our applications.</li><li>The biggest challenge was implementing the platform’s authentication and business logic inside a container, but we made it!</li><li>Collecting metrics on pre- and post-release has allowed us to be more aware of our goal, and it allows us to have a big picture of the whole application design to improve the UX</li><li>Improving the product development process</li></ul><blockquote>My final tip is to always try to improve and automate everything!</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfd8107fe248" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/optimize-the-user-experience-and-performance-via-node-js-and-lighthouse-bfd8107fe248">Optimize the User Experience and Performance via Node.js and Lighthouse</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Upgrading To React 18 Isn’t That Hard. Here’s How To Do It.]]></title>
            <link>https://medium.com/better-programming/upgrading-to-react-18-isnt-that-hard-here-s-how-to-do-it-bf054418b782?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf054418b782</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[micro-frontends]]></category>
            <category><![CDATA[webpack]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Mon, 15 Aug 2022 14:41:03 GMT</pubDate>
            <atom:updated>2022-08-15T14:41:03.226Z</atom:updated>
            <content:encoded><![CDATA[<h4>Migration made easy</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Rm7QMLypVSs6Dhab" /><figcaption>Photo by <a href="https://unsplash.com/@amenabarladrondeguevara?utm_source=medium&amp;utm_medium=referral">Ignacio Amenábar</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>We read a lot of people and companies having issues with the migration from a previous version of React library to the latest version, the React18, and thought it would be hard to upgrade our micro frontend applications from React16 to React18, with RecoilJS and all the tests.</p><p><em>It turns out that no, it was not that hard. Actually, it was pretty easy!</em></p><p>We did it pretty fast, without breaking anything. We migrated the whole application to the latest React, recoil, and testing library version without experiencing any issues.</p><p>In this article, we are going to analyze the actions that we made in order to get an easy migration to a newer version of the library.</p><h3>What’s New in React18?</h3><p>React-dom API is changing. This is the fastest answer to the question.</p><p>This article is not meant to be an in-depth journey into React18 because a lot of things were limited or deprecated before this version came out, and the other features are just little changes (such as renderToPipeableStream or useEffect or StrictMode).</p><p>Sure, we are reflecting all of these changes from our point of view, (React16 code base), where we are already using functional components for easier usage of the hooks, such as useEffects.</p><h3>Migrating to React18 in a Few Easy Steps</h3><p><em>Again, this is our personal experience. It might be different for others or in other environments.</em></p><p>First of all, we needed to clean all the old dependencies and check for security issues for the others via npm audits. It’s always about the node modules.</p><p>After this “pre-hook,” we verified the official <a href="https://reactjs.org/blog/2022/03/29/react-v18.html">React changelogs</a>, then upgraded the React package and start to get the errors we planned to see, such as the ReactDom package that changed its API:</p><figure><img alt="warning: reactdom.render is no longer supported in React 18. use createRoot instead. Until you switch to the new API, your app will behave as if it’s running React 17." src="https://cdn-images-1.medium.com/max/988/0*J40K3OsnDz8ilx7N" /></figure><p>Even in the test env, the error looks as follows:</p><figure><img alt="same message as previous image" src="https://cdn-images-1.medium.com/max/994/0*7rvhWpBe7ScHor-m" /></figure><p>By analyzing these errors, we changed the deprecated render method and also updated the testing-library/react to still run the unit test successfully.</p><p>Since we were already using functional components, the useEffects minor changes don’t affect us, but we added the newest StrictMode to verify that (it’s available only in dev mode).</p><p>Another major change in this React version relates to the Suspense usage and its tree that is now always consistent. We were not experiencing any issues.</p><p>Lastly, we needed to upgrade RecoilJS to the latest version to support the latest React version. Otherwise, the app would crash when it gets to the first state.</p><p>And here we go, we’ve just finalized our migration.</p><p>We needed to upgrade these few things to get our migration process done for all our micro frontends applications.</p><p>This process was made easy by our foresight in bringing the latest version of the packages that we are using without any fear of the time, effort, and boring stuff that needed to be done.</p><h3>Takeaways: Always Upgrade Your Dependencies and Approaches</h3><p>As I said, we were migrating from a code base in React16.</p><p><em>How many of you are updating your dependencies any time a new major version is released?</em></p><p>A good way to reduce the effort and hard times during migration is to schedule an “upgrade task” during the sprint as a tiny workload to avoid a bulk upgrade that may lead to huge time wasting.</p><p>Of course, we need time to make the updates, but it’s more under control to update a few things instead of a full code base.</p><p><em>“Yeah, OK, but my manager/pm does not let me schedule these maintenance tasks!”</em></p><p>Unfortunately, I heard a lot of people experiencing this issue. Speak to your manager to let them understand the importance of being updated with the tech stack, and also include that it’s good for security reasons.</p><p><em>“I hate upgrading or auditing my dependencies. It’s boring and very hard to accomplish.”</em></p><p>This period should not exist in a good environment.</p><p>Sure, it’s not fun to audit and update dependencies, but it’s part of our job and responsibilities.</p><p><em>Be a better developer, and upgrade your dependencies.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf054418b782" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/upgrading-to-react-18-isnt-that-hard-here-s-how-to-do-it-bf054418b782">Upgrading To React 18 Isn’t That Hard. Here’s How To Do It.</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Use Conventional Commit Messages to Improve Team Communication]]></title>
            <link>https://medium.com/better-programming/use-conventional-commit-messages-to-improve-team-communication-4c7d9cc8f939?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/4c7d9cc8f939</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[clean-code]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Wed, 03 Aug 2022 16:46:35 GMT</pubDate>
            <atom:updated>2022-08-03T16:46:35.465Z</atom:updated>
            <content:encoded><![CDATA[<h4>With wdyd and other platforms</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sYvXOKKiqDAGVo7J" /><figcaption>Photo by <a href="https://unsplash.com/@juniorferreir_?utm_source=medium&amp;utm_medium=referral">Júnior Ferreira</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Sometimes, when working in a team or open source organization, you may misspell a message or make errors in your repository&#39;s commits. These errors can spread through the code base of a huge product or tech stack.</p><p>To me, it’s really important to be fully transparent on the coding side and to be communicative and descriptive in developing a project, a product, or even a utility tool written by devs for devs.</p><p>In this article, we are going to talk about conventional commits, what is important, and how to write a good commit message to have full control over your code base.</p><p>I’ve created a simple project to help new developers/students approach the Conventional Commits in their own or professional projects.</p><h3>What Are Conventional Commits?</h3><p>It’s a specification to have a readable human commit message. It provides an easy set of rules for creating an explicit commit history by declaring a scope, relating an issue/story/bug, and adding some keywords in the subject/message or footer of your commits.</p><p>Here’s an example of a commit message with a description and breaking change footer:</p><blockquote>feat: allow provided config object to extend other configs</blockquote><h3>Why Should You Implement the Conventional Commits Rules?</h3><p>Being more descriptive in coding will give you the following advantages:</p><ul><li>You can automatically generate great changelogs on your projects and semantically determine the version bump</li><li>It will be easier to determine the nature of the changes to the teams by using some fundamental keywords (feat, chore, revert, etc.…)</li><li>By using hashtags, you can trigger workflow process (such as closing issues or stories)</li><li>Make it easier for third-party people to join the team, so they can start contributing after a low onboarding effort</li></ul><h3>How Wdyd Works</h3><p>The npm package, wdyd, was created as a support and utility tool in order to try out the conventional commits standard and implement it in your projects. It is also more friendly for newbie people in the software development industry.</p><p>The node script replicates and formats the message by taking in valuable user input. It has two modes: manual and interactive.</p><p>To get started, you need to install the package globally by using the following command:</p><blockquote>npm i -g wdyd</blockquote><h3>Interactive Mode</h3><p>By using the inquirer package, the user will be prompted with a couple of questions about the nature of its changes, and by choosing the type, the utility will create a commit message with you step by step. It would be easy for someone to approach this kind of message for the first time using the interactive mode.</p><p>The questions will be:</p><ul><li>Select the one that fits your changes. What did you do? (mandatory)</li><li>What scope did you focus on? (mandatory)</li><li>Describe your change in an imperative way (mandatory)</li><li>Include the motivation for the change and contrast this with previous behavior</li><li>Type The footer should contain any information about Breaking Changes and is also the place to reference GitHub issues this commit closes</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*M2Bocdgvv0jG-Q_D" /></figure><h3>Manual Mode</h3><p>Is for more mid/senior level developers (yes, no one should stop from learning). In this case, you can run <em>wdyd -h</em> to get all the info about the commands you can run. In the following image, you can see the list of possible commands you can run:</p><figure><img alt="Abridged list of commands: -v, -h, build, chore, ci, docs, feat, fix, perf, refactor, revert, style, test, help" src="https://cdn-images-1.medium.com/max/1024/0*bWOWn63jEsNRnLek" /></figure><p>You can run the following:</p><blockquote>wdyd e2e ‘signin page tests’ ‘Following the #34 issue on testing, we are now covering 93% of the code’</blockquote><p>To commit an e2e implementation over your sign-in page that links the #34 issue.</p><h3>How to Write a Good Commit Message</h3><p>You can have the full specification on the <a href="https://www.conventionalcommits.org/en/v1.0.0/">conventional commits website</a>, but here are some important tips to keep in mind when writing a commit message.</p><p>Any commit must have a prefixed type, such as feat, fix, or chore, to identify the context of the changes. If you are introducing a breaking change in your code base, you need to specify a ! right after the type.</p><p>A scope, inside the parenthesis right after the prefixed word, should be inserted when we have a short message or a project scope related to all the changes made in the commits, such as: feat(signin) or fix(product-page).</p><p>A mandatory part when we are composing our message is the description. It should be more descriptive, imperative, and not too long. Drop just a line, like:</p><blockquote><em>fix: object parsing issue when passing nullable values</em></blockquote><p>A longer commit body may be provided after the short description, providing additional contextual information about the code changes, such as:</p><blockquote>The page was giving a fatal error and blocked the user navigation flow. Now, we’re logging the error and not blocking the user flow anymore.</blockquote><p>If anything inside your commits is a breaking change, such as a deprecation or a deps change, it’s good to write it down as a footer of our commit message. Using BREAKING-CHANGE will help highlight the thing we’ve changed. For example:</p><blockquote>BREAKING CHANGE: non nullable values are now throwing just a warning message and not a fatal error.</blockquote><p>So, for example, our commit message should be composed like this:</p><blockquote>fix!(product-page): object parsing issue when passing nullable values</blockquote><blockquote>The page was giving back a fatal error and blocked the user navigation flow. Now we’re logging the error and no more blocking the user flow.</blockquote><blockquote><em>BREAKING CHANGE: non nullable values are now throwing just a warning message and not a fatal error.</em></blockquote><h3>Conclusion</h3><p>When working in a team or collaborating with others, it is always good to have guidelines or rules in our code and especially in our code base for better communication.</p><p>Conventional commits is embraced by a lot of people and companies. This tool is a simple implementation to help other devs or people to understand the logic behind and improve their team’s communication.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4c7d9cc8f939" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/use-conventional-commit-messages-to-improve-team-communication-4c7d9cc8f939">Use Conventional Commit Messages to Improve Team Communication</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Covid19 — Supermarket waiting times — How it was made]]></title>
            <link>https://codeburst.io/covid19-supermarket-waiting-times-how-it-was-made-6c9f2ede4b5a?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c9f2ede4b5a</guid>
            <category><![CDATA[python]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[flask]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 14:53:29 GMT</pubDate>
            <atom:updated>2021-04-16T14:53:29.712Z</atom:updated>
            <content:encoded><![CDATA[<h3>Covid19 — Supermarket waiting times — How it was made</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*r3NyU0pVq5LOMEoK" /></figure><h3>The context</h3><p>In March 2020 the world froze. A damn virus has spread across the globe and people have locked themselves up in their homes, safe.</p><p>Getting out was a risk. Go shopping, another one.</p><p>The problem is: the longer you stay out and in contact with other people, the more likely you are to contract the virus. Especially in closed and unventilated environments.</p><p>The project that I am presenting to you was created primarily for personal use and then, by word of mouth, it became public use worldwide (geographically). The project was not for profit but only to help others.</p><p>Since June 2020 it has been discontinued due to the slight improvement in cases and the clarity that has been made about the virus, as well as the various security measures that have been applied at the health level.</p><h3>The reason why</h3><p>In the days following the global lockdown, supermarkets, pharmacies and parapharmacies were attacked by people in search of basic goods and necessities. Immediately after the announcement of the lockdown, many supermarkets struggled to manage the influx of people, forcing them to gather outside the supermarket, standing in line and waiting to enter the building.</p><p>The gathering of people in line in front of shopping malls and pharmacies made me think. Why not create some sort of tracking based on Google Maps data? Kind of how it works for traffic.</p><p>So the goal was to create a map with the various points of interest, such as: food, bakers, pharmacies, supermarkets, liquor stores etc. where the waiting times retrieved by Google were shown (at the time this API was not public, that is, there was no endpoint, while now it *) giving the user the possibility to add a temporal feedback for the store in which he was located.</p><p>The use of the map aimed to schedule the exit of the house towards our point of interest at the moment in which there was the least waiting time to enter.</p><p>Crowdsourcing was then fundamental for the success of all this, since Google’s data is based on the time, the popularity of the place and how many devices are nearby. User feedback was therefore crucial.</p><p>* Google now displays the wait data in one place directly in Maps.</p><h3>Costs</h3><p>The project is open source and development costs are not considered as those developed for personal use and then immediately shared publicly.</p><p>At the start the whole project, i.e. Redis, API backend in Python and the frontend resided on my Raspberry PI 3B model. After about 7 days from the publication online, the site already counted about 10K visits per day and Raspberry was no longer able to satisfy the requests at the same time.</p><p>So I decided to move everything to the cloud using OVH and DigitalOcean for the backend and Github Pages for the frontend.</p><p>The backend, with Redis and the API in Python, I replicated on 4 VPS in the cloud divided as follows: 3 DigitalOcean (New York, London, San Francisco) and OVH (Europe).</p><p>The specifications were almost the same, that is 2GB of Ram and 3.2GHz dual core.</p><p>In total, I spent about $ 25 per month. The total is $ 75 for 3 months.</p><p>For the domain, not being a commercial project, I reused my former domain thejoin.tech, creating the subdomain <a href="https://translate.google.com/translate?hl=it&amp;prev=_t&amp;sl=it&amp;tl=en&amp;u=https://covid19-waiting-time.thejoin.tech/">https://covid19-waiting-time.thejoin.tech/</a></p><p>The included traffic was 10GB per month, so it wasn’t a backend issue.</p><p>By importing, via git, all the setup on the Cloud allowed me to satisfy (in the whole life cycle) more than 1Mln of users and more than 2.1Mln of sessions in 3 months of the life of the project with more than 1.5K contemporary user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*mkY353AmExgy07KA" /></figure><h3>How it worked</h3><p>I’ll briefly explain the idea and the mechanism behind it. For the more technical part <a href="https://thejoin95.medium.com/covid19-supermarket-waiting-times-a-2020-project-f3fb8efa540e">I leave you the link to the post</a>. The Github repository is available on my profile: <a href="https://github.com/TheJoin95/covid19-market-waiting-times">https://github.com/TheJoin95/covid19-market-waiting-times</a></p><p>The idea was born with a simple map created in JS (using Leaflet.js) where the various markers of the various points of interest were added, previously retrieved from the Here and Google API.</p><p>The data was persisted on Redis and, thanks to the Geo operator, could be easily searched through geospatial queries in order to provide geo-localized data and markers.</p><p>Redis was the most logical choice to provide fast, precise responses and with a TTL on persistence to the various requests so as not to overload the memory.</p><p>All the functionalities, from the search by location or by address / place to the WebIAM through to the map navigation and crowdsourcing features have been developed incrementally and thanks to the help of some contributors for the graphic part. All this within 25 days, after 8 hours of work.</p><p>The frontend does not use any framework other than the task runner Grunt to be able to include the various pieces of html, minify the css / js / html files and the web workers to be able to use it in the form of PWA (progressive web app). This choice made development very fast with no dependency or compatibility issues. However, compatibility is guaranteed both on mobile (being responsive) thanks to polyfill.</p><p>The APIs were instead developed in Python and deployed on the 4 instances mentioned above and use Flask as a micro-framework for API and uWSGI as a web server.</p><p>I must say that uWSGI was the best choice due to the low level of configuration it makes available to us.</p><h3>Turn-ups</h3><p>There have been a lot of likes, tweets and shares on all kinds of social media and blog / news sites. I was really pleased to help people all over the world, to receive negative and positive feedback in order to improve a tool that was helping thousands of people in the same situation and with the same problem.</p><p>It was certainly one of the best projects I’ve worked on and I’ve had the pleasure of dedicating time to, as well as my passion. Understanding how a prototype released locally on the Raspberry at home to then be made public for friends and then globally taught me a lot… this project was aimed at helping myself, but in the end it also helped other people. I may not have solved many problems or complexities, but the testimonies make me understand that there was a little help… and this is enough for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c9f2ede4b5a" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/covid19-supermarket-waiting-times-how-it-was-made-6c9f2ede4b5a">Covid19 — Supermarket waiting times — How it was made</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Covid19 — Supermarket waiting times — A 2020 project]]></title>
            <link>https://codeburst.io/covid19-supermarket-waiting-times-a-2020-project-f3fb8efa540e?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3fb8efa540e</guid>
            <category><![CDATA[flask]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Fri, 16 Apr 2021 14:51:17 GMT</pubDate>
            <atom:updated>2021-04-16T14:51:17.108Z</atom:updated>
            <content:encoded><![CDATA[<h3>Covid19 — Supermarket waiting times — A 2020 project</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*gfUOZtAPRdQm7cVu" /></figure><h3>The context</h3><p>In March 2020 the world froze. A damn virus has spread across the globe and people have locked themselves up in their homes, safe.</p><p>Getting out was a risk. Go shopping, another one.</p><p>The problem is: the longer you stay out and in contact with other people, the more likely you are to contract the virus. Especially in closed and unventilated environments.</p><p>The project that I am presenting to you was created primarily for personal use and then, by word of mouth, it became public use worldwide (geographically). The project was not for profit but only to help others.</p><p>Since June 2020 it has been discontinued due to the slight improvement in cases and the clarity that has been made about the virus, as well as the various security measures that have been applied at the health level.</p><p>In this technical article I will briefly describe how the project was developed and the architecture behind it.</p><h3>Architecture</h3><p>Initially the project resided on my raspberry, in a local network. Not having the need to go out on the public network, the performances were obviously excellent. Only one user.</p><p>Subsequently, thanks to the port forwarding of the router and a subdomain managed through dynamic dns, I made it accessible from the outside.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TyK0HwA25Q0TVcIM" /></figure><p>The first 10 days Raspberry managed to sustain good performances despite having Redis, uWSGI, API and the Frontend on the same machine.</p><p>It managed about 500/800 people a day.</p><p>The problems came in early April when, by word of mouth, the project began to expand. The daily people were around 3000/5000 people with around 8000 page views. Too much for my poor Raspberry.</p><p>Initially I thought that creating a local cluster was the right choice. Obviously it wasn’t. So I decided to rely on an old provider I was relying on for other projects: OVH.</p><p>I bought a VPS with 2vCore, 4GB of RAM and 80GB NVMe, for two months, located in the Strasbourg datacenter. A decent car.</p><p>Thanks to Git and the configurations I had created locally on the Raspberry linux system (debian based), the setup on the new machine was not too difficult and not at all time consuming. An hour to put everything online and 15 minutes to change the dns.</p><p>I had several subdomains: 1 for the API, 1 for the frontend. The subdomain for the API had a suffix to determine the location of the server so as to set everything up to be able to scale to other geographical areas.</p><p>The frontend still resided on the Raspberry, thanks also to the NGINX cache. After a few weeks I changed this approach and put the frontend on the cloud via Github Pages.</p><p>In mid-April I had another spike in visits: around 100K users per day and over 200K page views. Obviously it all happened while I was sleeping. Classic.</p><p>I was not in the least ready and as a fallback I recreated the environment on raspberry by creating a new API subdomain so that I could use it in the list of domains available in the frontend.</p><p>I was splitting the load on at least two instances. Obviously that wasn’t enough.</p><p>So I decide to use some free credit I had on Digital Ocean.</p><p>After analyzing Google Analytics and the logs, I then decide to buy a machine with the same characteristics as that of OVH on Digital Ocean, but located in New York.</p><p>In fact, the traffic came mainly from the east coast of America and Canada (west coast and east coast). In addition, I had also created a smaller fallback instance in London in case European traffic increased.</p><p>At the same time, after replicating the environment and setting up the machine, I optimize the code, the requests and the caching of the various requests / responses.</p><p>The project born for personal purposes was becoming popular in Canada and America.</p><p>So I decide to set up another, smaller, Digital Ocean machine located in western America.</p><p>Within half a day I can therefore re-establish and optimize everything, both from the point of view of architecture and from the point of view of software.</p><p>In summary: 4 machines in total that managed the backend part providing the APIs via uWSGI and Redis located in: France, England, East America and West America. Github Pages for the frontend, which was deployed through Continuous Deployment of Github and the use of Grunt as a task runner.</p><p>An example of an API domain was: api-geo-fr.domain.ext</p><p>Separate notes: the load sharing is based on the law of large numbers. Each connected client was assigned an API subdomain for its session from all available configured subdomains. If the subdomain was offline, it scaled to the next and so on until it gave an error and displays the “offline service” message.</p><p>Surely I could do better and manage the “cloud computing” issue in another way and with other services / providers.</p><p>During the project my priority was to provide the most up-to-date and truthful data possible with the least downtime. I often found myself managing problems for the first time that I had never seen before but thanks to workaround and transversal knowledge I was able to solve.</p><h3>How it worked</h3><p>This project aimed to avoid crowds of people in various supermarkets and pharmacies during the covid-19 pandemic. Based on the geolocation of the device, it will show various points of interest such as supermarkets, pharmacies, clinics, bars etc., with an estimate of the waiting time and a forecast of the next hour.</p><p>The front end uses Open Street Map with the Leaflet.js library.</p><p>It also uses the client-side geocode.xyz API to retrieve the address and city details from the geographic coordinates retrieved from the HTML5 API.</p><p>The backend is powered by Flask, a micro-framework for building some simple APIs to retrieve data from Google Places.</p><p>NOTE: This project does not use the official Google API, but works via some sort of workaround / bug. We can call it scraping, but that’s not the right word. The project was carried out in March 2020.</p><p>The data comes from Google Maps, like traffic data, in “real time” (according to Google’s terms). The data is also based on last week’s data, to have a history (based on Google), the time spent inside a place and the estimated waiting time to be able to complete the purchase. In the latest version, data is also crowdsourced through user feedback that anyone can provide by clicking on a location marker on the map.</p><p>The wait time is also based on the current popularity (readme as realtime) of a specific place. This feature isn’t available for all places, but for the vast majority it is. In this way, the estimated waiting times can still be reliable, since the calculations made on these data try to take into account the emergency variables such as social distancing, less influx of people indoors, etc. The data is then divided into hours and weekdays.</p><p>All times are to be considered estimates.</p><p>In fact, the same data that you would see on Google is used, i.e. the data within the local business.</p><p>Please note that sometimes a place may have a parking area or other things where geolocation can make mistakes. I couldn’t detect where the people are, if they are people or cars, how many people are in line etc. etc. The estimates are based on data that comes from Google with an additional formula to get an approximate wait time. This relative error can change from place to place.</p><h3>Backend</h3><p>The backend was developed in Python 3.6 using the Flask micro-framework to build the project’s API. The web services are then made available by the uWSGI web server which is configured with various workers to improve performance.</p><p>In fact, each API instance runs with a thread pool to allow the handling of many more simultaneous requests. This, of course, must be modulated according to the computational capabilities we have (CPUxRAM).</p><p>On the Raspberry I had certain threads, while on the other VPSs I had more threads.</p><p>Obviously there is always a limit, otherwise we could only have the opposite effect and therefore not an improvement.</p><p>The various endpoints available were:</p><p>● / geocode</p><p>● / places / get-waiting-times</p><p>● / places / get-by-name</p><p>● / places / explore</p><p>● / logger</p><p>● / places / browse</p><p>● / feedback</p><p>Geocoding was provided by the Here API and Geocode.xyz.</p><p>Geocoding was essential to derive the correct coordinates of the device or of an address that was specified, since the location of the device was optional.</p><p>The Here API has also been used for the places, browse, get-by-name and explore endpoints, to derive the actual place to search in the database from a place name or address.</p><p>The feedback endpoint relates to the part dedicated to crowdsourcing so as to update the times of the places for which users give their feedback, based on the geolocation to testify their presence on the site.</p><p>The key endpoint is clearly the get-waiting-times which uses the Redis cache connection to be able to search and persist places with their waiting times.</p><p>The application does not persist personal data of users.</p><p>Each Flask instance has a thread pool to process multiple requests simultaneously without conflicting. An access-control-origin header is set on each endpoint that does not allow the use of the API on other sites other than the specified domain, i.e. covid19-waiting-time.thejoin.tech.</p><p>This check was necessary as I had limited resources. In any case, the project could be distributed by anyone once the repository was cloned from Github.</p><h3>Frontend</h3><p>The frontend was developed with a very simple stack, Vanilla Javascript and Grunt.</p><p>The CSS was built ad hoc as the page only featured a full screen map.</p><p>The project was not very complex and in fact not too many lines of code are needed to manage everything.</p><p>Grunt allows us to use polyfills and to split our html code into multiple files and then include them gradually. Everything will then be merged and minified.</p><p>The site is also a Progressive Web App and uses WebIAM principles to make the information on the application accessible to all. Clearly it is responsive and features are mainly shown via modals above the map canvas.</p><p>The User Experience and User Design were fundamental for the success of the entire web application. Making your application usable and immediately usable helps users navigate it. As soon as we land on the site we will be offered a modal that contains the main information and a small getting started to immediately start browsing the information.</p><p>The color encoding of the various pins or buttons on the map was equally crucial.</p><p>This feature also remains for those with color blindness.</p><h3>Conclusions</h3><p>It was certainly one of the best projects I’ve worked on and I’ve had the pleasure of dedicating time to, as well as my passion. Understanding how a prototype released locally on the Raspberry at home to then be made public for friends and then globally taught me a lot… this project was aimed at helping myself, but in the end it also helped other people. I may not have solved many problems or complexities, but the testimonies make me understand that there was a little help… and this is enough for me.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3fb8efa540e" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/covid19-supermarket-waiting-times-a-2020-project-f3fb8efa540e">Covid19 — Supermarket waiting times — A 2020 project</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Netflix Cover Generator — A NuxtJS Project]]></title>
            <link>https://codeburst.io/netflix-cover-generator-a-nuxtjs-project-f20ea24e960f?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/f20ea24e960f</guid>
            <category><![CDATA[youtube]]></category>
            <category><![CDATA[canvas]]></category>
            <category><![CDATA[vuejs]]></category>
            <category><![CDATA[nuxtjs]]></category>
            <category><![CDATA[netflix]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Mon, 22 Feb 2021 16:48:26 GMT</pubDate>
            <atom:updated>2021-03-02T00:29:49.889Z</atom:updated>
            <content:encoded><![CDATA[<h3>Netflix Cover Generator — A NuxtJS Project</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*I8kGYiAZRwTHK0BH" /><figcaption>Photo by <a href="https://unsplash.com/@charlesdeluvio?utm_source=medium&amp;utm_medium=referral">Charles Deluvio</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>The context</h3><p>For our podcast, there was a need to speed up the YouTube cover creation process. The cover needed to be interesting, contain the right information, and in the right format.</p><p>In <a href="https://www.schrodinger-hat.it/">Schrodinger Hat</a>, we only have one graphic designer, Francesca. For this reason we always try to overload it with requests, so as to automate the process as much as possible.</p><h3>Why a Netflix Cover Generator?</h3><p>Well, if you don’t learn from the best who should you learn from?</p><p>We really like the covers of the various TV series and movies in the Netflix catalog. The inspiration comes from their platform. The style clearly refers to that of Netflix (albeit with a few changes and fewer details).</p><p>We took the example of the Netflix title as a reference; a testing page dedicated to positioning and footprint.</p><h3>What is the project really about?</h3><p>The project is a small application that makes a drag-n-drop editor so as to insert images and edit texts and clutter. It’s fully customizable and doesn’t require too many skills to tweak.</p><p>The codebase is <a href="https://nuxtjs.org/">Nuxt.js</a> (VueJS framework) and <a href="https://konvajs.org/">KonvaJS</a>, a JS library for HTML5 canvas interpolation.</p><p>The repository is available on our <a href="https://github.com/Schrodinger-Hat/netflix-show-generator">Github</a>.</p><p><a href="https://github.com/Schrodinger-Hat/netflix-show-generator">Schrodinger-Hat/netflix-show-generator</a></p><p>The demo is available on our <a href="https://netflix.schrodinger-hat.it/">demo website</a>.</p><p><a href="https://netflix.schrodinger-hat.it/">Netflix Show Image Generator</a></p><h3>How does it work?</h3><p>Using Konva.JS we initialize a Canvas containing multiple layers, just like a Photoshop project. Each layer encloses a portion of the rendering:</p><ul><li>Background and photos</li><li>Shade</li><li>Headings and text</li><li>Additional layer for additional photos / texts</li></ul><p>It is thanks to this structure that it is possible to have a game of effects, such as the gradient in Netflix style.</p><p>Nuxt handles the KonvaJS API very well and this makes the development and implementation of features easy and extremely fast.</p><p>The Canvas element also offers a very important property such as pixelRatio.<br>This property allows us to export and save our work in high resolution for subsequent modifications or to work with particular formats.</p><p>In this way, the project can solve many problems. Obviously, everything could be improved, starting from the colors that could be selectable and customizable directly during the creation of a “project”. We decided to leave it like this, as if it were a PoC, precisely because it could have interesting implications and because it is our favorite theme.</p><h3>How can I get it to work locally?</h3><p>The project is portable and can be released anywhere. We have chosen Netlify.<br>Locally it will be enough to clone the repository from the link above, install the npm modules and start the dev server via Nuxt.</p><p>In README.md you will find all the instructions :)</p><h3>Future implications or future implementations?</h3><p>We currently use it internally for the production of our podcast YouTube covers, but we do not hide that it could become something else in the future.</p><p>We would like to create a kind of tool to speed up UI / UX testing by simply having the various components in Vue / React / * JS so as to try to render them on a canvas (a bit like if we were making a microfrontend) and verify that it is all correct in terms of design.</p><h3>Conclusion</h3><p>The project was a lot of fun to do. KonvaJS is very intuitive and the API Reference was really useful. Downloading the YouTube cover in high resolution from this tool saved us a lot of time for each uploaded video!</p><p>Our YouTube channel is: <a href="https://www.youtube.com/channel/UC1QLLgrGrPmlaFhS0orykCA">https://www.youtube.com/channel/UC1QLLgrGrPmlaFhS0orykCA</a></p><p>The podcast is only available in Italian.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f20ea24e960f" width="1" height="1" alt=""><hr><p><a href="https://codeburst.io/netflix-cover-generator-a-nuxtjs-project-f20ea24e960f">Netflix Cover Generator — A NuxtJS Project</a> was originally published in <a href="https://codeburst.io/">codeburst</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automate the Publishing Process of Your Podcast With GitHub Actions]]></title>
            <link>https://medium.com/better-programming/youtube-to-anchor-fm-a-github-action-to-automate-the-publishing-process-of-your-podcast-1dbb0fc90560?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/1dbb0fc90560</guid>
            <category><![CDATA[automation]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[podcast]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Sun, 30 Aug 2020 16:19:28 GMT</pubDate>
            <atom:updated>2020-09-09T01:33:14.319Z</atom:updated>
            <content:encoded><![CDATA[<h3>Automate the Publishing Process of Your Podcast With GitHub Actions</h3><h4>Send your podcast from YouTube to Anchor.fm</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TzZJST1i2o7c06o1BCoFIg.png" /><figcaption>The repository cover image</figcaption></figure><h3>The Context</h3><p>During the quarantine period, I started an Italian tech live show on YouTube and a podcast on Spotify and Anchor.fm with some of my friends. The show is called Schrödinger Hat.</p><p>We are enjoying creating this content on the web, but we have encountered some technical issues. Some of them were minor issues that we managed easily during the time, but then there was the major issue.</p><h3>The Issue</h3><p>We encountered some problems by uploading the audio file from YouTube to Anchor.fm, because this action required time, a conversion tool, and you know, in 2020 no one has too much time.</p><p>We started thinking. We searched for some Anchor.fm APIs, but found none, until this conversation happened:</p><blockquote>“Should we create a private Anchor.fm API?”</blockquote><blockquote>“Uhm, I heard something about Github Actions, maybe we can automate the whole process by using it”</blockquote><blockquote>“Shut up and let’s start coding.”</blockquote><h3>The Solution</h3><p>We are managing the whole podcast project trough Github and with the Github Actions, you can automate, customize, and execute your software development workflows right in your repository.</p><p>We developed a Github Action, available on the <a href="https://github.com/marketplace/actions/upload-episode-from-youtube-to-anchor-fm">Github Action Marketplace,</a> that automates the whole publishing process from YouTube to Anchor.fm.</p><p><a href="https://github.com/Schrodinger-Hat/youtube-to-anchorfm">Schrodinger-Hat/youtube-to-anchorfm</a></p><p>The workflow and the action are available for free, it is open source under MIT license.</p><h3>How It Works</h3><p>The Github Action is using youtube-dl library and puppeteer. The first one is an npm module used for downloading the video/audio from YouTube, meanwhile Puppeteer will upload the generated file into the Anchor.fm dashboard (by logging into it).</p><p>The action will start every time you push a change on the episode.json file. You need to specify the Youtube ID of your video. The action uses a Docker image built over ubuntu 18.04. It takes some time to set up the environment (installing dependencies and chromium-browser).</p><h3>How Can I Use It?</h3><p>You can use the latest version of this action from the <a href="https://github.com/marketplace/actions/upload-episode-from-youtube-to-anchor-fm">Github Action Marketplace</a>. In your repository root directory, you should add a episode.json file containing your Youtube video ID, e.g:</p><pre>{<br>  &quot;id&quot;: &quot;nHCXZC2InAA&quot;<br>}</pre><p>Then you can add under the .github/workflows directory for this YAML file:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8fd2bf52b5b0c781aef93fd9020fa52e/href">https://medium.com/media/8fd2bf52b5b0c781aef93fd9020fa52e/href</a></iframe><p><strong>NOTE</strong>: You need to set up the secrets for <em>ANCHOR_EMAIL</em> and <em>ANCHOR_PASSWORD</em>. These environment variables are mandatory as they specify the sign-in account.</p><h3><em>A Little Workflow Explanation</em></h3><p>The above workflow is saying: “Every time you push some changes on the episode.json file, it will setup the “YouTube to Anchor.fm” action with your Anchor.fm account (specify in your secrets) that will download the YouTube video specified, convert it into an audio file (best quality) and upload it into your Anchor.fm account</p><h3>Conclusion</h3><p>We enjoyed building this action on Github Actions and it saves us a ton of time. We are hoping that this will help other creators that are using the same platform. I would suggest that Anchor.fm make some public API to permit developers to push the audio file and managing the whole publishing process better.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1dbb0fc90560" width="1" height="1" alt=""><hr><p><a href="https://medium.com/better-programming/youtube-to-anchor-fm-a-github-action-to-automate-the-publishing-process-of-your-podcast-1dbb0fc90560">Automate the Publishing Process of Your Podcast With GitHub Actions</a> was originally published in <a href="https://betterprogramming.pub/">Better Programming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sorting Hat Experiment | WebAR in pure JS]]></title>
            <link>https://medium.com/ar-vr-journey/the-sorting-hat-experiment-webar-in-pure-js-c53b91863c66?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/c53b91863c66</guid>
            <category><![CDATA[creative]]></category>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[webgl]]></category>
            <category><![CDATA[ar]]></category>
            <category><![CDATA[experiment]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Thu, 19 Mar 2020 05:56:00 GMT</pubDate>
            <atom:updated>2020-03-23T14:36:03.128Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/818/0*Xgv_Ukj_-eh1GUnn.jpg" /></figure><p>The power of <a href="https://arvrjourney.com/">augmented reality</a> in the palm of a hand: Google, with Chrome, is trying to develop and guarantee support for AR and VR by proposing a standard at the level of W3C. The proposals are still in draft and in the proposal phase, but there are already some experiments that can be tried.</p><h3>How to implement an experience in AR</h3><p>There are many applications and experiments with AR technology, while there are few experiments with the same technology directly on the web.</p><p>Despite the investments of many Big Companies on this technology, there is still no real standard for their realization.</p><p>For the native, there are various libraries, tools and frameworks. Google has developed ARCore, which can be implemented on both iOS and Android, while Apple has developed ArKit which however can only be released on iOS.</p><p>If we stop to reflect, the current lingua franca is javascript. The current environment, which everyone has, is the web. It is true, there is no guarantee of performance, due to the large scale of devices that have access to it.</p><p>However, we can still achieve excellent results.</p><h3>The WebGL experiment</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/272/1*M3a3KWEdil5yJxxSkhxssA.png" /></figure><p>About two years ago I implemented a small experiment in WebGL to extend the reality and, in fact, carry out an AR experiment: to implement the talking hat of the famous Harry Potter saga, to sort the various users in the various Hogwarts houses.</p><p>You can see the full project by clicking on the <a href="https://github.com/TheJoin95/sorting-hat-experiment-webgl">Sorting Hat Experiment</a> repo link.</p><p>The result can be visited <a href="https://experiments.thejoin.tech/">here</a> (self- signed certificate).</p><h3>Technologies used for the experiment</h3><p>The experiment was implemented in pure javascript, using the <a href="https://threejs.org/">Three.js</a> library , the native API to retrieve the camera and accelerometer input and making use of the <a href="https://trackingjs.com/">https://trackingjs.com/</a> library for facial recognition (via a MobileNet ).</p><h3>Trending AR VR Articles:</h3><blockquote><a href="https://arvrjourney.com/how-xr-can-unleash-cognition-3bda13026ade">1. How XR Can Unleash Cognition</a></blockquote><blockquote><a href="https://arvrjourney.com/oculus-go-the-nintendo-switch-of-vr-6827e1b91055">2. Oculus Go, the Nintendo Switch of VR</a></blockquote><blockquote><a href="https://arvrjourney.com/expert-view-3-ways-vr-is-transforming-learning-development-487a021e8334">3. Expert View: 3 ways VR is transforming Learning &amp; Development</a></blockquote><blockquote><a href="https://arvrjourney.com/ready-player-one-how-close-are-we-8af973c1cfa0">4. Ready Player One : How Close Are We?</a></blockquote><p>At the time of the experiment, there was still no google project to implement the WebXR API (API to implement the native web AR) in Chrome, nor the version of Three.js, oriented towards the management of a 3D environment in <a href="https://arvrjourney.com/">VR</a>, AR-oriented: <a href="https://github.com/google-ar/three.ar.js">Three.ar.js</a> .</p><h3>How the experiment was implemented</h3><p>The implementation was simple, as the only inputs are the camera of the device (pc or smartphone) and the input of the questionnaire taken from the Pottermore site (a reference site for the Harry Potter saga).</p><p>The critical issues are related to the support of a wide range of devices. The experiment, not using libraries optimized for <a href="https://arvrjourney.com/">AR</a>, suffers from <em>fps lag, </em>on older devices with CPU and GPU not of medium / high range.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/258/1*ThaRgxpoSZyj58F-f20Iww.png" /><figcaption>Example of face recognition in web app</figcaption></figure><p>The greatest optimization, to try to solve this problem, was done in rendering the 3D model of the sorting hat based on facial recognition.</p><p>This process brings a big charge at the CPU and GPU level, since on each tick he has to update the whole canvas (our AR level) and reposition the hat.</p><p>The main optimization was to carry out the facial reconnaissance process only every tot of frames per second, in this way it is possible to guarantee a smooth experience without weighing down the less performing device, effectively levelling all the other higher-end devices. .</p><p>At the start of the quiz, audio files were loaded and played in sequence, based on the choices of the questionnaire, which replicated the scenes of the film and the indecision of the hat.</p><p>At the end of the quiz, the sorting hat decreed the house of belonging and exclaimed its name.</p><h3>Conclusion</h3><p>An experiment of this kind, brought to a more professional level, with the right tools and with more resources, could certainly be useful to JK Rowling in the boom of the saga to further retain the various users.</p><h3>Don’t forget to give us your 👏 !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*yX6T_VDVDq7kqnJU" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fcc7833%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2FARVR%3Ffbclid%3DIwAR3o3Cek44YsQ5uIM2rk9fWCGFnhDthkHbC095-H0CcmYt9FKGpa5UJ2dps&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fcc7833%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e1f2ee7654748bb938735cbca6f0fd3/href">https://medium.com/media/1e1f2ee7654748bb938735cbca6f0fd3/href</a></iframe><figure><a href="https://www.facebook.com/groups/984060571735120/"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*2f7OqE2AJK1KSrhkmD9ZMw.png" /></a></figure><figure><a href="https://upscri.be/ARVR"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*v-PpfkSWHbvlWWamSVHHWg.png" /></a></figure><figure><a href="https://docs.google.com/forms/d/1YBHAY792wL3OslxTQRqcIbRICNeKdeYSiSr2HyVrptU/edit"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Wt2auqISiEAOZxJ-I7brDQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c53b91863c66" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ar-vr-journey/the-sorting-hat-experiment-webar-in-pure-js-c53b91863c66">The Sorting Hat Experiment | WebAR in pure JS</a> was originally published in <a href="https://medium.com/ar-vr-journey">AR/VR Journey: Augmented &amp; Virtual Reality Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Augmented Reality — A brief explanation]]></title>
            <link>https://medium.com/ar-vr-journey/the-augmented-reality-a-brief-explanation-6f73bed865bb?source=rss-dab2a46eef7e------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f73bed865bb</guid>
            <category><![CDATA[creative]]></category>
            <category><![CDATA[marketing-strategies]]></category>
            <category><![CDATA[ar]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web]]></category>
            <dc:creator><![CDATA[Miki Lombardi]]></dc:creator>
            <pubDate>Wed, 18 Mar 2020 17:01:00 GMT</pubDate>
            <atom:updated>2020-03-23T14:36:04.429Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Augmented Reality — A brief explanation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*KgpddPJXJ5tJLpkj215sFw.png" /></figure><h3>What is Argumented Reality</h3><p><a href="https://arvrjourney.com/">Augmented reality</a> (in short, AR) is a technology that expands our physical world by adding various digital layers to it. Unlike virtual reality (in short, VR) it does not create an entire virtual environment and, above all, it does not replace the real environment with a completely virtual one.</p><p>Augmented reality is introduced directly onto the existing environment, adding various sounds, videos, 3D models, graphics and more.</p><p>In short, AR is a vision of the physical / real environment with in addition computer generated images, superimposed on each other, which thus change the perception of reality.</p><p>Once defined what AR is, it will make it strange to know the history of this technology and the various terms associated with it. The first use of such a technology dates back to the years 90, especially in the military sector. From the 2000s onwards, thanks to the advent of smartphones, this technology (which was still used) was rediscovered for commercial use thanks also to interactivity and the use of 3D models.</p><p>After some history, we need to define the macro categories to differentiate certain uses and types of <a href="https://arvrjourney.com/">augmented reality</a> of our day:</p><ul><li>Marker- less</li><li>Marker- based</li><li>Projection-based</li><li>Superimposition-based</li></ul><h3>How can this technology be implemented?</h3><p>It is certainly the first question that each of us asks at the first contact with this technology.</p><p>To answer correctly we must premise that, unlike VR, we must also refer to some principles of computer vision , given that we are in a real environment. It is clear that the levels that we will add can be enhanced with well-defined data types such as images, animations, videos, 3D models and localized audio.</p><p>Knowing the possible types of data we can therefore also know a series of possible devices on which it will be possible to perform the AR such as: monitors, smart mirrors, portable devices, smartphones, smart glasses and so on .. paradoxically it is sufficient to have a device with display and graphics engine (of course, there will be minimum requirements based on usage).</p><h3>Trending AR VR Articles:</h3><blockquote><a href="https://arvrjourney.com/how-xr-can-unleash-cognition-3bda13026ade">1. How XR Can Unleash Cognition</a></blockquote><blockquote><a href="https://arvrjourney.com/oculus-go-the-nintendo-switch-of-vr-6827e1b91055">2. Oculus Go, the Nintendo Switch of VR</a></blockquote><blockquote><a href="https://arvrjourney.com/expert-view-3-ways-vr-is-transforming-learning-development-487a021e8334">3. Expert View: 3 ways VR is transforming Learning &amp; Development</a></blockquote><blockquote><a href="https://arvrjourney.com/ready-player-one-how-close-are-we-8af973c1cfa0">4. Ready Player One : How Close Are We?</a></blockquote><p>Why did we have to refer to computer vision before? Well, because in AR we can implement computer vision technologies such as SLAM (simultaneous localization and mapping), depth tracking (distance between objects) and more.</p><p>This is possible with the support of these hardware / software components:</p><p>1. Camera and sensors — Collect data and allow direct interfacing with the user</p><p>2. Performing CPU and GPU — The computing power to manage all the components, processing and continuous rendering are fundamental tasks but also designed and ensuring stable FPS is of primary necessity. The latest generation smartphones have GPUs and CPUs capable of handling the load of an AR application, while older devices may suffer from FPS lag or overheating</p><p>3. Holographic projection — It is an augmented reality device</p><p>Knowing now, in broad terms, how it works behind an implementation in AR we can therefore analyse the various types.</p><h3>Types of augmented reality</h3><p>1. <strong>Marker-based — </strong>an image recognition algorithm of special images, called markers, is implemented. Markers are images made up of characters, QR codes or special geometric shapes which, if printed and framed with the camera within an AR application, will display the 3D image or model or a digital animation mapped for that marker.</p><p>2. <strong>Marker-less </strong>— in the absence of the printed images, an AR application can still rely on the hardware of the device and use the location using the GPS module. Similarly, data from a compass, gyroscope or accelerometer can be used. In this way the data can be associated with GPS coordinates, with an error radius, and when the user is in that defined radius it will be possible to view our data which can be a digital map, an advertising billboard or anything else</p><p>3. <strong>Projection-based — </strong>Holograms. This type requires special devices since they must project a light beam containing a series of information so that the result is pleasant</p><p>4. <strong>Superimposition-based </strong>— is the replacement of a part of reality or the addition / overlapping of a digital data within reality. An example could be the Ikea AR app which, taken from an object from the catalogue, will be possible to position it inside your home through the camera of our device</p><h3>In which contexts and use cases is it possible to implement an AR experience?</h3><p><a href="https://arvrjourney.com/">Augmented reality</a> can be integrated into many daily activities, in various ways, even if the main field of use is often recreational, such as games such as Ingress or PokemGO.</p><p>At the implementation level, the only limit is often the creativity of the developers because basically everything could be implemented in an AR application, just create it, this is the difficult one.</p><p>For example, in retail, an AR experience could encourage customer engagement and loyalty, as well as facilitate brand expansion and consequently increase sales.</p><p>Another context, always within the same sector, could be to favour customers and guide them in the purchase (such as the example of Ikea), perhaps by providing data on the product, viewing it in 3D, providing indications between the various departments or indicate on a digital map where to find a product.</p><p>There are ideas that can be applied in multiple sectors and in any case could be successful.</p><p>Recently there has been a lot of talk about smart working: we could think of interactive models for learning and / or training purposes, practical chemistry lessons through AR, physics or other subjects.</p><p>AR is a technology that helps and extends reality to accomplish a specific goal.</p><h3>Conclusion: why use such innovative technology?</h3><p>Surely a company that offers AR as a marketing strategy or as a user / customer loyalty campaign is a company that focuses on innovation and creativity.</p><p>Customers often look for safe ways, AR is an experiment that the customer might like, because it is safe, and the customer because it is new and, especially in Italy, little seen and used by companies.</p><p>In the next articles of this little series about <a href="https://arvrjourney.com/">AR/VR</a>: <a href="https://medium.com/@miki.lombi/the-sorting-hat-experiment-webar-in-pure-js-c53b91863c66">The Sorting Hat Experiment in WebGL</a>!</p><h3>Don’t forget to give us your 👏 !</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/780/0*yX6T_VDVDq7kqnJU" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fupscri.be%2Fcc7833%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fupscri.be%2FARVR%3Ffbclid%3DIwAR3o3Cek44YsQ5uIM2rk9fWCGFnhDthkHbC095-H0CcmYt9FKGpa5UJ2dps&amp;image=http%3A%2F%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fcc7833%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/1e1f2ee7654748bb938735cbca6f0fd3/href">https://medium.com/media/1e1f2ee7654748bb938735cbca6f0fd3/href</a></iframe><figure><a href="https://www.facebook.com/groups/984060571735120/"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*2f7OqE2AJK1KSrhkmD9ZMw.png" /></a></figure><figure><a href="https://upscri.be/ARVR"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*v-PpfkSWHbvlWWamSVHHWg.png" /></a></figure><figure><a href="https://docs.google.com/forms/d/1YBHAY792wL3OslxTQRqcIbRICNeKdeYSiSr2HyVrptU/edit"><img alt="" src="https://cdn-images-1.medium.com/max/255/1*Wt2auqISiEAOZxJ-I7brDQ.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f73bed865bb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ar-vr-journey/the-augmented-reality-a-brief-explanation-6f73bed865bb">The Augmented Reality — A brief explanation</a> was originally published in <a href="https://medium.com/ar-vr-journey">AR/VR Journey: Augmented &amp; Virtual Reality Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>