<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Field Notes on Derald's Workbench</title><link>https://derald.com/posts/</link><description>Recent content in Field Notes on Derald's Workbench</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 Derald R. Grimwood Jr.</copyright><lastBuildDate>Sat, 11 Jul 2026 08:00:00 -0700</lastBuildDate><atom:link href="https://derald.com/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>Old Systems, New Tools</title><link>https://derald.com/posts/old-systems-new-tools/</link><pubDate>Sat, 11 Jul 2026 08:00:00 -0700</pubDate><guid>https://derald.com/posts/old-systems-new-tools/</guid><description>&lt;p&gt;There is a difference between preserving an old idea and refusing to move forward.&lt;/p&gt;
&lt;p&gt;I do not work with xBase ideas because every old design was good. Many were limited by memory, storage, operating systems, and assumptions that no longer apply. I return to them because some of those systems were unusually direct.&lt;/p&gt;</description><content>&lt;p&gt;There is a difference between preserving an old idea and refusing to move forward.&lt;/p&gt;
&lt;p&gt;I do not work with xBase ideas because every old design was good. Many were limited by memory, storage, operating systems, and assumptions that no longer apply. I return to them because some of those systems were unusually direct.&lt;/p&gt;
&lt;p&gt;A table was visible. A record pointer had meaning. Commands were readable. A user could inspect the work rather than merely trust a hidden service.&lt;/p&gt;
&lt;h2 id="carry-the-useful-parts-forward"&gt;Carry the useful parts forward&lt;/h2&gt;
&lt;p&gt;Modern tools give us better compilers, testing, version control, continuous builds, portable libraries, graphical interfaces, and far more computing power. They also make it easy to hide a modest problem beneath a tall stack of abstractions.&lt;/p&gt;
&lt;p&gt;The useful course is neither nostalgia nor fashionable replacement. It is selection.&lt;/p&gt;
&lt;p&gt;Keep what was clear:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;understandable data structures&lt;/li&gt;
&lt;li&gt;explicit commands&lt;/li&gt;
&lt;li&gt;inspectable state&lt;/li&gt;
&lt;li&gt;durable files&lt;/li&gt;
&lt;li&gt;repeatable scripts&lt;/li&gt;
&lt;li&gt;documentation close to the work&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Replace what was limiting:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;narrow sizes and address spaces&lt;/li&gt;
&lt;li&gt;fragile global assumptions&lt;/li&gt;
&lt;li&gt;platform dependence&lt;/li&gt;
&lt;li&gt;untested behavior&lt;/li&gt;
&lt;li&gt;undocumented side effects&lt;/li&gt;
&lt;li&gt;artificial format ceilings&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="the-long-view"&gt;The long view&lt;/h2&gt;
&lt;p&gt;A good modernization project should answer two questions.&lt;/p&gt;
&lt;p&gt;First: what can the new tools do that the old system could not?&lt;/p&gt;
&lt;p&gt;Second: what did the old system make obvious that the new one is in danger of concealing?&lt;/p&gt;
&lt;p&gt;The best result respects both answers.&lt;/p&gt;</content></item><item><title>A System Should Explain Itself</title><link>https://derald.com/posts/readable-systems/</link><pubDate>Fri, 10 Jul 2026 08:00:00 -0700</pubDate><guid>https://derald.com/posts/readable-systems/</guid><description>&lt;p&gt;Documentation is often treated as a report written after the real work is finished. That arrangement almost guarantees that the report will fall behind.&lt;/p&gt;
&lt;p&gt;A system should explain itself while it is being built.&lt;/p&gt;
&lt;p&gt;That does not mean filling the source with noise or generating pages nobody reads. It means designing visible contracts:&lt;/p&gt;</description><content>&lt;p&gt;Documentation is often treated as a report written after the real work is finished. That arrangement almost guarantees that the report will fall behind.&lt;/p&gt;
&lt;p&gt;A system should explain itself while it is being built.&lt;/p&gt;
&lt;p&gt;That does not mean filling the source with noise or generating pages nobody reads. It means designing visible contracts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;commands with clear names&lt;/li&gt;
&lt;li&gt;help derived from governed catalogs&lt;/li&gt;
&lt;li&gt;runtime checks that prove behavior&lt;/li&gt;
&lt;li&gt;examples that can be executed again&lt;/li&gt;
&lt;li&gt;architecture boundaries that are stated and tested&lt;/li&gt;
&lt;li&gt;documentation linked to implementation evidence&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="teaching-exposes-weak-design"&gt;Teaching exposes weak design&lt;/h2&gt;
&lt;p&gt;A programmer can become accustomed to unexplained conventions. A student cannot. When a system is difficult to teach, the difficulty may be in the subject—but it may also be in the design.&lt;/p&gt;
&lt;p&gt;Teaching asks the questions that maintenance eventually asks:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;What is this object responsible for?&lt;/li&gt;
&lt;li&gt;Where does this state live?&lt;/li&gt;
&lt;li&gt;What happens before and after the command?&lt;/li&gt;
&lt;li&gt;Which behavior is guaranteed?&lt;/li&gt;
&lt;li&gt;How can I prove it?&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Software that can answer those questions is easier to teach, but it is also easier to maintain.&lt;/p&gt;
&lt;h2 id="evidence-is-better-than-confidence"&gt;Evidence is better than confidence&lt;/h2&gt;
&lt;p&gt;A large project accumulates confident statements. Some are true, some were true, and some describe an intention that never became implementation.&lt;/p&gt;
&lt;p&gt;Runtime evidence, repeatable tests, generated catalogs, and reviewed documentation help separate those categories.&lt;/p&gt;
&lt;p&gt;The goal is not paperwork. The goal is a system whose claims can be checked.&lt;/p&gt;</content></item><item><title>Using AI Without Surrendering the Architecture</title><link>https://derald.com/posts/ai-without-surrender/</link><pubDate>Thu, 09 Jul 2026 08:00:00 -0700</pubDate><guid>https://derald.com/posts/ai-without-surrender/</guid><description>&lt;p&gt;AI can write code quickly. That is useful, but speed is not the same as continuity.&lt;/p&gt;
&lt;p&gt;A long-running system contains decisions that may not be obvious from one file: naming rules, lifecycle contracts, compatibility requirements, test surfaces, abandoned approaches, and features that must not quietly disappear.&lt;/p&gt;</description><content>&lt;p&gt;AI can write code quickly. That is useful, but speed is not the same as continuity.&lt;/p&gt;
&lt;p&gt;A long-running system contains decisions that may not be obvious from one file: naming rules, lifecycle contracts, compatibility requirements, test surfaces, abandoned approaches, and features that must not quietly disappear.&lt;/p&gt;
&lt;p&gt;The person directing the work remains responsible for those decisions.&lt;/p&gt;
&lt;h2 id="where-ai-helps"&gt;Where AI helps&lt;/h2&gt;
&lt;p&gt;AI is effective at:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;scanning a large code surface&lt;/li&gt;
&lt;li&gt;drafting repetitive implementation&lt;/li&gt;
&lt;li&gt;comparing approaches&lt;/li&gt;
&lt;li&gt;expanding tests&lt;/li&gt;
&lt;li&gt;organizing documentation&lt;/li&gt;
&lt;li&gt;finding likely omissions&lt;/li&gt;
&lt;li&gt;translating between technical layers&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="where-direction-remains-necessary"&gt;Where direction remains necessary&lt;/h2&gt;
&lt;p&gt;AI needs firm boundaries when:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;a local simplification would remove existing behavior&lt;/li&gt;
&lt;li&gt;two components appear redundant but have different contracts&lt;/li&gt;
&lt;li&gt;a generated answer conflicts with runtime evidence&lt;/li&gt;
&lt;li&gt;a fashionable redesign would erase the project&amp;rsquo;s purpose&lt;/li&gt;
&lt;li&gt;uncertainty is being presented as fact&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="a-practical-relationship"&gt;A practical relationship&lt;/h2&gt;
&lt;p&gt;The useful model is not “AI builds the system.”&lt;/p&gt;
&lt;p&gt;It is:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;The developer holds the architecture. AI increases the developer&amp;rsquo;s reach.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;That relationship can produce better work, provided the human keeps the long view and the machine remains accountable to evidence.&lt;/p&gt;</content></item></channel></rss>