<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Lab on Thoughts and Ramblings by Mike</title><link>https://mikedent.io/tags/lab/</link><description>Recent content in Lab on Thoughts and Ramblings by Mike</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Mike Dent</copyright><lastBuildDate>Wed, 22 Apr 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://mikedent.io/tags/lab/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Cisco Modeling Labs Earned a Permanent Spot in My Workflow</title><link>https://mikedent.io/post/2026/4/cisco-modeling-labs-workflow/</link><pubDate>Wed, 22 Apr 2026 09:00:00 -0400</pubDate><guid>https://mikedent.io/post/2026/4/cisco-modeling-labs-workflow/</guid><description>
&lt;p&gt;If you are a network engineer who has ever stared down a change window and wished you could test the exact topology before touching production, this post is for you. I want to walk through why Cisco Modeling Labs (CML) has become one of the most used tools in my day to day, and how it has shaped the way I approach design, migrations, and team enablement. The short version: a sandbox that mirrors real gear means fewer surprises at 2 AM, faster validation on design work, and a safer way to bring the next engineer up to speed.&lt;/p&gt;</description></item></channel></rss>