<?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[NAVARA - Medium]]></title>
        <description><![CDATA[Business technology with impact. - Medium]]></description>
        <link>https://medium.com/navara?source=rss----2283751c3060---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>NAVARA - Medium</title>
            <link>https://medium.com/navara?source=rss----2283751c3060---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 00:25:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/navara" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Biome: The Faster Lint and Formatting Alternative to Prettier]]></title>
            <link>https://medium.com/navara/biome-the-faster-lint-and-formatting-alternative-to-prettier-12fcf8b122b9?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/12fcf8b122b9</guid>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Rebecca Davidsson]]></dc:creator>
            <pubDate>Fri, 12 Jan 2024 13:07:08 GMT</pubDate>
            <atom:updated>2024-01-12T13:07:08.879Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9_Ec3RQdTce_0jk7zLZeYw.png" /></figure><h3>Biome: The Next Generation of Code Formatting and Linting</h3><h4>Prettier has been widely used by developers to format code. Recently, a much faster alternative was released: Biome.</h4><p>For years, Prettier has been widely used by developers to format code for JavaScript, TypeScript, JSON and many more. However, there was one drawback: performance. Biome, a new open-source toolchain for web development, tackles this problem by combining a faster formatter and linter.</p><p>Built on Rust, it is renowned for its speed and efficiency and has <strong>many performance benefits</strong> compared to Prettier. Recently, Biome won the <a href="https://biomejs.dev/blog/biome-wins-prettier-challenge/">Prettier challenge</a> that was launched by one of Prettier’s creators. The challenge was to write a prettier-compliant pretty printer in Rust.</p><p>Biome is significantly faster, producing more consistent and predictable formatting. Its error messages are also more informative and helpful, making it easier to identify and rectify formatting issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ej4zmVx7GwefVHXBw_i4xg.png" /></figure><h4><strong>A linter and formatter in one tool</strong></h4><p>Biome can be used to perform a variety of tasks, including analyzing, formatting, and linting your code. By using the check command you can run both the lint and format option.</p><pre>npx @biomejs/biome check --apply &lt;files&gt;</pre><p>I’ve found Biome’s linter to be more proactive than Prettier’s, catching potential bugs and errors early on, preventing them from becoming major issues. The linter immediately finds several potential issues, including unused variables and misplaced parentheses. These issues are resolved quickly and easily, leaving code cleaner and more organized.</p><h4>Key features of Biome</h4><ul><li><strong>Speed and Efficiency:</strong> Built on the Rust programming language, Biome boasts exceptional performance.</li><li><strong>Simplicity</strong>: Biome eliminates the need for complex configuration, allowing developers to start using it right away without extensive setup. Yet, it provides extensive options for fine-tuning its behavior to suit individual preferences.</li><li><strong>Scalability:</strong> Biome is designed to handle projects of any size, ensuring that its performance remains consistent regardless of the code base’s complexity.</li><li><strong>IDE Integration</strong>: Biome integrates seamlessly with popular IDEs and code editors, such as VS Code and IntelliJ IDEA. It also offers extensibility through plugins and hooks.</li><li><strong>Error Reporting and Diagnostics</strong>: Biome provides detailed and contextual error messages that guide developers toward identifying and resolving issues quickly.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*DF9k4pigyJB3gTYN1eR4zA.png" /><figcaption>Biome provides detailed error messages to identify problems.</figcaption></figure><h4><strong>Accessibility</strong></h4><p>Checking for accessibility in HTML is becoming more and more important for web development. Biome does a great job at identifying accessibility issues. It provides easy-to-understand error messages and offers potential solutions for them. I want to bring up two examples.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*swi5AEZlK-Jo_nOR-is_YA.png" /><figcaption>Biome shows what should be fixed in the div.</figcaption></figure><p>In the example above, Biome points out what exactly should be fixed in the incorrect usage of role=&quot;slider&quot;.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_ccTa-nYWD-gett7B8RwmA.png" /></figure><p>For the example above, Biome gives solutions for a fix. This makes it easier to identify and fix issues during development.</p><h4><strong>Benchmarks of Biome vs Prettier</strong></h4><p>Biome has made <a href="https://github.com/biomejs/biome/blob/main/benchmark/README.md">a repository</a> dedicated to running benchmarks that compare it to Prettier and parallel-prettier. The benchmarks involve formatting a collection of JavaScript and TypeScript files of varying sizes and complexities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XIkR16oOPCGGotiAR7dtTA.png" /><figcaption>Formatting and linting <a href="https://github.com/biomejs/biome/blob/main/benchmark/README.md">speed results </a>of different tools compared to Biome</figcaption></figure><p>The benchmark <a href="https://github.com/biomejs/biome/blob/main/benchmark/README.md">results</a> consistently show that Biome outperforms Prettier in both formatting and linting. Biome is significantly faster than Prettier and dprint for formatting and faster than ESLint for linting.</p><p><em>Good to note here: the benchmark uses </em><em>— max-diagnostics=0 when running Biome, which means that Biome only prints the diagnostic count, whereas ESLint prints a line for each lint error.</em></p><h4>Should you switch to Biome right now?</h4><p>While Biome offers promising features, it is currently in its early stages of development and there are <strong>still some limitations</strong>.</p><p><strong>Biome has less type-checked lint rules</strong></p><p>The incredible speed comes at a price: Rust-based linters currently lack the comprehensiveness of type-checked lint rules provided by ESLint. This means that while they can identify syntax errors and common style issues, they may miss problems that rely on type information.</p><p>Rust-based linters are still missing a piece of the puzzle when it comes to<strong> type checking</strong>, a feature that ESLint + typescript-eslint does have. On the other hand, as of January 2024, Biome does include <a href="https://github.com/biomejs/biome/discussions/3#typescript-eslint">64 typescript-eslint rules</a>, but these rules don’t cover all the<a href="https://typescript-eslint.io/rules/"> typescript-eslint rules</a>. For example, in contrast to typescript-eslint:</p><ul><li>Biome lacks the prefer-readonly rule, which enforces marking private members as readonly if they are never modified outside of the constructor.</li><li>It also lacks the explicit-function-return-type rule, which requires explicit return type declarations for all functions, even if they always return the same type.</li></ul><p>And there are some other examples of rules that Biome does not have. However, Biome is still being developed and more rules are being added.</p><p>So, which approach should you choose? If performance is critical and you’re willing to make some small trade-offs in typescript-eslint rules, then Biome could be a good option. If you need complete type-checking in your project, stay with Prettier and ESlint and wait until Biome is developed further.</p><p><strong>Nx support</strong></p><p>While there is no official announcement regarding nx support for Biome, the new toolchain for web projects, it’s possible that such integration could be developed in the future…</p><p><strong>Prettier is also becoming faster</strong></p><p>While Biome is a solid option, Prettier is also likely to get a speed boost in the future. This will be achieved by optimizing its parsing engine, AST representations, whitespace handling, and leveraging hardware acceleration. So, if you’re happy with Prettier, you’re probably also good to stick with it.</p><h4>Conclusion</h4><p>As Biome continues to evolve, I believe it has the potential to optimize the way we develop web applications. Its focus on performance, compatibility, and ease of use makes it a compelling choice for developers. In the future, I see that Biome has the potential to become the standard toolchain for web development.</p><p>If you want to set up Biome in your project, it’s done in a few seconds. Go to <a href="https://biomejs.dev/guides/getting-started/">biomejs.dev</a> for more details about setting up Biome. There is also a <a href="https://biomejs.dev/playground/">playground</a> to get to know the formatter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=12fcf8b122b9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/biome-the-faster-lint-and-formatting-alternative-to-prettier-12fcf8b122b9">Biome: The Faster Lint and Formatting Alternative to Prettier</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Key takeaways from Storybook’s first meetup in Paris]]></title>
            <link>https://medium.com/navara/key-takeaways-from-storybooks-first-meetup-in-paris-5d1ffe816880?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d1ffe816880</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[storybook]]></category>
            <category><![CDATA[chromatics]]></category>
            <category><![CDATA[automation-testing]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Diego Consen]]></dc:creator>
            <pubDate>Wed, 15 Nov 2023 08:11:36 GMT</pubDate>
            <atom:updated>2023-11-15T08:18:04.605Z</atom:updated>
            <content:encoded><![CDATA[<h3>Key Takeaways From Storybook’s First Meetup in Paris</h3><h4><strong>Automation + Tools for design system engineers.</strong></h4><figure><img alt="View from the top floor of the Eiffel Tower, Paris" src="https://cdn-images-1.medium.com/max/1024/1*QfwabpxX22QcXuCMKTP9-A.png" /><figcaption>Taking in the breathtaking view over Paris after the event.</figcaption></figure><p>Last Tuesday, November 7th, 2023, marked the first Paris Storybook meetup. I was fortunate enough to be part of this insightful event with like-minded professionals.</p><p>To be quite honest, when first arriving at the venue I was worried that I had shown up at the wrong place. But don’t let yourself be fooled by appearance. When I spotted the big neon sign behind the front desk with some strong language suggesting that reusing products is the way to go, I immediately knew I had the correct spot. We got there a bit early so not a lot of people had shown, but it started to get more and more crowded as the first session was about to start.</p><p>If you couldn’t make it to Paris, or the event livestream even, let me make it up to you by sharing some of the key takeaways from this enervating event.</p><h4><strong>Storybook (+ Chromatic)</strong></h4><p>The night was kicked off by one of Storybook’s core maintainers ‘Norbert de Langen’, taking us through the basics of Storybook and how you can leverage its strengths even further using Chromatic. Developing frontends and design systems can be quite challenging because the future is always uncertain. As Norbert rightfully said: “Abstraction is hard, but testing UI is REALLY hard.”</p><p>Storybook is all about developing UI components in isolation, removing the confusing contexts in which the component may be used. Most developers are familiar with unit-testing their code, and this is also certainly possible for testing your UI components. However, these tests often rely on virtual DOMs set by NodeJS and JSDOM. Storybook enables you to perform these unit tests in different browser contexts while also providing you with a visual representation of your component and any unexpected differences that were found compared to previous versions of your UI element.</p><p>The tests that you write for Storybook are run in ‘Play functions’ after the component has rendered. The developer also has access to a step-by-step trace of the test for optimal debugging, seeing the exact interaction that caused your new element to fail. There is also a test runner available for NodeJS, powered by Playwright, that can run Storybook’s play functions in parallel and cross-browser. If that wasn’t enough you aren’t even limited to running the tests on your local storybook project, but also against deployed Storybook projects.</p><p>By incorporating Chromatic into this equation you can set up automated workflows as part of your pull request cycles that allow for visual regression testing as well. A static build of your Storybook project is published to Chromatic and, like you are used to with GIT pull requests, a review is prepared for the stakeholders that you’ve set up for your specific use cases. Currently, a plugin is in Beta to run these visual tests right from within your Storybook dashboard.</p><h4><strong>Design System Compliance</strong></h4><p>Next up was Victor Michaud, Design System Manager at Doctolib, sharing with us how he and his team deal with the challenge of compliance with their design systems.</p><p>To tackle this, the team has built its own Figma-plugin to identify all compliant and non-compliant layers in the project. Using these numbers they can estimate a percentage of compliance using a proprietary formula. Doctolib has also developed an in-house extension for Google Chrome that highlights (non-)compliant elements in a live preview. These tools help them to identify any design system debt that they may be facing, such as missing components. The goal is not to reach 100% compliance as this would inhibit creativity. Striving for 75% or 80% design system compliance would be just as good, if not better.</p><h4><strong>Design Tokens</strong></h4><p>To close off the night we had Steve Dodier-Lazaro from our host BackMarket to share their experience with design tokens. Particularly how their team has struggled with changing design tokens throughout a complex codebase.</p><p>Design tokens describe general properties that are used throughout a design system. For example, color, spacing, and fonts can be captured in design tokens so that they may be re-used throughout your product. Contrary to popular belief Steve states that the use of design tokens does NOT make future brand changes easy as their team has experienced firsthand how much trouble it is. What it does however provide your team with is a formalized style declaration and uniform CSS.</p><p>When design tokens change, often the code has to be migrated, and most of the time this is done manually by the developers. This is where they have found a way to optimize this process. Migrating design tokens usually consists of a combination of <em>value change</em>, <em>addition, removal, </em>and <em>replacement</em>. To tackle these migrations the team has used codemodding to replace patterns in their code based on grammar. This even allowed for previously hardcoded values to be replaced with newly defined design tokens.</p><p>All in all, I look back on an interesting event with professionals who share a passion for front-end development. Many thanks to all the speakers, organizers, and everyone I have had a chance to speak to about our mutual passion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d1ffe816880" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/key-takeaways-from-storybooks-first-meetup-in-paris-5d1ffe816880">Key takeaways from Storybook’s first meetup in Paris</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting Started with Terraform on Microsoft Azure]]></title>
            <link>https://medium.com/navara/with-terraform-getting-started-on-microsoft-azure-69f6e0b608ec?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/69f6e0b608ec</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <dc:creator><![CDATA[Erik Burger]]></dc:creator>
            <pubDate>Sun, 01 Oct 2023 14:43:16 GMT</pubDate>
            <atom:updated>2023-10-04T18:02:16.986Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*vIhABkPZW-mXIR761x_F5w.png" /></figure><h4>Safely and consistently manage your Azure infrastructure using Infrastructure as Code.</h4><p>In this article, you’ll learn how to install and configure Terraform to connect to Microsoft Azure. You’ll then create your first resource using Terraform.</p><h4>What is Infrastructure as Code?</h4><p>Infrastructure as Code (IaC) is a method of managing and providing IT infrastructure using machine-readable scripts or code rather than manual configuration. It enables DevOps teams to use code to describe and automate the setup and maintenance of infrastructure resources such as servers, networks, and databases.</p><p>IaC has various benefits, including higher consistency, repeatability, and scalability of infrastructure deployments, faster and more reliable provisioning. It also allows for the use of version control and documentation of infrastructure configurations, making it easier to trace changes and rollbacks. It aligns perfectly with core DevOps principles of automation, collaboration, and continuous integration and delivery (CI/CD).</p><h4>What is Terraform?</h4><p>A lot of different tools exist to enable a team to use IaC, like <a href="https://www.ansible.com/">Ansible</a> and <a href="https://aws.amazon.com/cloudformation/">AWS Cloudformation</a>, and which tool to use depends a lot on the use case, as well as on the availability of skills within your team.</p><p><a href="https://www.terraform.io/">Terraform</a>, by <a href="https://www.hashicorp.com/">HashiCorp</a>, is one of the most well-known IaC tools. One of its key benefits over other tools is its multi-cloud support, allowing users to manage infrastructure consistently across various cloud platforms, including <a href="https://aws.amazon.com/">AWS</a>, <a href="https://azure.microsoft.com/">Azure</a>, <a href="https://cloud.google.com/">Google Cloud</a>, and more. Terraform’s state management ensures efficient and safe updates to infrastructure, and its plan-driven approach provides a clear preview of changes before they are applied, enhancing predictability and reducing the risk of errors.</p><h3>Installing Terraform</h3><p>The easiest way to install Terraform on OS X is using <a href="https://brew.sh/">Homebrew</a>. Inside a Terminal, run:</p><pre>brew tap hashicorp/tap</pre><p>This installs the HashiCorp tap, which contains all their packages.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/898/1*jAsTK01FMV6ISJpsCNzKNQ.png" /><figcaption>Installing HashiCorp tap.</figcaption></figure><p>Then, to install Terraform, run:</p><pre>brew install hashicorp/tap/terraform</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/897/1*pWSiCba7SwXOVBT-Mo9OWA.png" /><figcaption>Installing Terraform.</figcaption></figure><p>You can run terraform -version to check whether Terraform was installed successfully.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MP6nhnXOIWL2UQi_2_EZ_g.png" /><figcaption>Terraform version.</figcaption></figure><h3>Connecting to Azure</h3><p>In order to use Terraform to create resources on Microsoft Azure, you’ll need to have an Azure subscription. If you don’t have one, you can <a href="https://azure.microsoft.com/en-us/free/">create one here</a>.</p><p>You also need the Azure CLI installed. Using Homebrew again:</p><pre>brew update &amp;&amp; brew install azure-cli</pre><h4>Log in to Azure</h4><p>In your terminal, type az login to log in to your Azure subscription. This will open a browser window, which you can close again after you successfully authenticate. The output will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ClTM5BZ3QtKuuLYs3NIKFA.png" /><figcaption>Output from az login.</figcaption></figure><p>Then set the active subscription using the id field from the above output:</p><pre>az account set -s &quot;&lt;id&gt;&quot;</pre><h4>Create a Service Principal</h4><p>Terraform needs a Service Principal to be able to go into your Azure subscription and make changes. The Service Principal needs the Contributor role in order to do this:</p><pre>az ad sp create-for-rbac --role=&quot;Contributor&quot; --scopes=&quot;/subscriptions/&lt;id&gt;&quot;</pre><p>Again, replace &lt;id&gt; with the active subscription id. Your output will look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f5ZG6gSkEBsV0kYpgfxfUw.png" /><figcaption>Creating a Service Principal.</figcaption></figure><h4>Setup environment variables</h4><p>Terraform needs a set of environment variables to connect to your Azure subscription. Replace the values between &lt; &gt; with the values from the outputs above.</p><pre>export ARM_CLIENT_ID=&quot;&lt;appId&gt;&quot;<br>export ARM_CLIENT_SECRET=&quot;&lt;password&gt;&quot;<br>export ARM_SUBSCRIPTION_ID=&quot;&lt;id&gt;&quot;<br>export ARM_TENANT_ID=&quot;&lt;tenant&gt;&quot;</pre><p>Now that you have Terraform installed and connected to your Azure subscription, you can start creating your first resource.</p><h3>Creating a Resource Group</h3><p>In Azure, Resource Groups are used to, well, group resources. Any resource has to belong to a Resource Group, and they’re a very convenient way to organize larger numbers of resources that belong together, such as the resources in your test, acceptance, and production environments.</p><p>Or, in this case, to the <a href="https://erikbrgr.medium.com/list/with-terraform-5ed5b2167056"><strong>With Terraform</strong></a> series.</p><p>Create a folder with-terraform.</p><p>Inside the folder, create a new file called main.tf. tf is the file extension for Terraform files.</p><h4>Configure the Azure provider</h4><p>To start, we need to configure Terraform to use the Azure provider. A <a href="https://developer.hashicorp.com/terraform/language/providers/configuration"><em>provider</em></a> determines which cloud infrastructure you can manage using Terraform.</p><p>Copy and paste the following code into your main.tf file.</p><pre># Configure the Azure provider<br>terraform {<br>  required_providers {<br>    azurerm = {<br>      source  = &quot;hashicorp/azurerm&quot;<br>      version = &quot;~&gt; 3.75.0&quot;<br>    }<br>  }<br><br>  required_version = &quot;&gt;= 1.5.7&quot;<br>}<br><br>provider &quot;azurerm&quot; {<br>  features {}<br>}</pre><p>This configures the required_provider to be Azure, and to use version 3.75.0. The ~&gt; sign allows for patch updates, but nothing else. We also specify the required_version for Terraform to be at least 1.5.7.</p><p>Now, run terraform init in your terminal top initialize Terraform with your configuration.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*cJ166cSFeSAT6CiVAm0iAQ.png" /><figcaption>Initializing Terraform.</figcaption></figure><p>You can see that it automatically installs the correct version of the Azure provider. It also created a lock file to make sure the configuration doesn’t change by accident.</p><h4>Adding a Resource Group</h4><p>Now, let’s add a Resource Group. Add the following code at the bottom of your main.tf file.</p><pre># Create a resource group<br>resource &quot;azurerm_resource_group&quot; &quot;rg-wtf&quot; {<br>  name     = &quot;rg-with-terraform&quot;<br>  location = &quot;West Europe&quot;<br>}</pre><p>This instructs Terraform that a resource group called rg-with-terraform should be created, in the West Europe region. To reference the resource group in our Terraform configuration, we’re specifying rg-wtf as the name of this particular resource group.</p><blockquote><em>The </em><em>location property supports specifying the Azure region </em><a href="https://github.com/claranet/terraform-azurerm-regions/blob/master/REGIONS.md"><em>in several formats</em></a><em>.</em></blockquote><h4>Creating the Resource Group</h4><p>To create the Resource Group in Azure, you use two separate commands.</p><p>First, use terraform plan to preview what changes will be made to your Azure subscription.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*RYrOsVmxUYV3NTCDCSKLaw.png" /><figcaption>Terraform plan, or “what does this button do?”</figcaption></figure><p>The output tells us that one resource will be created, which is our rg-with-terraform Resource Group. Nothing’s going to be changed or destroyed. It&#39;s looking good so far.</p><blockquote><em>While, technically, running </em><em>terraform plan is optional, it is always a good idea to check before you do something you’ll regret. As Robin Hobb said in Assassin’s Apprentice: “Don’t do what you can’t undo, until you’ve considered what you can’t do once you’ve done it.” I think this quote counts double, when Terraform is involved.</em></blockquote><p>Then, run terraform apply -auto-approve to apply your changes to your Azure subscription (it’s safe to add the auto-approve flag, since you ran terraform plan like, a few seconds ago).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*XpRHuGXjs4KB3ObDZi1N4A.png" /><figcaption>Terraform apply, or “<em>terraformus azurus!</em>”</figcaption></figure><blockquote><em>This really is the coolest part of this entire tutorial 😎</em></blockquote><p>If you check your Azure subscription, you can see that the Resource Group was successfully created.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*WOR8kgHAGoJi4SgUctxbAg.png" /><figcaption>Successfully created Resource Group in the Azure portal.</figcaption></figure><h3>Cleaning up</h3><p>At one point, you should clean up any resources you created using Terraform. terraform destroy destroys all the resources you defined in your configuration, leaving your Azure subscription nice and clean.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/847/1*Z_N5I3J5z2O4SZfV2nK0Pg.png" /><figcaption>Terraform destroy, or “here comes the BOOM!”</figcaption></figure><h3>Conclusion</h3><p>In this article, you learned how to use Terraform to create a Resource Group in Microsoft Azure.</p><p>Terraform is an incredibly powerful tool to have in your arsenal, if you are serious about Infrastructure as Code in particular, and DevOps in general.</p><p>Being able to manage your infrastructure safely and consistently (albeit not always <em>quickly</em> as your infrastructure grows), allows you and your team to respond quicker to changing business requirements, and to keep an edge on the competition.</p><h3>Quick reference of Terraform commands</h3><p>terraform init initializes the Terraform configuration, preparing the working directory for use.</p><p>terraform plan generates an execution plan, outlining the actions Terraform will take to achieve the desired state, aka what resources will be added, changed, and/or destroyed.</p><p>terraform apply applies the changes described in the execution plan. The auto-approve flag can be used to bypass interactive approval.</p><p>terraform destroy destroys all the resources defined in your Terraform configuration, cleaning up your infrastructure.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=69f6e0b608ec" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/with-terraform-getting-started-on-microsoft-azure-69f6e0b608ec">Getting Started with Terraform on Microsoft Azure</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chrome DevTools Updates You Can’t Miss in 2023]]></title>
            <link>https://medium.com/navara/chrome-devtools-updates-you-cant-miss-in-2023-6acccff5960?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/6acccff5960</guid>
            <category><![CDATA[css]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[chrome]]></category>
            <category><![CDATA[frontend]]></category>
            <dc:creator><![CDATA[Rebecca Davidsson]]></dc:creator>
            <pubDate>Wed, 27 Sep 2023 08:28:42 GMT</pubDate>
            <atom:updated>2023-09-27T08:28:42.912Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*A5FEwEOms5Bo0q_q" /><figcaption>Photo by <a href="https://unsplash.com/@growtika?utm_source=medium&amp;utm_medium=referral">Growtika</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>In the Chrome 116–117 release, a number of new features are introduced that developers will love, such as HTTP mocking.</h4><p>A number of new features are introduced in Chrome 116–117 that will definitely improve the developer experience in Chrome, such as <strong>HTTP mocking</strong> directly in DevTools.</p><h3>HTTP mocking in Chrome 🔥</h3><p>HTTP mocking is a technique that allows you to simulate HTTP responses. This can be useful for a variety of purposes, such as prototyping, debugging, and testing.</p><p>To use HTTP mocking, simply open the DevTools network panel and right-click on the request that you want to mock. Then, select “Override content” from the context menu:</p><figure><img alt="Dropdown with the override http request option in Chrome Devtools" src="https://cdn-images-1.medium.com/max/1024/1*_xJ02oGopIjErvdJM5uHGg.png" /></figure><p>This will open a dialog box where you can enter the mock response. You can enter JSON, XML, HTML, or any other type of data that you want the server to return.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X-ZXbZg4AOzcKPWxtluhag.png" /></figure><p>Don’t forget to click the “Save” button once you have entered the mock response. Chrome will then use this mock response whenever the request is made. You see a purple circle in your Network panel whenever a resource is overwritten.</p><ul><li>✅ <strong>No more waiting for the backend API to be deployed</strong>: HTTP mocking can be used to prototype new web apps without having to wait for the backend API to be developed. You can now simulate the API responses and test your app locally!</li><li>✅ <strong>(Performance) testing</strong>: it can be used to test the performance of your web app by simulating different types of network conditions. For example, you can use HTTP mocking to simulate a slow network connection or a packet loss. in addition, you can use it to test behavior at a large amount of traffic or when a website is under attack.</li></ul><h3>Highlighting more updates</h3><ul><li><strong>CSS animations editor </strong>and other CSS updates: You can now easily preview animations and edit animation timelines.</li><li><strong>Debug priority fetches</strong>: You can now debug priority fetches by showing the fetch priority for each request in the DevTools network panel.</li><li><strong>Prefetch pages</strong>: A new feature called “prefetch pages” allows you to prefetch pages that are likely to be visited next. This can improve the performance of web applications by reducing the time it takes to load pages.</li><li><strong>Array grouping: </strong>You can group the elements of an array based on the values returned by a callback function.</li><li><strong>Debug missing CSS styles</strong>: Debugging missing CSS styles is now easier by providing a new panel in DevTools that shows all of the missing styles for a given page.</li></ul><p>In addition, there are multiple other updates such as better syntax highlighting for source code and the option to hide annoying Chrome extension logs. Next to the http mocking feature, I’m enthusiastic about some of the CSS animation updates, which I will cover in the next paragraph.</p><h3>CSS animation updates</h3><p>Another notable new feature is the ability to <strong>edit animation timelines</strong>. This allows you to fine-tune the timing of your animation and to create complex animations with multiple keyframes.</p><figure><img alt="CSS animation timeline editor in Chrome Devtools" src="https://cdn-images-1.medium.com/max/600/1*D6xzyvx72vkYHkfQf5I_eA.gif" /></figure><h4>CSS transition animation on exit</h4><p>Before I dive into this new feature, I will start with an exit animation example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*hR6ymrpRlo9o_aMtSEaEFQ.gif" /><figcaption>Example of an<a href="https://developer.chrome.com/blog/entry-exit-animations/"> exit animation</a></figcaption></figure><p>It is not unlikely that you would want to remove a DOM node (with a timeout) after an exit animation is finished. Now you have the ability to animate display and content-visibility on a keyframe timeline!</p><h4>Animate entry animations with a new CSS rule</h4><p>In the example above, a new feature @starting-style is used to animate the entry effect from display: none and was then added into the top-layer. Chrome then uses this to look up a style on an element before it is open, called the ‘before-open’ state. We then have three states: before-open, is-open and exiting state:</p><pre>/* Before-open state*/<br>@starting-style {<br>  .item {<br>    opacity: 0;<br>    transform: scale(0);<br>  }<br>}<br><br>/* Is-open state */<br>.item {<br>  display: grid;<br>  overflow: hidden;<br>  opacity: 1;<br>  transform: scale(1);<br>  transition: opacity 0.5s, transform 0.5s, display 0.5s allow-discrete;<br>}<br><br>/* Exit state */<br>.is-deleting {<br>  opacity: 0;<br>  display: none;<br>  transform: scale(0.5) skewX(50deg) translateX(-25vw);<br>}</pre><p>Notice the transition-behavior property with the allow-discrete keyword in this example, which is used to to enable the transition of display.</p><p><em>Read more about new CSS features brought to Chrome 116–117 such as animating the overlay property </em><a href="https://developer.chrome.com/blog/entry-exit-animations/"><em>here</em></a><em>.</em></p><h3>Network panel improvements</h3><ul><li>See the <strong>changes in fetch priority</strong> for network events. This can be helpful for debugging performance issues and understanding how fetch priorities affect network requests.</li><li><strong>Prefetch pages</strong>: you can prefetch pages that are likely to be visited next. This can improve the performance of web applications by reducing the time it takes to load pages.</li><li><strong>Hide annoying Chrome extension warnings </strong>in your console. This can make the Network panel less cluttered and easier to use. A way more peaceful console.</li><li><strong>Readable HTTP status codes</strong>. DevTools now displays human-readable descriptions for HTTP status codes, making it easier to understand what they mean.</li></ul><h3>Array grouping with JS</h3><p>In older versions of Chrome, you had to use a for-loop to iterate over the array and group the elements based on the values returned by a callback function, which was just too much work. <strong>Before:</strong></p><pre>const products = [<br>  { name: &quot;Banana&quot;, category: &quot;Fruit&quot; },<br>  { name: &quot;Orange&quot;, category: &quot;Fruit&quot; },<br>  { name: &quot;Peanut butter&quot;, category: &quot;Best products ever&quot; },<br>];</pre><pre>// Grouping products by category<br>const groupedProducts = {};<br>for (const product of products) {<br>  const category = product.category;<br>  if (!groupedProducts[category]) {<br>    groupedProducts[category] = [];<br>  }<br>  groupedProducts[category].push(product);<br>}</pre><p><strong>After: </strong>Now we can replace this by using groupBy() in one line:</p><pre>const groupedProducts = Object.groupBy(product, ({ category }) =&gt; category);</pre><h3>Conclusion</h3><p>The new features in Chrome 116 and 117 make the browser even more powerful. HTTP mocking, in particular, is a powerful tool that can save developers and testers a significant amount of time and effort. You can simply mock the responses of your backend API to simulate different scenarios directly in the browser. Some other great updates in CSS animations are added, as well as great updates in the Network tab. I’m already excited for some of the next updates in version 118.</p><p><em>Resources: </em><a href="https://developer.chrome.com/blog/new-in-devtools-116/"><em>New in DevTools 116</em></a><em> , </em><a href="https://developer.chrome.com/blog/new-in-devtools-117/"><em>New in DevTools 117</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6acccff5960" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/chrome-devtools-updates-you-cant-miss-in-2023-6acccff5960">Chrome DevTools Updates You Can’t Miss in 2023</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Writer’s Guidelines]]></title>
            <link>https://medium.com/navara/writers-guidelines-dacc29ba2ec6?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/dacc29ba2ec6</guid>
            <category><![CDATA[navara]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Erik Burger]]></dc:creator>
            <pubDate>Tue, 19 Sep 2023 07:02:33 GMT</pubDate>
            <atom:updated>2024-01-12T12:20:01.645Z</atom:updated>
            <content:encoded><![CDATA[<h4>Want to write for us? Here’s how.</h4><figure><img alt="Photo of a notebook in front of a laptop, on a desk." src="https://cdn-images-1.medium.com/max/1024/0*MzuKfkOTl64PnVyL" /><figcaption>Photo by <a href="https://unsplash.com/@nickmorrison?utm_source=medium&amp;utm_medium=referral">Nick Morrison</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><em>Note: We currently only accept Navarians to write for the Navara publication.</em></p><p>First of all, awesome! We’re very happy to welcome you as a writer, no matter your experience in writing or publishing. We’re looking forward to helping you get started, keep going, and put yourself out there as an expert in the field you’re passionate about.</p><p>Let’s get started!</p><h3>Applying as a writer</h3><p>To apply as a writer, you’ll need your Medium username. You can find your Medium username by clicking on your profile picture, here:</p><figure><img alt="The Medium profile menu with username highlighted." src="https://cdn-images-1.medium.com/max/245/1*RoR5o77XhDI4UVfY6F8NnA.png" /><figcaption>Where to find your Medium username.</figcaption></figure><p>Then, you have 2 options:</p><ol><li>Leave your Medium username in a comment on this article.</li><li>Leave us a message (including your username) on our Slack channel: #community-writing-technical-blogs.</li></ol><p>One of our editors will then add you as a writer, and contact you about submitting your first article.</p><h3>Communication</h3><p>All communication concerning writing for the publication takes place in our private Slack channel. You can find us at #community-writing-technical-blogs.</p><h3>Submitting your article</h3><p>After you have made sure your article adheres to our guidelines below, you can submit your article. <a href="https://help.medium.com/hc/en-us/articles/213904978">Here’s how that works</a>.</p><h3>Topics</h3><p>We don’t limit the topics you can write about, as long as they are (remotely) tech-related. That said, here’s a few ideas:</p><ul><li>Tutorial-style articles on topics you have encountered in your daily work or life.</li><li>Deep dives into specific technology or practices.</li><li>Experiences you’ve had, and the learnings you gained from them.</li></ul><p>Opinion pieces are very welcome, but note that we will look at those through the lens of Navara’s own opinions, and how they may affect our brand. We welcome discussion, but we’re careful about how to have those discussions in public.</p><h3>Guidelines</h3><p>We try to maintain a high standard for any articles submitted to our publication. As such, we have a set of guidelines we request all writers to adhere to.</p><h4>Basics</h4><ul><li>Articles should be written in English. However, we are more than willing to help you translate an article written in Dutch. Just let us know.</li><li>Please make sure your Medium account is complete, i.e. it should have your name, a short bio, and a profile picture. Articles will be published under your name, so this is beneficial to you, as well.</li><li>Make sure you are using all 5 topic slots you have available (either through the <em>Change topics</em> menu or on the submission page). This makes your article easier to find. If you have a slot left, just add Navara as a topic.</li></ul><figure><img alt="Dialog to submit to the NAVARA publication." src="https://cdn-images-1.medium.com/max/462/1*FhqibgJQNkQRFOTsLdXC2g.png" /><figcaption>Submitting to the NAVARA publication.</figcaption></figure><h4>Headlines and Headings</h4><ul><li>Your article should have a title and a subtitle. Also, please make sure the values in the <em>Change display title / subtitle</em> menu are the same.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/404/1*V7esara8gcts-0NCmSqxkg.png" /></figure><ul><li>While not an end-all, be-all solution, using a <a href="https://www.monsterinsights.com/headline-analyzer/">Headline Analyzer</a> can help you craft a better headline. One tip; when in doubt, ignore the advice, and go with what you think is best. It’s your article, after all.</li><li>We follow AP style for title capitalization. This means all major words are capitalized, while minor words are lowercase. <a href="https://titlecaseconverter.com/">Title Case Converter</a> is a helpful tool, if you’re not sure.</li><li>In your subtitle, use sentence-case; this means capitalizing it like you would any other sentence.</li></ul><h4>Images and Code Blocks</h4><ul><li>Your article should have a cover image (also known as a Feature Image) <em>that you have the rights to use</em>. Either your own, or an image licensed under Creative Commons. We recommend sites like <a href="http://unsplash.com/">Unsplash</a> for finding images to use. You are required to credit any image used properly. See the top of this post for an example.<br>Note that sometimes, an image will look great above an article, but will look, let’s say, less great in the story preview (which shows a square version of your image). Fortunately, you can do a lot to improve this. Reading <a href="https://medium.com/geekculture/how-featured-images-work-on-medium-how-to-set-the-focal-point-3bcba35755dc">this</a> article, for example.</li><li>Images should have an <em>alt text</em>, and a caption. You can access the alt text by clicking on your image:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/717/1*lhuq5Qx8iREFW0ZzApRHig.png" /></figure><ul><li>If you use code snippets, use either <a href="https://blog.medium.com/code-blocks-with-syntax-highlighting-53343df53c4f">Medium code blocks</a> or <a href="https://erikbrgr.medium.com/using-multi-file-github-gists-in-medium-f4e40bb9e283">GitHub Gists</a>. For multiple code snippets, we suggest multi-file Gists, as illustrated in the article.</li></ul><h4>Spelling and Formatting</h4><p>Please (pretty please?), use a tool like <a href="https://www.grammarly.com/">Grammarly</a> to look for spelling errors, grammatical inconsistencies, and whatever else Grammarly helps you find (it’s a lot!). This saves our editors a lot of time and allows us to focus on the content of your article instead of fixing spelling errors.</p><ul><li>The <a href="https://chrome.google.com/webstore/detail/grammarly-grammar-checker/kbfnbcaeplbcioakkpcpgfkobkghlhen">Grammarly extension for Google Chrome</a> works inside the Medium editor, which is really nice.</li><li>Whitespace is your friend. Use short paragraphs rather than long, and break them up using whitespace. The Medium editor mostly takes care of this for you.</li><li>While common in scientific writing, please do not use footnotes for links. Include them in the text. Scrolling back and forth to reach a link disrupts the reading experience, and will cause people to stop reading.</li><li>It is very helpful to your reader to include a <strong>Resources</strong> section at the end of your article, containing useful links mentioned in your article. For example, links to GitHub repos, Gists, JSFiddles, etc.</li></ul><h4>Voice</h4><ul><li>Remember that you are engaging with your reader when you write. Treat your writing as a dialogue, not as an information dump. It’s nice to thank the reader for spending part of their day with you. Obviously, this is not mandatory, if it’s not your style.</li></ul><h4>Plagiarism</h4><ul><li>Any quotes or otherwise quoted content must be properly credited. <em>We take plagiarism very seriously.</em> Any repeated attempt at trying to pass another’s work off as your own will result in you being removed from the publication.</li></ul><h4>About AI-Generated Content</h4><p>AI is a tool just like any other. Forbidding you to use AI would be like forbidding you to use Google. However, you are still the author of your article, and we expect you to have written it.</p><p>That’s it. We will be updating this article if and when the need arises, based on your feedback. So let us know if there’s anything we’re missing, or if you have any other questions and/or comments.</p><p>We hope to see your articles in our publication soon!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dacc29ba2ec6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/writers-guidelines-dacc29ba2ec6">Writer’s Guidelines</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How To Save Your Organisation With Documentation]]></title>
            <link>https://medium.com/navara/how-to-save-your-organisation-with-documentation-23459dfe2885?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/23459dfe2885</guid>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-lifecycle]]></category>
            <category><![CDATA[navara]]></category>
            <dc:creator><![CDATA[Axel Scheele]]></dc:creator>
            <pubDate>Tue, 12 Sep 2023 18:06:14 GMT</pubDate>
            <atom:updated>2023-09-12T18:06:14.398Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niSFIn02uqy6whFbolkZuQ.jpeg" /></figure><h4>Documents I write to improve decision-making in software development</h4><h3>Introduction</h3><p>A while back I worked at a company in a senior tech position. Before I even started, I knew things would be difficult. I had been told that the change to failure rate was very high. What I walked into, though, was really something I had never seen before.</p><p>From day one I got sucked into a crisis, doing hot fixes on the software and manual updates on production databases. Operations ran about 18 hours a day and IT was critical to do anything. Then the last 6 hours of the day were used to synchronise systems with partners so operations could resume the next day.</p><p>At any moment things would break due to changes and operational load. Everyone just did what was important in that moment. New features were never delivered on time and things seemed to take forever. It was panic, it was chaos, it was the way things worked.</p><h3>Post Mortem</h3><p>In a situation like that you can choose to do two things. One you look for something else, or two you improve the situation. And as I was allowed a little bit of influence I chose the second option. The first thing I did after a major incident was introduce post-mortem meetings.</p><p>Post mortem is a term out of <a href="https://sre.google/books/">Google SRE</a>. It is a meeting to discuss incidents in a <a href="https://response.pagerduty.com/after/post_mortem_template/">structured way</a> and to come up with lessons and improvements that can be implemented. A key part for me is that an incident report is made. It can be used to refer to the need to work on certain things and it is a way to keep lessons for the future.</p><p>Apart from having a cathartic effect on the people involved, post-mortem meetings also showed us what we wanted to improve. One of the things we wanted to do was to create test plans.</p><h3>Test Plan</h3><p>A test plan in its crudest form is nothing more than a checklist with things we want to be sure about before a release. For example, one check would be when releasing a new version of a mobile app, to be sure that it doesn’t crash when running on an actual mobile device. Apart from any functional criteria that we could think of a considerable value would be in our beta testers. Doing follow-up with them all is something on those lists too.</p><p>This seems all very obvious, but by keeping track of these things we were sure they happened. Furthermore, it offers a way to communicate very clearly with a manager about release planning. The overall effect is peace of mind. A value that is shared in another documentation format that I call protocols.</p><h3>Protocols</h3><p>In the introduction of this article, I mentioned making changes in production databases. This is something I rather not do. I one time deactivated all operations by running an incorrect update. However, the world is not perfect and badly written legacy code forces us to do things we rather not do. In fact, sometimes, it is part of the daily routine.</p><p>Things get really bad though when you have to do these things late at night, alone. The first time I had to do this I asked one of the veterans in the company to help me write out the steps of the work I had to do. Including rollbacks and verification.</p><p>So our protocols were born. For every manual action, we created one. It gave us certainty that we would cause less trouble and at the same time, they showed the holes in the applications. Things we needed to do and to fix became clear at this point, but to make plans we needed to discuss solutions.</p><h3>Architectural Designs &amp; Decision Records</h3><p>Solutions in IT are often very complex and abstract. Furthermore, many decisions are taken based on the context available at that time. Some people can do all this in their heads, especially when they are alone on a project. However, when you have to discuss solutions together changes are that you misunderstand each other. And if you have to remember decisions taken a long time ago it becomes hopeless.</p><p>Architectural designs are key in discussing solutions, looking at complex cases and coming to a common conclusion. I personally have a preference for <a href="https://c4model.com/">C4</a> and <a href="https://en.wikipedia.org/wiki/Sequence_diagram">sequence diagrams</a>. C4 is great for discussing high-over solutions with people and sequence diagrams show the intricate interaction between systems and where things get tricky. It doesn’t really matter, as long as you can understand each other.</p><p>However, choices in software are often made with more than just the designs. Often there is a context to take into consideration and that is where <a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/architectural-decision-records/appendix.html">decision records</a> shine. Though given that you will not immediately see a result from decision records, your future self and future colleagues will be very thankful. Having a reference to why solutions were chosen at a time is great input for refactors and new features.</p><p>I discussed documents to assist in making technical decisions here. Something that is straightforward if the requirements are clear. New features, though, seldomly have clear requirements.</p><h3>Feature Scopes</h3><p>New features were often a source of disappointment. Somewhere in an email sent a few weeks ago a very important request about the feature had been made. This email was overlooked and now the feature had to be redone. An email chain does not really work as a requirements list.</p><p>Therefore we introduced a new concept, to collaborate better on business requirements and the new software that we had to build. I call this document the feature scope. What we did first was create a rough description of what was needed. Then we added a few acceptance criteria and some scenarios that would probably describe how it would function. Then I discussed this document with the people who requested the feature. Once everything was happy we would freeze this scope and build it.</p><p>Of course, the first version was never what was wanted. But it was what was agreed upon and it was finished. Discussing changes was much more constructive and the document allowed us to agree on smaller increments and therefore quick feedback. A much more pleasant way of working for everyone and a much better result.</p><h3>Conclusion</h3><p>Did things go better at the company? The applications were still pretty horrible, but we had a bit more grip. Furthermore, collaboration and self-reliance improved among the engineers. The business was more involved.</p><p>Still, there was the elephant in the room, the software landscape that needed a proper refactor/ rebuild. I think, and that was also the goal of my efforts, that the documentation made clear what was needed. It could be discussed. A priority could be given based on evidence and rational choices could be made based on facts. Documentation in itself is not a solution for problems, but it helps in solving them.</p><p>For almost every step of the software development cycle, a form of documentation is proposed that could improve your work. Maybe you will not need all of them, but perhaps there is one that you would like to try.</p><h3>References</h3><ol><li><a href="https://sre.google/books/">Google SRE</a></li><li><a href="https://response.pagerduty.com/after/post_mortem_template/">Post mortem template</a></li><li><a href="https://c4model.com/">C4 diagrams</a></li><li><a href="https://en.wikipedia.org/wiki/Sequence_diagram">Sequence diagrams</a></li><li><a href="https://docs.aws.amazon.com/prescriptive-guidance/latest/architectural-decision-records/appendix.html">Decision records</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=23459dfe2885" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/how-to-save-your-organisation-with-documentation-23459dfe2885">How To Save Your Organisation With Documentation</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New & Upcoming CSS Features In 2023]]></title>
            <link>https://medium.com/navara/new-upcoming-css-features-2023-ba44d8a45993?source=rss----2283751c3060---4</link>
            <guid isPermaLink="false">https://medium.com/p/ba44d8a45993</guid>
            <category><![CDATA[frontend]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Rebecca Davidsson]]></dc:creator>
            <pubDate>Fri, 01 Sep 2023 09:15:08 GMT</pubDate>
            <atom:updated>2023-09-04T07:06:30.695Z</atom:updated>
            <content:encoded><![CDATA[<h4>Anchor positioning, new pseudo-classes, and more!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0JzKxar5ynDPS8qcNLpwHg.jpeg" /><figcaption>Anchor positioning in CSS</figcaption></figure><p>The <a href="https://www.w3.org/groups/wg/css/">CSS Working Group</a> is working on a number of exciting new features and CSS properties. These include features like anchor positioning, features for shapes, scroll snap, and new audio pseudo-classes.</p><h3>Anchor Positioning</h3><p>CSS Anchor Positioning is an experimental new CSS feature that allows you to position an element relative to another element on the page. This is done by using the anchor-position property. For example, the following code would position an element 10px to the left of the anchor element:</p><pre>.element {<br>  anchor-position: my-anchor left 10px;<br>}</pre><p>CSS Anchor Positioning is a powerful new feature that can be used to create a variety of interactive elements, such as tooltips, modals, and popovers. It makes tooltips even more dynamic. Here is a small example that shows how to anchor positioning to create a tooltip:</p><pre>&lt;div id=&quot;anchor&quot;&gt;This is the anchor element&lt;/div&gt;<br>&lt;div id=&quot;tooltip&quot;&gt;This is the tooltip&lt;/div&gt;</pre><pre>#tooltip {<br>    position: absolute;<br>    display: none;<br>    anchor-position: my-anchor top 10px;<br>  }<br>#anchor:hover #tooltip {<br>    display: block;<br>  }</pre><p>This code will create a tooltip that is positioned 10px above the anchor element when the anchor element is hovered over.</p><p>Another example from <a href="https://developer.chrome.com/blog/tether-elements-to-each-other-with-css-anchor-positioning/#focus-and-follow">developers.chrome.com</a> uses anchor positioning to track a visual indicator for the focused input fields. As you can see, the anchor can deal with multiple positions and layouts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*zK23S0cQhkbhhVNTHMnFlw.gif" /><figcaption><a href="https://developer.chrome.com/blog/tether-elements-to-each-other-with-css-anchor-positioning/#focus-and-follow">Focus and follow</a> using CSS anchor-position</figcaption></figure><p>In the future, we will be able to position an element relative to multiple anchor elements:</p><pre>.anchor1 {<br>  anchor-name: anchor1;<br>}<br>.anchor2 {<br>  anchor-name: anchor2;<br>}<br>.positioned {<br>  position: absolute;<br>  top: 0;<br>  left: 0;<br>  anchor: anchor1, anchor2;<br>}</pre><p>An example of multiple handlers for one element is the chart below, where the tooltips are anchored by combining it with the max and min values of the chart (source: <a href="https://developer.chrome.com/blog/tether-elements-to-each-other-with-css-anchor-positioning/#bar-chart-calc">developers.chrome.com</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*v7Da3Upqlr8Z9iSTc4nokA.gif" /><figcaption><a href="https://developer.chrome.com/blog/tether-elements-to-each-other-with-css-anchor-positioning/#bar-chart-calc">Tracking bar chart</a> values with CSS anchor position</figcaption></figure><p>Some other examples of how CSS anchor positioning can be used:</p><ul><li>Elements that follow the user as they scroll down the page.</li><li>Accordions that expand and collapse when the user clicks on a button.</li><li>Resize images based on multiple anchor-position s.</li><li>Modal dialogs that appear over the rest of the page.</li><li>Even more dynamic tooltips!</li></ul><p><em>Note that as of August 2023, anchor-positioning is still an experimental feature. You can test </em><a href="https://www.google.com/chrome/canary/"><em>Chrome Canary</em></a><em>!</em></p><h3>New features for shapes</h3><p>With CSS Shapes we don’t mean creating a div of 100 by 100 pixels and filling it read to create a square… CSS Shapes is a real thing that allows you to easily create complex shapes with CSS.</p><p>The shape-outside property has already been developed a while ago. This lets you create shapes that are relative to a specific location on the page. For example, you could create a circle that is centered on the top-left corner of the page:</p><pre>.circle {<br>  shape-outside: circle(50px at 10px 10px);<br>}</pre><p>But this is just the beginning. There are more shapes such as triangles, trapezoids, or polygons. You can make it as complex as you want.</p><pre>.triangle {<br>  shape-outside: triangle(50px, 0, 50px, 100px, 0, 100px);<br>}</pre><p>Other new features:</p><ul><li><strong>shape-inside</strong> which can be used to create shapes that are filled with images or other content.</li><li><strong>shape-image</strong> which can be used to create shapes that are responsive to the size of the element.</li><li><strong>shape-overflow</strong> which can be used to create shapes that are clipped or that have content that flows outside of the shape. In the following example shape-overflow: clip will allow the content to overflow the shape, but it will be constrained to the stroke box of the element:</li></ul><pre>.shape {<br>  shape-image: url(https://example.com/image.png);<br>  shape-overflow: clip;<br>}</pre><p><em>Note that as of August 2023, these features are still in draft phase.</em></p><h3>New features for scroll snap</h3><p>I personally really like the scroll snap feature, as it makes the scrolling experience much smoother and it is very easy to implement. If you haven’t worked with scroll-snap before, here is an example of how you can use CSS Scroll Snap to create a snap-to-scrolling behavior for an element:</p><pre>.my-element {<br>  scroll-snap-type: mandatory;<br>  scroll-snap-points-x: repeat(50px, 100px);<br>}</pre><p>This code will create an element that snaps to every 50px on the x-axis and every 100px on the y-axis.</p><p>Scroll snap has been live for a while now, but there are a few of new features that are somewhat new:</p><ul><li><strong>Scroll snap align</strong>: The new scroll-snap-align property allows you to control how an element is aligned when it snaps to a snap position. For example, you can use this property to ensure that an element is always aligned to the top, bottom, center, or left/right of the scroll container. Also in the example below, you can see that there is support for scroll snap in both axes.</li></ul><pre>.container {<br>  overflow-x: scroll;<br>  overflow-y: scroll;<br>  scroll-snap-type: both mandatory; // Support both axes<br>  scroll-snap-align: center;<br>}</pre><ul><li><strong>Better support for touch devices</strong>: making it easier to snap to snap positions using touch gestures.</li></ul><pre>.container {<br>  scroll-snap-type: both mandatory;<br>  scroll-snap-touch-snap-points: true;<br>}</pre><h3>Audio pseudo-classes</h3><p>As part of the Selectors Level 4 update, there are some pseudo-classes added that represent loaded images and videos.</p><p>When it comes to media playback, the :playing, :paused, and :seeking pseudo-classes seem very useful. This is great because we can now easily style these elements to create a more interactive and engaging user experience.</p><p>Another section deals with media loading states and includes :buffering and :stalled. These classes indicate to users that the media will continue playing once loading issues are resolved. Also the pseudo-classes :muted and :volume-locked will be added. These pseudo-classes are a nice way to provide visual feedback, keep users informed, and work with different styling, such as in the following example:</p><pre>video {<br>  opacity: 1;<br>}<br>video:buffering {<br>  background-color: #ccc;<br>  opacity: 0.5;<br>}</pre><p>Overall, these CSS pseudo-classes could be very practical. They’ll be a valuable addition to our web development toolkit, making it easier to handle media elements and improve the overall user experience on our websites. I’m looking forward to using them.</p><p><em>As of August 2023, some of these functions are only available for Safari.</em></p><h3>Current-element pseudo-class</h3><p>The :current pseudo-class is straightforward; it represents the element that is currently being displayed or an ancestor of that element. We could use this to create styles that respond to the user&#39;s current position in a specific element.</p><p>For example, the following rule could be used to highlight the paragraph or anchor element that is being read aloud in a speech rendering of the document:</p><pre>:current(p, a) {<br>  background: yellow;<br>}</pre><p>In addition, the :past and :future pseudo-classes also offer interesting possibilities, representing elements that occur entirely before or after the :current element. The :past pseudo-class represents any element that is defined to occur entirely prior to a :current element. The :future pseudo-class however, represents the element after.</p><h3>New features for subgrid</h3><p>CSS Subgrids are a feature of CSS Grid Layout that allows you to create nested grids within a single grid container, and there are new features coming! A small recap; here is an example of how you can create a subgrid:</p><pre>.my-grid {<br>  display: grid;<br>  grid-template-columns: repeat(2, 1fr);<br>}<br>.my-subgrid {<br>  display: grid;<br>  grid-template-columns: repeat(2, 50px);<br>}<br>.my-grid &gt; .my-subgrid {<br>  grid-column: 1 / 2;<br>}</pre><pre>Grid Container<br>   Column 1<br>       Subgrid<br>         Row 1<br>         Row 2<br>   Column 2</pre><p>As you can see, the subgrid is nested within the grid container. The subgrid has its own grid layout, which is independent of the grid layout of the grid container.</p><p>A new feature of subgrids is <strong>named grid lines. </strong>You will be able to name grid lines on your grid and then position items based on those names rather than the line number, such as in this example:</p><pre>.grid {<br>  display: grid;<br>  grid-template-names: a b c;<br>}<br>.grid .item.a {<br>  grid-column: a;<br>}<br>.grid .item.b {<br>  grid-column: b;<br>}<br>.grid .item.c {<br>  grid-column: c;<br>}</pre><p>Another one is <strong>subgrid alignment </strong>of a child grid to align the grid with the parent grid:</p><pre>.grid {<br>  display: grid;<br>  grid-template-columns: 1fr 1fr;<br>  grid-template-rows: 1fr 1fr 1fr;<br>}<br>.grid .item {<br>  background-color: #ccc;<br>  border: 1px solid black;<br>}<br>.grid .item &gt; .child-grid {<br>  grid-template-columns: 1fr 1fr;<br>  grid-template-rows: 1fr 1fr;<br>  grid-alignment: start start;<br>}</pre><p>The grid-alignment property can be used to align a child grid with its parent. In this example, the child grid is aligned with the parent grid on both the horizontal and vertical axes.</p><p><strong>One downside of subgrids: they can be hard to debug. </strong>If they become hard to debug: use a grid inspector to visualize the layout. In the inspector panel, you will see a number of different tabs. One of the tabs will be the “Grid” tab. The Grid tab will show you a visualization of the layout of the CSS grid. The visualization will show you the grid lines, the grid tracks, and the grid items.</p><p>Overall, I believe that CSS Subgrids are a valuable tool that can be used to create complex and responsive layouts and I am excited to see how they are used in the future with these new features.</p><p><em>Note that as of August, subgrids are not yet supported by all browsers!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ba44d8a45993" width="1" height="1" alt=""><hr><p><a href="https://medium.com/navara/new-upcoming-css-features-2023-ba44d8a45993">New &amp; Upcoming CSS Features In 2023</a> was originally published in <a href="https://medium.com/navara">NAVARA</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>