<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Shemar Marks — Insights</title><link>https://shemarmarks.com/insights/</link><description>Practical infrastructure, Linux, and automation notes.</description><language>en</language><atom:link href="https://shemarmarks.com/rss.xml" rel="self" type="application/rss+xml"/><item><title>A backup is not a recovery plan</title><link>https://shemarmarks.com/insights/a-backup-is-not-a-recovery-plan/</link><guid>https://shemarmarks.com/insights/a-backup-is-not-a-recovery-plan/</guid><description>A successful backup job is one check. A working application after a failure is a different one. Here is how to connect them.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Every automation needs a failure path</title><link>https://shemarmarks.com/insights/automations-need-a-failure-path/</link><guid>https://shemarmarks.com/insights/automations-need-a-failure-path/</guid><description>A workflow is only useful if you can tell what happened, retry safely, and recover when a dependency is unavailable.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate></item><item><title>Linux hardening starts with a baseline</title><link>https://shemarmarks.com/insights/linux-hardening-start-with-a-baseline/</link><guid>https://shemarmarks.com/insights/linux-hardening-start-with-a-baseline/</guid><description>Before changing SSH, permissions, or firewall rules, understand what the host needs to do—and how you will get back in.</description><pubDate>Mon, 19 Oct 2026 00:00:00 GMT</pubDate></item></channel></rss>