<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Yetric Blog: Company</title>
    <subtitle>Posts in the Company category.</subtitle>
    <link href="https://yetric.com/blog/categories/company/feed.xml" rel="self"/>
    <link href="https://yetric.com/blog/categories/company/"/>
    
    <updated>2026-02-20T00:00:00Z</updated>
    <id>https://yetric.com/blog/categories/company/</id>
    <author>
        <name>Yetric</name>
    </author>
    
    <entry>
        <title>New Site, New Chapter</title>
        <link href="https://yetric.com/blog/posts/new-site-new-chapter/"/>
        <updated>2026-02-20T00:00:00Z</updated>
        <id>https://yetric.com/blog/posts/new-site-new-chapter/</id>
        
        <category term="company"/>
        
        
            
            
        <category term="company"/>
            
        <category term="site-updates"/>
            
        <category term="writing"/>
            
        
        
        <summary>yetric.com has a new home. A fresh site, a renewed commitment to writing, and a collection of older posts worth revisiting.</summary>
        
        <content type="html">&lt;p&gt;The new yetric.com is up.&lt;/p&gt;
&lt;p&gt;It&#39;s been a while since the old site was actively maintained, and I decided it was time to start fresh — cleaner design, better structure, and a real commitment to writing more regularly.&lt;/p&gt;
&lt;p&gt;Yetric is my software development and consulting practice based in Sweden. I work with teams on building products, modernizing systems, and making better decisions around architecture and data. If any of that sounds relevant to what you&#39;re working on, the &lt;a href=&#34;https://yetric.com/about/&#34;&gt;about page&lt;/a&gt; has more.&lt;/p&gt;
&lt;h2 id=&#34;what-s-coming&#34; data-toc-text=&#34;What&#39;s coming&#34;&gt;What&#39;s coming&lt;/h2&gt;
&lt;p&gt;This blog is where I&#39;ll write about things I run into in real work:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Architecture decisions and how to make them without pretending they&#39;re permanent.&lt;/li&gt;
&lt;li&gt;Moving away from legacy systems without burning everything down.&lt;/li&gt;
&lt;li&gt;Building short feedback loops so mistakes stay small.&lt;/li&gt;
&lt;li&gt;The intersection of data, product, and engineering — and how to align them.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;More soon, and more regularly than before.&lt;/p&gt;
&lt;h2 id=&#34;worth-reading-from-the-archive&#34; data-toc-text=&#34;Worth reading from the archive&#34;&gt;Worth reading from the archive&lt;/h2&gt;
&lt;p&gt;I&#39;ve brought over a handful of older posts from the previous site that I think still hold up:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://yetric.com/blog/posts/technical-debt/&#34;&gt;Unraveling Technical Debt: The Silent Software Killer&lt;/a&gt; — on the compounding cost of ignoring shortcuts in your codebase.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://yetric.com/blog/posts/analytics-gdpr-compliance/&#34;&gt;Navigating Analytics and GDPR Compliance&lt;/a&gt; — key considerations for running analytics without running afoul of data protection law.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://yetric.com/blog/posts/alternatives-to-react/&#34;&gt;Modern Alternatives to React&lt;/a&gt; — a look at Svelte, Preact, Solid, and Web Components.&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://yetric.com/blog/posts/whats-in-a-name/&#34;&gt;What&#39;s in a Name?&lt;/a&gt; — the story behind Yetric, for anyone curious about where the name came from.&lt;/li&gt;
&lt;/ul&gt;
</content>
    </entry>

    <entry>
        <title>What's in a Name?</title>
        <link href="https://yetric.com/blog/posts/whats-in-a-name/"/>
        <updated>2019-10-20T00:00:00Z</updated>
        <id>https://yetric.com/blog/posts/whats-in-a-name/</id>
        
        <category term="company"/>
        
        
            
            
        <category term="branding"/>
            
        <category term="company"/>
            
        <category term="founder-story"/>
            
        
        
        <summary>The story behind the name Yetric — from Strategio to 80 Ridge Street Media to "yet another metric solution".</summary>
        
        <content type="html">&lt;p&gt;This week a friend of mine asked me: &amp;quot;Why is it called Yetric? Any idea behind it or is it just something you grabbed from thin air?&amp;quot;. There is an idea. Actually. If you have 2–3 minutes to spare, here&#39;s how the name came about.&lt;/p&gt;
&lt;h2 id=&#34;why-is-the-company-called-yetric&#34; data-toc-text=&#34;Why is the company called Yetric?&#34;&gt;Why is the company called Yetric?&lt;/h2&gt;
&lt;p&gt;I&#39;ve had a company for over 10 years. Mainly focusing on building smaller projects and hoping that one of them would sooner or later generate some income. During that period I learned a lot about finding niches, crafting the offer, and measuring how well a product delivers to the user and to the product&#39;s owner (which was often me).&lt;/p&gt;
&lt;p&gt;One of the things I am really proud of in my life is that me and my dad built a house in 2010. I lived there for over 7 years with my three kids and my wife. Around 2011 I changed my individual company — named Strategio — to a limited company. I tried to keep the name, but I wasn&#39;t allowed, since naming limited companies is harder than individual ones (at least here in Sweden). So I had to pick a new name.&lt;/p&gt;
&lt;p&gt;I used the address to the house me and my dad built: &lt;strong&gt;80 Ridge Street Media&lt;/strong&gt;. I added &amp;quot;Media&amp;quot; since it&#39;s vague and kind of lets you offer a lot of different services and products. I was quite happy with the name.&lt;/p&gt;
&lt;p&gt;In 2017 me and my wife went through a divorce and we sold the house. I was really close to quitting everything that had to do with having a business. But after some reasoning with myself, I decided to continue — the name just felt strange. It was named after something I didn&#39;t own anymore, and it didn&#39;t feel right.&lt;/p&gt;
&lt;p&gt;So I had to come up with a new name.&lt;/p&gt;
&lt;p&gt;&amp;quot;What do I actually want to do for a living?&amp;quot; That was the big question.&lt;/p&gt;
&lt;p&gt;I want to live off my products. In order to do that, I need to either scale them up, build new ones, or build and sell products. I don&#39;t want to sell stuff I built — it felt bad when I sold the house my dad and I had built together. I really wanted to create things I owned and cared about.&lt;/p&gt;
&lt;p&gt;What am I good at? I&#39;m quite good at coding, building user experiences, measuring the impact, and tweaking products according to data. So I decided on two things:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;I must do some consulting in order to make a living the first few years.&lt;/li&gt;
&lt;li&gt;I want to build a product that helps small business owners with the stuff I had been working on for a long time.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;What name should that product have? &lt;em&gt;Yet another metric solution.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;That&#39;s where I found it. I checked domain names, social media accounts — and &lt;strong&gt;Yetric&lt;/strong&gt; was born. I registered the new name, and that&#39;s what&#39;s in a name.&lt;/p&gt;
</content>
    </entry>


</feed>
