<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Tim Rutte&apos;s blog</title><description>Articles on AWS, backend architecture and AI in production. From projects, not from slides.</description><link>https://timrutte.de/</link><language>en</language><item><title>Cutting AWS costs: from 15,000 to 2,500 euros a month</title><link>https://timrutte.de/en/blog/aws-cost-reduction-case-report/</link><guid isPermaLink="true">https://timrutte.de/en/blog/aws-cost-reduction-case-report/</guid><description>Twelve months of FinOps across two real AWS accounts: where the large amounts were, why Athena and CloudWatch cost more than the databases, and why commitments come last.</description><pubDate>Wed, 19 Aug 2026 12:00:00 GMT</pubDate></item><item><title>An AI system on a zero budget: six decisions, three mistakes</title><link>https://timrutte.de/en/blog/ai-in-production-on-zero-budget/</link><guid isPermaLink="true">https://timrutte.de/en/blog/ai-in-production-on-zero-budget/</guid><description>Six architectural decisions and three mistakes from an AI side project that must cost nothing. With real code and the places where it went wrong.</description><pubDate>Tue, 18 Aug 2026 12:00:00 GMT</pubDate></item><item><title>Bad architecture sends no alerts. It just keeps costing.</title><link>https://timrutte.de/en/blog/finops-aws-hidden-architecture-costs/</link><guid isPermaLink="true">https://timrutte.de/en/blog/finops-aws-hidden-architecture-costs/</guid><description>Where four- and five-figure amounts quietly disappear in grown AWS setups, and how to get them back without changing a single line of code.</description><pubDate>Thu, 11 Jun 2026 12:00:00 GMT</pubDate></item><item><title>When AWS loses a region: what actually matters when it gets serious</title><link>https://timrutte.de/en/blog/aws-region-outage-multi-region/</link><guid isPermaLink="true">https://timrutte.de/en/blog/aws-region-outage-multi-region/</guid><description>What actually matters when an AWS region goes down: multi-region strategies, realistic failover concepts and the costs nobody plans for.</description><pubDate>Thu, 09 Apr 2026 12:00:00 GMT</pubDate></item><item><title>Agentic coding with spec-driven development: why your AI agent needs structure before it writes code</title><link>https://timrutte.de/en/blog/agentic-coding-spec-driven-development/</link><guid isPermaLink="true">https://timrutte.de/en/blog/agentic-coding-spec-driven-development/</guid><description>Why your AI agent needs structure before it writes code. Spec-driven development as a method for predictable, consistent quality with AI tools.</description><pubDate>Mon, 30 Mar 2026 12:00:00 GMT</pubDate></item><item><title>Go in a PHP world: adding high-performance services without rebuilding everything</title><link>https://timrutte.de/en/blog/golang-in-a-php-world/</link><guid isPermaLink="true">https://timrutte.de/en/blog/golang-in-a-php-world/</guid><description>How I add new high-performance Go services to existing PHP systems without rebuilding everything. Strangler fig in practice instead of a big-bang rewrite.</description><pubDate>Tue, 03 Feb 2026 12:00:00 GMT</pubDate></item><item><title>Why full rewrites almost always fail</title><link>https://timrutte.de/en/blog/why-full-rewrites-fail/</link><guid isPermaLink="true">https://timrutte.de/en/blog/why-full-rewrites-fail/</guid><description>Rewrites fail, and so does standing still. Why the complete rebuild almost never works and how incremental modernization delivers measurable results.</description><pubDate>Sun, 11 Jan 2026 12:00:00 GMT</pubDate></item><item><title>From Sphinx to Manticore Search: a migration about latency, relevance and operational discipline</title><link>https://timrutte.de/en/blog/from-sphinx-to-manticore-search/</link><guid isPermaLink="true">https://timrutte.de/en/blog/from-sphinx-to-manticore-search/</guid><description>A search migration from Sphinx to Manticore about latency, relevance and operational discipline. From 5 seconds to under 100 ms in practice.</description><pubDate>Thu, 10 Jul 2025 12:00:00 GMT</pubDate></item><item><title>Technical debt as business risk, and why nobody listens until it is too late</title><link>https://timrutte.de/en/blog/technical-debt-as-business-risk/</link><guid isPermaLink="true">https://timrutte.de/en/blog/technical-debt-as-business-risk/</guid><description>Technical debt is not a developer problem. It is a business risk, and it grows quietly until it becomes visible exactly when there is no room for it.</description><pubDate>Thu, 03 Apr 2025 12:00:00 GMT</pubDate></item></channel></rss>