<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Backend on Tobys Portfolio</title><link>https://portfolio.obli.dk/tags/backend/</link><description>Recent content in Backend on Tobys Portfolio</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 15 Mar 2026 14:00:00 +0100</lastBuildDate><atom:link href="https://portfolio.obli.dk/tags/backend/index.xml" rel="self" type="application/rss+xml"/><item><title>Security - Protecting the Backend</title><link>https://portfolio.obli.dk/posts/week7-security/</link><pubDate>Sun, 15 Mar 2026 14:00:00 +0100</pubDate><guid>https://portfolio.obli.dk/posts/week7-security/</guid><description>&lt;h1 id="security---protecting-the-backend"&gt;Security - Protecting the Backend&lt;/h1&gt;
&lt;p&gt;This week focused on something that is easy to overlook early in development, but absolutely critical in real systems: &lt;strong&gt;security&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;While the previous week introduced authentication and testing, this week was about understanding how to properly protect the backend.&lt;/p&gt;
&lt;h2 id="from-functionality-to-responsibility"&gt;From functionality to responsibility&lt;/h2&gt;
&lt;p&gt;Up until this point, my focus had mostly been:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;making endpoints work&lt;/li&gt;
&lt;li&gt;returning correct data&lt;/li&gt;
&lt;li&gt;structuring the backend properly&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;But this week introduced a different perspective:&lt;/p&gt;</description></item></channel></rss>