<?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>Engineering-Leadership on Calyntro Blog</title><link>https://calyntro.com/blog/tags/engineering-leadership/</link><description>Recent content in Engineering-Leadership on Calyntro Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 20 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://calyntro.com/blog/tags/engineering-leadership/index.xml" rel="self" type="application/rss+xml"/><item><title>The Review Is Too Late</title><link>https://calyntro.com/blog/posts/2026-05-20-the_review_is_too_late/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://calyntro.com/blog/posts/2026-05-20-the_review_is_too_late/</guid><description>Everyone is optimising the code review. But the review isn&amp;#39;t where quality gets decided — it&amp;#39;s where quality gets caught. In the age of AI-generated code, that distinction matters more than ever.</description></item></channel></rss>