<?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>Calyntro on Calyntro Blog</title><link>https://calyntro.com/blog/tags/calyntro/</link><description>Recent content in Calyntro on Calyntro Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 13 May 2026 08:00:00 +0200</lastBuildDate><atom:link href="https://calyntro.com/blog/tags/calyntro/index.xml" rel="self" type="application/rss+xml"/><item><title>What We Found When We Analysed MongoDB's Codebase</title><link>https://calyntro.com/blog/posts/2026-05-13-if-it-happens/</link><pubDate>Wed, 13 May 2026 08:00:00 +0200</pubDate><guid>https://calyntro.com/blog/posts/2026-05-13-if-it-happens/</guid><description>A file can look shared today but have been built entirely by someone who left last year. We ran that analysis on MongoDB — and the results are worth paying attention to.</description></item><item><title>The Invisible Risk in Your Codebase</title><link>https://calyntro.com/blog/posts/2026-04-30-invisible_risks_in_codebase/</link><pubDate>Thu, 30 Apr 2026 08:00:00 +0200</pubDate><guid>https://calyntro.com/blog/posts/2026-04-30-invisible_risks_in_codebase/</guid><description>Most teams know that critical knowledge is concentrated in a few people. Almost none know exactly where. That&amp;#39;s not a knowledge transfer problem — it&amp;#39;s a visibility problem.</description></item></channel></rss>