Russ also has a great blog, with the most recent entry on fast floating-point printing and parsing. I believe these performance improvements have landed in the latest version of Go.
<a href="https:&#x2F;&#x2F;research.swtch.com&#x2F;fp" rel="nofollow">https:&#x2F;&#x2F;research.swtch.com&#x2F;fp</a>

It&#x27;s available online for free: <a href="https:&#x2F;&#x2F;abseil.io&#x2F;resources&#x2F;swe-book" rel="nofollow">https:&#x2F;&#x2F;abseil.io&#x2F;resources&#x2F;swe-book</a><p>And, yep, it&#x27;s worth a read.

The book Software Engineering at Google goes into this (all factors of programming at scale &#x2F; over time), worth a read.

don&#x27;t we already have the words slop and vibecode

Then a new term is warranted for what happens to programming when we add prompts &amp; agents.

&gt; Software engineering is what happens to programming when you add time and other people.

I recently learned that Russ also wrote software for The On-Line Encyclopedia of Integer Sequences (<a href="https:&#x2F;&#x2F;oeis.org" rel="nofollow">https:&#x2F;&#x2F;oeis.org</a>) and is the president of the OEIS Foundation.

I love the &quot;Tornado&quot; term and &quot;software debt&quot;... worked with a few over the years, fixed the bug but broke the paradigm.  Well articulated wisdom.