<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>modernization on Code it Yourself</title><link>https://carlos.mendible.com/tags/modernization/</link><description>Recent content in modernization on Code it Yourself</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Carlos Mendible</copyright><lastBuildDate>Mon, 19 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://carlos.mendible.com/tags/modernization/index.xml" rel="self" type="application/rss+xml"/><item><title>Classify Your Azure VMs into Modernization Waves with azqr</title><link>https://carlos.mendible.com/2026/10/19/classify-your-azure-vms-into-modernization-waves-with-azqr/</link><pubDate>Mon, 19 Oct 2026 00:00:00 +0000</pubDate><guid>https://carlos.mendible.com/2026/10/19/classify-your-azure-vms-into-modernization-waves-with-azqr/</guid><description>&lt;p&gt;A list of VM sizes only tells you half the story. An AKS node, an application server and a vendor appliance can all run on an older VM series, but each one needs a very different migration plan. Before picking a target size, you need to know &lt;strong&gt;what each VM does, who manages it and what must be checked before it can move&lt;/strong&gt;.&lt;/p&gt;</description></item></channel></rss>