<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Book Review on Network Automation with David</title><link>https://dv-lunel.com/tags/book-review/</link><description>Recent content in Book Review on Network Automation with David</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0200</lastBuildDate><atom:link href="https://dv-lunel.com/tags/book-review/index.xml" rel="self" type="application/rss+xml"/><item><title>Book Review: AI Agents for Network Operations</title><link>https://dv-lunel.com/post/2026-07-27-book-review-sif/</link><pubDate>Mon, 27 Jul 2026 00:00:00 +0200</pubDate><guid>https://dv-lunel.com/post/2026-07-27-book-review-sif/</guid><description>&lt;h1 id="review-of-ai-agents-for-network-operations-by-sif-baksh"&gt;Review of &amp;ldquo;AI Agents for Network Operations&amp;rdquo; by Sif Baksh&lt;/h1&gt;
&lt;p&gt;Most network engineers don&amp;rsquo;t wake up thinking about tokens or context windows. We wake up thinking about why BGP is down, why an alert fired, and why the dashboard is green while the ticket says everything is broken.&lt;/p&gt;
&lt;p&gt;So when a book puts &amp;ldquo;AI Agents&amp;rdquo; and &amp;ldquo;Network Operations&amp;rdquo; in the same title, my first reaction is usually a quiet &amp;ldquo;here we go.&amp;rdquo; I&amp;rsquo;ve seen enough demos where AI gets bolted onto a workflow that a plain script already handled better.&lt;/p&gt;</description></item></channel></rss>