<?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 Vetle Leinonen-Roeim on Medium]]></title>
        <description><![CDATA[Stories by Vetle Leinonen-Roeim on Medium]]></description>
        <link>https://medium.com/@vetler?source=rss-b25d1cbef1b2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hmU_mzLq2QwCFEsBk1XdGg.jpeg</url>
            <title>Stories by Vetle Leinonen-Roeim on Medium</title>
            <link>https://medium.com/@vetler?source=rss-b25d1cbef1b2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 07:23:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@vetler/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[Hjemmekontor til besvær]]></title>
            <link>https://medium.com/dfind-consulting/hjemmekontor-til-besv%C3%A6r-9e896f453356?source=rss-b25d1cbef1b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9e896f453356</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[systemutvikling]]></category>
            <dc:creator><![CDATA[Vetle Leinonen-Roeim]]></dc:creator>
            <pubDate>Sun, 25 Apr 2021 22:37:49 GMT</pubDate>
            <atom:updated>2021-04-25T22:37:49.473Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dwzD4nSclN7niVbyBmkPZA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@frantic?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Alex Kotliarskyi</a> on <a href="https://unsplash.com/s/photos/open-office-plan?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Opprinnelig publisert på <a href="https://www.kode24.no/kodenytt/hjemmekontor-passer-darlig-for-ledere-som-liker-micromanagement/73637916">kode24.no</a></p><p>Daglig leder i Alv, Marcus Sahlin Pettersen, skal i hvert fall ha skryt for å våge å gå mot strømmen når han skriver at han <a href="https://www.kode24.no/kodenytt/konsulent-sjef-vil-ha-utviklerne-sine-i-apne-landskap/73623233">vil ha utviklerne sine i åpne landskap</a>. Veldig mange utviklere opplever hjemmekontor positivt, og mange går så langt som å si at de <a href="https://www.kode24.no/nedetid/uaktuelt-a-sitte-i-apent-landskap-noen-gang-igjen/73542449">aldri vil tilbake på kontorene fem dager i uka som før</a>.</p><p>Han sender et sterkt og tydelig signal om hva som er viktig for han, og legger inn et spark til utviklerne — “<em>Hvordan kan det ha seg at de samme utviklerne som i årevis har ropt høyt om at de ikke involveres i stor nok grad eller tidlig nok, nå uttaler seg over fortreffeligheten av hjemmekontor?”</em></p><p>Uten å gå inn på hvor ansvaret for å involvere ansatte ligger, så vitner dette på at Sahlin Pettersen ikke har fulgt med i timen det siste året, mens mange andre har innsett realiteten; at vi må forberede oss på en fremtid med distribuerte team.</p><p>Selvfølgelig er ikke hjemmekontor uten problemer, og han har nok rett i mye av det han sier; det kan være vanskelig å fange opp små signaler, og det kan være effektivt å sitte sammen når man skal løse en del type problemer — men er det slik at vi etter et år på hjemmekontor ikke har maktet å gjøre disse tingene?</p><p>At han ønsker god oppfølging av juniorer og andre medarbeidere er selvfølgelig bra, men hva da med senioren som tar på seg de støydempende hodetelefonene og irriterer seg over alt maset eller utvikleren som er langt nede i en vanskelig problemstilling og blir avbrutt fordi noen spør om han vil ha kanelbolle eller spille bordtennis?</p><p>Å ha distribuerte team krever naturligvis endringer, både i hvordan vi samarbeider, men også i ledelsesstil og personaloppfølging — det passer dårlig med hjemmekontor for ledere som liker micromanagement eller som føler de mister kontrollen når de ikke kan se alle sitte sammen.</p><p>Nå har både ledere og utviklere fått erfare hvordan det er å ha hjemmekontor i over ett år, og om det er mange som foretrekker dette så ville det vært rart å ikke ha det som en mulighet. Her er det kanskje til og med er en mulighet her for arbeidsgivere som våger ta steget fullt ut, som legger til rette for de som ønsker det, og ikke bare må ha folk på kontoret bare fordi det var slik det ble gjort før og ikke greier å håndtere at verden endrer seg.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9e896f453356" width="1" height="1" alt=""><hr><p><a href="https://medium.com/dfind-consulting/hjemmekontor-til-besv%C3%A6r-9e896f453356">Hjemmekontor til besvær</a> was originally published in <a href="https://medium.com/dfind-consulting">Dfind Consulting</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Software is eating the world, but remember to brush its teeth]]></title>
            <link>https://medium.com/@vetler/software-is-eating-the-world-but-remember-to-brush-its-teeth-9d27f0aa5d10?source=rss-b25d1cbef1b2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d27f0aa5d10</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[software-engineering]]></category>
            <dc:creator><![CDATA[Vetle Leinonen-Roeim]]></dc:creator>
            <pubDate>Wed, 07 Nov 2018 22:53:58 GMT</pubDate>
            <atom:updated>2018-11-07T22:53:58.082Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4zO37fLhu0ZXIxk68QH-Jw.jpeg" /></figure><p>If software is eating the world, as <a href="https://www.wsj.com/articles/SB10001424053111903480904576512250915629460">Marc Andreesen wrote in 2011</a>, then security vulnerabilities are its toothaches and cavities. As time goes on, as software continues eating and consuming every industry in its path, it only gets worse. Maybe the analogy is starting to fall apart at this point, but you should get the idea.</p><p>In software development, it can actually be impossible to know if a component in your system has a security vulnerability. Components you thought were safe, may suddenly turn out to have big security holes in them. This is nothing new — it has happened before, and will happen again. It happened in 2017 with the Apache Struts flaw, resulting in the <a href="https://arstechnica.com/information-technology/2017/09/massive-equifax-breach-caused-by-failure-to-patch-two-month-old-bug/">Equifax hack</a> exposing personal information on 143 million Americans and 40 million people in the UK. This happened in 2018 with <a href="https://en.wikipedia.org/wiki/Meltdown_(security_vulnerability)">Meltdown</a> and <a href="https://en.wikipedia.org/wiki/Spectre_(security_vulnerability)">Spectre</a>, which exposed flaws in popular CPUs — flaws so severe that many initially thought they were false. As I write this, a new flaw in SSDs is being exposed, which makes full-disk encryption such as BitLocker worthless.</p><p>Data breaches due to security flaws happen all the time — in addition to Equifax in 2017, we can mention a few other breaches that happened that year; Verizon exposing data for 14 million customers, Uber with data on 57 million riders and drivers, and Deep Root Analytics with data on 200 million American voters. These are just a few examples, but probably the most severe. We can only guess what all this data is being used for now, but it is not something people were expecting to be in the wild.</p><p>Meltdown and Spectre are two interesting cases, because they affect such a central component in every software system — the very component that is in charge of performing the fundamental operations of the system. Simply explained, these flaws made it possible for software to get private data from other software running on the same computer, by exploiting how CPUs and operating systems work. And in this case, like in many other security flaws, it is impossible to know if it was exploited by anyone, because it is not possible to detect when someone takes advantage of it.</p><p>There is actually no way to know of any future vulnerability in a component of your system — it could keep working problem free for years, and maybe nothing is ever found, or a severe flaw could be just around the corner. Even if flaws are found, it is not a given that whoever found it will disclose it to the people responsible and make sure it is fixed; they may want to take advantage of it, or even sell it to someone else. This may sound like fiction, but it is very real.</p><p>If you think these things don’t apply to you, because your system doesn’t handle sensitive data, then let me stop you right there — your system could just as well be used as a way of attacking users to get into other systems by injecting malicious data into it. Passwords are also popular targets, as users often reuse them on other systems, and they enter them into your system in good faith that you will keep them safe.</p><p>It does seem as if we have no choice; we have to put security first. It’s not optional, it’s not something you add later — you do it from the start, and you do it continuously. Most likely it is never done, and it adds cost — both time and money. Non-technical people might wonder if it’s really necessary, and we can’t really blame them for not knowing the full scope and cost of this; after all, they don’t know how software and security works. There may also be many technical people who don’t know or want to admit the full scope of this either, but looking at the severity and sheer number of breaches happening all over the world, I believe we have a moral obligation to take responsibility, and to work to make everyone understand the importance of security and how it affects almost everything. We can’t wait for non-technical people to raise concerns, we have to do it ourselves — they don’t know what to ask for.</p><p>Software may be eating the world, but we are forever doomed to maintain and patch it for vulnerabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d27f0aa5d10" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>