<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>It on doismiu - dispatches from the infernal archive</title><link>https://doismiu.blog/tags/it/</link><description>Recent content in It on doismiu - dispatches from the infernal archive</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Jan 2026 00:00:00 +0100</lastBuildDate><atom:link href="https://doismiu.blog/tags/it/index.xml" rel="self" type="application/rss+xml"/><item><title>The Only Correct Way to Return API Data</title><link>https://doismiu.blog/posts/the-only-correct-way-to-return-api-data/</link><pubDate>Sat, 10 Jan 2026 00:00:00 +0100</pubDate><guid>https://doismiu.blog/posts/the-only-correct-way-to-return-api-data/</guid><description>&lt;p&gt;We live in an era of digital excess where developers are taught to believe that &lt;strong&gt;the goal of an API is to serve data&lt;/strong&gt;. This is a &lt;strong&gt;fundamental fallacy&lt;/strong&gt; that has cost billions in infrastructure and security around the world. We spent years debating REST versus GraphQL or gRPC versus WebSockets and forgot to look at the most elegant and performant solution that exists. I am speaking of the concept of &lt;strong&gt;No as a Service or NaaS&lt;/strong&gt; (&lt;a href="https://github.com/hotheadhacker/no-as-a-service)"&gt;https://github.com/hotheadhacker/no-as-a-service)&lt;/a&gt;.&lt;/p&gt;</description></item></channel></rss>