<?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 Ismo Aro on Medium]]></title>
        <description><![CDATA[Stories by Ismo Aro on Medium]]></description>
        <link>https://medium.com/@ismo-aro?source=rss-3ea8a1db38b9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*QgShCiRHa7Z0KMeSdplIVw.jpeg</url>
            <title>Stories by Ismo Aro on Medium</title>
            <link>https://medium.com/@ismo-aro?source=rss-3ea8a1db38b9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 15:13:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ismo-aro/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[DevSecOps]]></title>
            <link>https://ismo-aro.medium.com/devsecops-d5adad2dc324?source=rss-3ea8a1db38b9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d5adad2dc324</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[devsecops]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[devsecops-solutions]]></category>
            <category><![CDATA[devops-practice]]></category>
            <dc:creator><![CDATA[Ismo Aro]]></dc:creator>
            <pubDate>Mon, 24 May 2021 17:28:28 GMT</pubDate>
            <atom:updated>2021-05-24T17:28:28.988Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>DevSecOps</strong> is not only a technology, or tool, or practise or even a mindset — it’s all of these and much more. Where DevSecOps can help in vintage software projects, it is an essential component of modern, accurate and fast software development. <br>DevSecOps includes the following parts: DevSecOps mindset, Delivery Pipelines, Test Automation, Security and Environments, which are all covered by <a href="https://www.northcode.fi/">NorthCode</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PJEXun7eArinaMl34ZXZpw.jpeg" /></figure><h3>DevSecOps mindset</h3><p>Feedback loops are within the core of the DevSecOps mindset. Whenever we change things, we want to receive feedback as soon and as accurately as possible. Automation plays a core role. We rely on automation to give us feedback in order for us to understand the quality of the changes made. Fast release cycles are also an important component, as customer feedback is what really counts in the end.</p><h3>Delivery Pipelines</h3><p>Code in a developer’s hard drive does not create any additional value to the end user, but code in the production process can potentially do so. This is why we need fast and reliable delivery pipelines that are as highly automated as possible.</p><h3>Test Automation</h3><p>To ensure quality, we need to have Quality Gates in our pipelines. Test Automation plays a key role here as well. Quality Gates operate on every level of a test pyramid, starting with the lowest level (e.g. Unit Test). The further each change goes within the Delivery Pipeline, the higher level tests are executed (eg. Integration and Acceptance Test). If critical tests fail in the pipeline, delivery is halted and each specific problem is fixed.</p><h3>Security</h3><p>Traditionally security audits are done at the end of each project, but within the DevSecOps domain they are executed on a constant basis. The aim is to bring security in on day one, with scans and executed in delivery pipelines to ensure fast feedback with immediate, on-the-spot problem-solving.</p><h3>Environments</h3><p>DevSecOps relies heavily on Infrastructure as a Code paradigm: as modern software development relies more and more on Cloud Native, we need to take into account that ageing machines exist and need regular maintenance and updating. It doesn’t matter if your infrastructure is built from a hardware pc to serverless functions in the cloud, you can still automate all environmental maintenance via the infrastructure as code.</p><p><strong>DevSecOps</strong> covers everything from developmental environments to production environments and the necessary monitoring for each one of these areas to give you a fast, more reliable and controlled outcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5adad2dc324" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Always A Step Ahead]]></title>
            <link>https://ismo-aro.medium.com/always-a-step-ahead-6b9b9a324a01?source=rss-3ea8a1db38b9------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b9b9a324a01</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[sharing-is-caring]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Ismo Aro]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 05:30:53 GMT</pubDate>
            <atom:updated>2021-03-02T05:30:53.935Z</atom:updated>
            <content:encoded><![CDATA[<h3>What takes us further as mankind?</h3><p>Innovation and technology constantly reshape the evolution of mankind, taking us further into the future — we believe the two should be shared.</p><p>Once we commit to sharing technological and innovative advancements, progress will naturally reveal itself in leaps and bounds. We believe it is of service to all of us to distribute information, instead of keeping it to ourselves. It helps us create new services and products, which in turn bring food onto everyone’s table, making it a win-win all round.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1AJZEeQ_dwkf6fFY9vTVuQ.jpeg" /></figure><h3>Standardized work</h3><p>Standardized work is basically any mechanical performance in a constant form of repetition, with constantly improving outcomes. It is a core element within Lean practices. This seldom works in coding. You could compare coding to the work of an artist, where creation, observation, deduction and even chance play vital roles.</p><p>This is never the case in standardized work where e.g. code and number crunching by computers are essential. Standardized work can be utilised by your Delivery Pipeline, Build Script or even for spinning new environments.</p><h3>Intellectual Property (IPR)</h3><p>If you’re creating shareable innovation and technology, why not share it without the risk of harming your business? Perhaps you can help in creating a tool to solve a common problem within an entire industry?</p><p>Although we understand that when you are sharing your technological capital with other entities, who ultimately use it for their own distinct advantage, you might feel you’re getting the short end of the stick.</p><p>But let’s look at it from a different angle — once you start sharing your intellectual property, which others will use, you are positioning yourself at the top of the IPR hierarchy giving you the competitive edge. In addition, you’ll have the benefit of gathering valuable information from each user, so as to develop your tool even further, giving it a broader scope.</p><h3>Knowledge Capital</h3><p>Rather than seeing code and documentation as an exclusive privilege, we should place more focus on people and identify human knowledge as a very valuable commodity. Knowledge should always be nurtured and fostered as the ultimate human capital.</p><h3>Our path at NorthCode?</h3><p>As a company, how do we practice what we preach?</p><p>At <a href="https://www.northcode.fi/">NorthCode</a>, we made a clear decision to collect all our standardized work under one project: <a href="https://github.com/TheProjectAurora">The Project Aurora</a>. The Project Aurora is distinctly based on Open Sourcing of standardized work. We decided not to give it our company’s unique brand, but instead to open up a complete community of people to join in on the journey of creating real change in an ever-evolving, shared world — together.</p><p>Please feel free to explore our work with The Project Aurora at Github and join us on this journey.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b9b9a324a01" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>