<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Opinion on The Coders Blog</title><link>https://thecodersblog.com/tag/opinion/</link><description>Recent content in Opinion on The Coders Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 10 May 2026 15:58:40 +0000</lastBuildDate><atom:link href="https://thecodersblog.com/tag/opinion/index.xml" rel="self" type="application/rss+xml"/><item><title>Cloud Computing: Returning to AWS and Rediscovering Its Flaws</title><link>https://thecodersblog.com/return-to-aws-reasons-for-leaving-2026/</link><pubDate>Sun, 10 May 2026 15:58:40 +0000</pubDate><guid>https://thecodersblog.com/return-to-aws-reasons-for-leaving-2026/</guid><description>&lt;p&gt;The hum of familiar servers, the scent of possibility, the undeniable gravitational pull of the market leader. After a period of exploration and seeking greener pastures, our team recently found ourselves drawn back into the orbit of Amazon Web Services (AWS). It wasn&amp;rsquo;t a capitulation; it was a strategic, albeit somewhat reluctant, repositioning. We’d left AWS for reasons that felt substantial at the time – complexity that gnawed at productivity, a growing unease about vendor lock-in, and an opaque billing structure that felt more like a mystery novel than a financial report. Returning, however, has been less a joyous homecoming and more a rediscovery of those very same, persistent flaws, now viewed through a more seasoned lens.&lt;/p&gt;</description></item></channel></rss>