<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Memfida</title><description>Three engineers talk about the cloud systems they build and run: AWS, Kubernetes, AI, and the problems that come with them. New episode every two weeks.</description><link>https://memfida.com/</link><language>en-gb</language><item><title>Episode 1 · Legacy is an ownership problem</title><link>https://memfida.com/podcast/1/</link><guid isPermaLink="true">https://memfida.com/podcast/1/</guid><description>If you are trying to get a legacy system retired and cannot get it prioritised, we go through what stalls that work, how to make the saving land with a business, and the sequence we use to finish one.</description><pubDate>Sun, 23 Aug 2026 00:00:00 GMT</pubDate><category>Enterprise software</category><category>Engineering culture</category></item><item><title>The power of inflated self-assessment</title><link>https://memfida.com/articles/2026-08-22-the-power-of-inflated-self-assessment/</link><guid isPermaLink="true">https://memfida.com/articles/2026-08-22-the-power-of-inflated-self-assessment/</guid><description>The loud colleague who has an opinion on everything, and the engineer who has spent five years inside a control plane and says nothing in the design meeting. Both are misjudging themselves, and a paper by Kruger and Dunning explains the psychological aspect behind their behaviors. Telling somebody they are wrong is not the right intervention. Telling them they are experts does not make them experts. Training them is the right intervention and the right path to make them experts.</description><pubDate>Sat, 22 Aug 2026 00:00:00 GMT</pubDate><category>Engineering culture</category></item><item><title>The shutdown plan is seven years old</title><link>https://memfida.com/articles/2026-08-16-the-shutdown-plan-is-seven-years-old/</link><guid isPermaLink="true">https://memfida.com/articles/2026-08-16-the-shutdown-plan-is-seven-years-old/</guid><description>A legacy ecommerce core was scheduled for shutdown in 2019 and has more systems depending on it now than it had then. Three replacement projects put it there. Outlived three CIOs, one office move, and a vendor that is not reachable. The cost of keeping it is growing, split across ten cost centres, and attributable to nobody. The cost of removing it requires one owner and one budget line, but yet, the legacy runs today.</description><pubDate>Sun, 16 Aug 2026 00:00:00 GMT</pubDate><category>Enterprise software</category><category>Cloud cost</category><category>Engineering culture</category></item></channel></rss>