<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>JML on That Bearded IT Guy</title><link>https://thatbeardeditguy.co.uk/tags/jml/</link><description>Recent content in JML on That Bearded IT Guy</description><generator>Hugo -- gohugo.io</generator><language>en-gb</language><copyright>© 2026 That Bearded IT Guy</copyright><lastBuildDate>Wed, 02 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://thatbeardeditguy.co.uk/tags/jml/index.xml" rel="self" type="application/rss+xml"/><item><title>Sometimes Improving a Process Means Removing Things</title><link>https://thatbeardeditguy.co.uk/blog/sometimesimprovingaprocessmeansremovingthings/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://thatbeardeditguy.co.uk/blog/sometimesimprovingaprocessmeansremovingthings/</guid><description>Why sometimes the best way to improve an IT process is to remove the things that only add unnecessary complexity.</description></item></channel></rss>