<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>History on Derald's Workbench</title><link>https://derald.com/tags/history/</link><description>Recent content in History 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/tags/history/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></channel></rss>