<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Engineering-Leadership on Brian Faust</title><link>https://vacua.dev/tags/engineering-leadership/</link><description>Recent content in Engineering-Leadership on Brian Faust</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate><atom:link href="https://vacua.dev/tags/engineering-leadership/rss.xml" rel="self" type="application/rss+xml"/><item><title>Quality Needs a Risk and Capacity Budget</title><link>https://vacua.dev/quality-needs-a-risk-and-capacity-budget/</link><pubDate>Wed, 01 Apr 2026 00:00:00 +0000</pubDate><guid>https://vacua.dev/quality-needs-a-risk-and-capacity-budget/</guid><description>&lt;p&gt;An API change took about eight hours to release and another sixty hours to
repair properly after it kept causing trouble.&lt;/p&gt;
&lt;p&gt;The API was an active legacy system already associated with recurring defects,
service interruptions, unreliable tests, difficult tooling, and delivery
estimates which could miss by a factor of four or five. We still added work in
a known performance-sensitive area because a customer or partnership needed it
now.&lt;/p&gt;
&lt;p&gt;The commercial logic was sound. The company existed to sell, acquire customers,
and make money. The immediate value was legible. A failure six months away,
conditional on traffic continuing to grow, was not.&lt;/p&gt;</description></item><item><title>Choose a Stack from Constraints, Not Identity</title><link>https://vacua.dev/choose-a-stack-from-constraints-not-identity/</link><pubDate>Sun, 01 Mar 2026 00:00:00 +0000</pubDate><guid>https://vacua.dev/choose-a-stack-from-constraints-not-identity/</guid><description>&lt;p&gt;We did not replace Laravel because Go was fashionable. We replaced it because
CPU had become the limiting resource under concurrent inbound traffic, and the
Laravel services had reached the point where more framework tuning no longer
changed that fact.&lt;/p&gt;
&lt;p&gt;After the migration, CPU use fell by almost 60 percent. The average endpoint
became sixteen times faster while the services handled forty times as much
traffic. We moved from machines with 16 CPU cores and 32 GB of memory to four
cores and 16 GB. Infrastructure cost halved. Incidents fell.&lt;/p&gt;</description></item><item><title>A Decision Record Needs a Way Back</title><link>https://vacua.dev/a-decision-record-needs-a-way-back/</link><pubDate>Sun, 01 Feb 2026 00:00:00 +0000</pubDate><guid>https://vacua.dev/a-decision-record-needs-a-way-back/</guid><description>&lt;p&gt;The incident review finds &lt;code&gt;ADR-003: Use Redis for caching&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Redis is in the configuration. The record has successfully preserved the one
fact the repository already reveals and lost everything the operator needs:
what problem the cache solved, why the database was insufficient, which failure
the team accepted, and when removing Redis would be safer than repairing it.&lt;/p&gt;
&lt;p&gt;A longer document would not necessarily help. It could spend six pages
describing Redis and still omit the choice.&lt;/p&gt;</description></item><item><title>Boundaries Follow Work Without Becoming Destiny</title><link>https://vacua.dev/boundaries-follow-work-without-becoming-destiny/</link><pubDate>Tue, 01 Oct 2024 00:00:00 +0000</pubDate><guid>https://vacua.dev/boundaries-follow-work-without-becoming-destiny/</guid><description>&lt;p&gt;We had a small team, so every service was officially owned by everyone. In
practice, a developer could finish five hours of work in a specialist
application and then spend three weeks integrating and testing it against the
legacy API.&lt;/p&gt;
&lt;p&gt;The delay was not a queue in front of another team. There was no other team. It
came from a system which had evolved across years, changing commercial
priorities, agencies, freelancers, and eventually an internal development
team. Each period left decisions which made sense under its own pressure. Their
combined cost appeared in the next change.&lt;/p&gt;</description></item></channel></rss>