<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>IT Governance on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</title><link>https://pwsh.in/tags/it-governance/</link><description>Recent content in IT Governance on Vibhu Bhatnagar — PowerShell &amp; Infrastructure Engineer</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Sun, 12 Jul 2026 16:47:35 +0530</lastBuildDate><atom:link href="https://pwsh.in/tags/it-governance/index.xml" rel="self" type="application/rss+xml"/><item><title>Why Naming Conventions Matter for Governance and Scale</title><link>https://pwsh.in/posts/why-naming-conventions-matter/</link><pubDate>Sun, 12 Jul 2026 16:47:35 +0530</pubDate><guid>https://pwsh.in/posts/why-naming-conventions-matter/</guid><description>&lt;h2 id="the-point">The Point&lt;/h2>
&lt;p>Skip a naming standard and you don&amp;rsquo;t get &amp;ldquo;no standard&amp;rdquo; — you get one anyway: an accidental, undocumented one, invented server by server, that quietly makes audits harder and growth messier.&lt;/p>
&lt;h2 id="context">Context&lt;/h2>
&lt;p>Walk into any organization past a handful of servers and you&amp;rsquo;ll find one of two things: a naming convention nobody questions, or a graveyard of &lt;code>SERVER2&lt;/code>, &lt;code>NEWSQL&lt;/code>, &lt;code>test-final-v2&lt;/code>, &lt;code>DONOTDELETE-backup&lt;/code>. There&amp;rsquo;s no third option.&lt;/p>
&lt;p>Here&amp;rsquo;s why that convention matters more than it looks — for passing an audit, and for staying sane as the environment keeps changing — followed by the full standard, unedited, as a working reference.&lt;/p></description></item></channel></rss>