<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Leadership on vnykmshr</title><link>https://blog.vnykmshr.com/writing/tags/leadership/</link><description>Recent content in Leadership on vnykmshr</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 28 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.vnykmshr.com/writing/tags/leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>The codebase heard them</title><link>https://blog.vnykmshr.com/writing/the-codebase-heard-them/</link><pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate><guid>https://blog.vnykmshr.com/writing/the-codebase-heard-them/</guid><description>&lt;p&gt;There was a dev I worked with for years, a few hours ahead of me, never met face to face, who would not say a word in any meeting we shared.&lt;/p&gt;
&lt;p&gt;Sprint planning, design discussions, retros. The PM would speak, the leads would speak, QA would speak, EM would speak. I would speak. The dev would listen, take their notes, and stay quiet. Not because they had nothing to say. While everyone else was shaping the discussion, they were a few steps ahead, working it out in their head.&lt;/p&gt;</description></item></channel></rss>