<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Blog of Mathias</title><link>https://blog.mathiasegekvist.dk/</link><description>Recent content on Blog of Mathias</description><generator>Hugo</generator><language>en-GB</language><lastBuildDate>Sat, 27 Sep 2025 13:01:32 +0200</lastBuildDate><atom:link href="https://blog.mathiasegekvist.dk/index.xml" rel="self" type="application/rss+xml"/><item><title>Tools</title><link>https://blog.mathiasegekvist.dk/posts/tools/</link><pubDate>Sat, 27 Sep 2025 13:01:32 +0200</pubDate><guid>https://blog.mathiasegekvist.dk/posts/tools/</guid><description>&lt;p>Software are getting all these smart tools that can do all kind of fancy stuff for a small fee.&lt;/p>
&lt;p>I generally like the idea behind it but often a tool ends up being something you&amp;rsquo;ll have to learn. If you have to spend time learning something why not learn the technology behind it all, so you have more freedom?&lt;/p>
&lt;p>I realise that knowing the tool behind it all sometimes still demand a lot of handheld work which you can skip with a tool. I just prefer having simple tools automating the repetitive and hard tasks and then leaving the rest open to use.&lt;/p>
&lt;p>If you have used an ORM for database calls you know that it&amp;rsquo;s sometimes super smart and sometimes irritating. You can do basic calls super easy without writing SQL. Often you can also insert SQL directly in some way. I just don&amp;rsquo;t understand what&amp;rsquo;s dangerous about SQL. If you collect everything in SQL files you&amp;rsquo;ll have direct control about precisely what happens where.&lt;/p>
&lt;p>I could write for ages about ORMs. I don&amp;rsquo;t mind them. I have tried using them where it was really convenient and I tried using it where the integration and the breaking changes was not worth it.&lt;/p></description></item><item><title>Hosting</title><link>https://blog.mathiasegekvist.dk/posts/hosting/</link><pubDate>Sat, 27 Sep 2025 12:51:59 +0200</pubDate><guid>https://blog.mathiasegekvist.dk/posts/hosting/</guid><description>&lt;h2 id="hosting-is-always-a-question">Hosting is always a question&lt;/h2>
&lt;p>There are tons of hosting options out there with a ton of different options.&lt;/p>
&lt;p>Many companies normally defaults to either Microsoft or Amazon because they believe they need the capabilities or support. I have not been a place that truly needed anything from them. It might also be something about availability, developer experiences and too big to fail.&lt;/p>
&lt;p>I think it is a shame that they don&amp;rsquo;t try other places.&lt;/p>
&lt;p>I have been a fan of Digital Ocean for a long time, because it was super simple and I have only used it for small scale sites. They are now transitioning to making more money, which I understand, but that bloats their site, with one click AI installations and all kinds of smart stuff I don&amp;rsquo;t need.&lt;/p>
&lt;p>I still use them but mainly because of familiarity. With the new political landscape I would also like to support more European companies.&lt;/p>
&lt;p>I do like how their App Platform let&amp;rsquo;s me have a super simple CI/CD integration with Github and one click deployment where it figures out most behind the scenes. It&amp;rsquo;s really smart when it works. But as you know, sometimes you want to do custom stuff and then it&amp;rsquo;s a tool to learn and then you might as well learn and setup a simple nginx config.&lt;/p></description></item><item><title>My First Post</title><link>https://blog.mathiasegekvist.dk/posts/my-first-post/</link><pubDate>Sat, 27 Sep 2025 10:08:52 +0200</pubDate><guid>https://blog.mathiasegekvist.dk/posts/my-first-post/</guid><description>&lt;h2 id="hugo-as-a-tool-for-making-a-blog">Hugo as a tool for making a blog&lt;/h2>
&lt;p>This is my first test with Hugo. So far the response time is incredibly fast and the documentation is really easy to follow along. I am pleasantly surprised that it uses MarkDown files to post pages. This means I can make a vault and edit my posts in Obsidian, which I have grown quite fund of as a note/idea tool.&lt;/p>
&lt;h3 id="issues">Issues&lt;/h3>
&lt;p>I had some trouble getting it to work as a route &lt;code>mathiasegekvist/blog&lt;/code> but I am unsure if that is the way hugo is made or the way Digital Ocean tries to deploy it.
I tried a bunch of stuff but it kept making the links for styling and assets wrong.
I ended up making it as another deployment in Digital Ocean and then routing to &lt;code>blog.mathiasegekvist.dk&lt;/code> instead. That worked perfectly out of the box.&lt;/p>
&lt;pre tabindex="0">&lt;code>&lt;/code>&lt;/pre></description></item></channel></rss>