<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nasir Qureshi on foojay.io - Friends of OpenJDK</title><link>https://foojayio.github.io/website/today/author/nasir-qureshi/</link><description>Articles written by Nasir Qureshi on foojay.io - Friends of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Tue, 17 Feb 2026 15:33:56 +0000</lastBuildDate><atom:link href="https://foojayio.github.io/website/today/author/nasir-qureshi/index.xml" rel="self" type="application/rss+xml"/><item><title>Optimizing the MongoDB Java Driver</title><link>https://foojayio.github.io/website/today/optimizing-the-mongodb-java-driver-how-minor-optimizations-led-to-macro-gains/</link><pubDate>Tue, 17 Feb 2026 15:33:56 +0000</pubDate><guid>https://foojayio.github.io/website/today/optimizing-the-mongodb-java-driver-how-minor-optimizations-led-to-macro-gains/</guid><description>&lt;p&gt;Co-authored by &lt;em&gt;Slav Babanin&lt;/em&gt;.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www-cs-faculty.stanford.edu/~knuth/" target="_blank" rel="noopener noreferrer"&gt;Donald Knuth&lt;/a&gt;
{#https://www-cs-faculty.stanford.edu/~knuth/}, widely recognized as the &amp;lsquo;father of the analysis of algorithms,&amp;rsquo; warned against premature optimization&amp;mdash;spending effort on code that appears inefficient but is not on the critical path. He observed that programmers often focus on the wrong 97% of the codebase. Real performance gains come from identifying and optimizing the critical 3%. But, how can you identify the critical 3%? Well, that&amp;rsquo;s where the philosophy of &amp;rsquo;never guess, always measure&amp;rsquo; comes in.&lt;/p&gt;</description></item></channel></rss>