<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>The Villain's Lab (Posts about systems)</title><link>https://www.ct-unlimited.org/</link><description></description><atom:link href="https://www.ct-unlimited.org/categories/systems.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Wed, 16 Sep 2026 07:05:55 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>The Engineering Foundations Library</title><link>https://www.ct-unlimited.org/posts/engineering-foundations-library/</link><dc:creator>The Villain</dc:creator><description>&lt;div&gt;&lt;p&gt;Ok, let's talk about something that keeps annoying me.&lt;/p&gt;
&lt;p&gt;We have a lot of engineers that know tools.  They know Kubernetes, Terraform,
Argo, AWS, GitHub Actions, Prometheus, Grafana, Postgres, Redis, Kafka, and
whatever else happens to be in the stack this year.  That is fine.  Tools
matter.  The problem is that a lot of them do not understand the substrate those
tools are built on.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://www.ct-unlimited.org/posts/engineering-foundations-library/"&gt;Read more…&lt;/a&gt; (11 min remaining to read)&lt;/p&gt;&lt;/div&gt;</description><category>devops</category><category>distributed-systems</category><category>engineering</category><category>linux</category><category>networking</category><category>platform-engineering</category><category>security</category><category>sre</category><category>systems</category><guid>https://www.ct-unlimited.org/posts/engineering-foundations-library/</guid><pubDate>Wed, 08 Jul 2026 07:00:00 GMT</pubDate></item></channel></rss>