<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Code-Review on Girish Shekhar</title><link>https://blog.girishshekhar.com/tags/code-review/</link><description>Recent content in Code-Review on Girish Shekhar</description><generator>Hugo -- 0.163.3</generator><language>en-us</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.girishshekhar.com/tags/code-review/index.xml" rel="self" type="application/rss+xml"/><item><title>The Principal Engineer's Inversion</title><link>https://blog.girishshekhar.com/posts/pe-role-inversion/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://blog.girishshekhar.com/posts/pe-role-inversion/</guid><description>The Principal Engineer is back at the keyboard, but the keyboard now operates fleets. Review has become the binding constraint, and the work has moved up a layer — from reviewing artifacts to authoring the criteria against which artifacts get reviewed. Notes on what that looks like in practice, and on the longer discipline that I think now defines the seat.</description></item></channel></rss>