<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>It-Culture on Roethof.Net</title><link>https://roethof.net/tags/it-culture/</link><description>Recent content in It-Culture on Roethof.Net</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>ronny@roethof.net (Ronny Roethof)</managingEditor><webMaster>ronny@roethof.net (Ronny Roethof)</webMaster><copyright>© 2026 Ronny Roethof</copyright><lastBuildDate>Fri, 19 Jun 2026 09:33:04 +0200</lastBuildDate><atom:link href="https://roethof.net/tags/it-culture/index.xml" rel="self" type="application/rss+xml"/><item><title>The Commodity IT Fallacy: How We Outsourced Technical Sovereignty</title><link>https://roethof.net/posts/2026/06/the-commodity-it-fallacy/</link><pubDate>Fri, 19 Jun 2026 00:00:00 +0200</pubDate><author>ronny@roethof.net (Ronny Roethof)</author><guid>https://roethof.net/posts/2026/06/the-commodity-it-fallacy/</guid><description>We haven&amp;rsquo;t just outsourced our hardware; we&amp;rsquo;ve outsourced our technical problem-solving capability. The ultimate sovereignty question: when the system fails, who is allowed to fix it?</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://roethof.net/posts/2026/06/the-commodity-it-fallacy/cover.png"/></item></channel></rss>