<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Figures on Aayush Bajaj's Augmenting Infrastructure</title><link>https://abaj.ai/tags/figures/</link><description>Recent content in Figures on Aayush Bajaj's Augmenting Infrastructure</description><generator>Hugo</generator><language>en</language><copyright>© 2026 Aayush Bajaj</copyright><lastBuildDate>Fri, 10 Jul 2026 08:20:25 +1000</lastBuildDate><atom:link href="https://abaj.ai/tags/figures/index.xml" rel="self" type="application/rss+xml"/><item><title>Matplotlib Library</title><link>https://abaj.ai/wiki/ccs/programming/libraries/matplotlib/</link><pubDate>Thu, 09 Jul 2026 21:02:56 +1000</pubDate><guid>https://abaj.ai/wiki/ccs/programming/libraries/matplotlib/</guid><description>&lt;p>matplotlib has a reputation for being clunky, and the reputation is earned exactly by people fighting the &lt;em>wrong&lt;/em> api. there are two: a stateful &lt;code>pyplot&lt;/code> layer that mimics matlab (&amp;ldquo;draw on whatever was touched last&amp;rdquo;), and an object-oriented core in which every visible thing is an object you hold a reference to. the second is the real library; the first is sugar for one-liners. write &lt;code>fig, ax = plt.subplots()&lt;/code> and stay in object land, and most of the clunk evaporates.&lt;span class="margin-note" data-note="official docs: https://matplotlib.org/stable/ — the &amp;#39;anatomy of a figure&amp;#39; poster there is the single best page of documentation in scientific python">
 &lt;span class="margin-note-indicator">𐃏&lt;/span>
&lt;/span>

all code on this page executed for real; figures were written to &lt;code>/tmp&lt;/code> and are described rather than embedded, with true file sizes.&lt;/p></description></item></channel></rss>