<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Derald's Workbench</title><link>https://derald.com/</link><description>Recent content 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/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><item><title>About</title><link>https://derald.com/about/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://derald.com/about/</guid><description>&lt;h1 id="the-long-view"&gt;The long view&lt;/h1&gt;
&lt;p&gt;I have spent much of my life around systems—military, business, educational, and technical. The best of them share a few qualities: they are understandable, dependable, disciplined, and built for people who must actually use them.&lt;/p&gt;</description><content>&lt;h1 id="the-long-view"&gt;The long view&lt;/h1&gt;
&lt;p&gt;I have spent much of my life around systems—military, business, educational, and technical. The best of them share a few qualities: they are understandable, dependable, disciplined, and built for people who must actually use them.&lt;/p&gt;
&lt;p&gt;I served in the &lt;strong&gt;U.S. Army from 1982 to 1988&lt;/strong&gt;. My later work moved through payroll and scheduling, bookstore software, FoxPro business systems, data conversion, barcode systems, semiconductor manufacturing, SAP, technical instruction, and independent development.&lt;/p&gt;
&lt;p&gt;The technologies changed. The basic questions did not:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Can a person understand what the system is doing?&lt;/li&gt;
&lt;li&gt;Can the work be checked and repeated?&lt;/li&gt;
&lt;li&gt;Does the design preserve useful knowledge?&lt;/li&gt;
&lt;li&gt;Will it still make sense to the next person?&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="a-working-timeline"&gt;A working timeline&lt;/h2&gt;
&lt;div class="timeline"&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;1982–1988&lt;/div&gt;&lt;div&gt;&lt;strong&gt;Army service.&lt;/strong&gt; Discipline, responsibility, and practical work under real constraints.&lt;/div&gt;&lt;/div&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;Around 1990&lt;/div&gt;&lt;div&gt;&lt;strong&gt;College and early professional computing.&lt;/strong&gt; Business software, payroll scheduling, COBOL, and database work.&lt;/div&gt;&lt;/div&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;1990s&lt;/div&gt;&lt;div&gt;&lt;strong&gt;xBase and FoxPro systems.&lt;/strong&gt; Cross-platform business applications, time and attendance, receivables, and data-centered software.&lt;/div&gt;&lt;/div&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;Enterprise years&lt;/div&gt;&lt;div&gt;&lt;strong&gt;Manufacturing, barcodes, conversion, SAP, and ABAP.&lt;/strong&gt; Systems attached to physical work, production, and long-lived business processes.&lt;/div&gt;&lt;/div&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;Teaching&lt;/div&gt;&lt;div&gt;&lt;strong&gt;Technical instruction.&lt;/strong&gt; Explaining programming and systems reinforced the belief that software should reveal its own structure.&lt;/div&gt;&lt;/div&gt;
&lt;div class="timeline-row"&gt;&lt;div class="timeline-date"&gt;Now&lt;/div&gt;&lt;div&gt;&lt;strong&gt;x64base and DotTalk++.&lt;/strong&gt; Revisiting the strengths of readable database systems with modern C++, cross-platform tools, documentation, and AI-assisted development.&lt;/div&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;h2 id="not-simply-nostalgia"&gt;Not simply nostalgia&lt;/h2&gt;
&lt;p&gt;I value older systems because many of them were direct. A table looked like a table. A command described an action. A programmer could follow the path from input to result.&lt;/p&gt;
&lt;p&gt;That does not mean freezing technology in the past. It means carrying forward the parts that still deserve to live: clarity, inspectability, modest dependencies, durable data, and respect for the operator.&lt;/p&gt;
&lt;h2 id="beyond-programming"&gt;Beyond programming&lt;/h2&gt;
&lt;p&gt;Photography and art provide a different kind of discipline. Technical work asks whether a system functions. Visual work asks whether we noticed what was there.&lt;/p&gt;
&lt;p&gt;This site holds both.&lt;/p&gt;</content></item><item><title>Now</title><link>https://derald.com/now/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://derald.com/now/</guid><description>&lt;h1 id="now"&gt;Now&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Last reviewed: November 2026.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="building"&gt;Building&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Stabilizing and extending &lt;strong&gt;x64base&lt;/strong&gt; and the &lt;strong&gt;DotTalk++&lt;/strong&gt; runtime&lt;/li&gt;
&lt;li&gt;Keeping DBF, memo, indexing, relation, tuple, constraint, and scripting work orthogonal&lt;/li&gt;
&lt;li&gt;Developing parallel TUI, wxWidgets, and Python-facing user-interface surfaces&lt;/li&gt;
&lt;li&gt;Improving the project&amp;rsquo;s self-documentation and evidence systems&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="studying"&gt;Studying&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Business Management with an MIS minor at &lt;a href="./northwood/"&gt;Northwood University&lt;/a&gt;, starting with MIS 3250, ERP Business Applications (SAP S/4HANA)&lt;/li&gt;
&lt;li&gt;Modern enterprise systems and SAP education paths&lt;/li&gt;
&lt;li&gt;Better ways to teach database and programming concepts&lt;/li&gt;
&lt;li&gt;Practical uses of AI in long-running software development&lt;/li&gt;
&lt;li&gt;The history of systems whose useful ideas should not be discarded&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="publishing"&gt;Publishing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://x64base.com/"&gt;x64base.com&lt;/a&gt; as the project and ecosystem entrance&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dottalkpp.com/"&gt;dottalkpp.com&lt;/a&gt; as the technical artifact room&lt;/li&gt;
&lt;li&gt;&lt;a href="https://grimwood.family/"&gt;grimwood.family&lt;/a&gt; as the family site&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;derald.com&lt;/strong&gt; as the personal workbench and field journal&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="principle-for-the-season"&gt;Principle for the season&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Use new tools without surrendering the long view.&lt;/p&gt;</description><content>&lt;h1 id="now"&gt;Now&lt;/h1&gt;
&lt;p&gt;&lt;em&gt;Last reviewed: November 2026.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="building"&gt;Building&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Stabilizing and extending &lt;strong&gt;x64base&lt;/strong&gt; and the &lt;strong&gt;DotTalk++&lt;/strong&gt; runtime&lt;/li&gt;
&lt;li&gt;Keeping DBF, memo, indexing, relation, tuple, constraint, and scripting work orthogonal&lt;/li&gt;
&lt;li&gt;Developing parallel TUI, wxWidgets, and Python-facing user-interface surfaces&lt;/li&gt;
&lt;li&gt;Improving the project&amp;rsquo;s self-documentation and evidence systems&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="studying"&gt;Studying&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Business Management with an MIS minor at &lt;a href="./northwood/"&gt;Northwood University&lt;/a&gt;, starting with MIS 3250, ERP Business Applications (SAP S/4HANA)&lt;/li&gt;
&lt;li&gt;Modern enterprise systems and SAP education paths&lt;/li&gt;
&lt;li&gt;Better ways to teach database and programming concepts&lt;/li&gt;
&lt;li&gt;Practical uses of AI in long-running software development&lt;/li&gt;
&lt;li&gt;The history of systems whose useful ideas should not be discarded&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="publishing"&gt;Publishing&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://x64base.com/"&gt;x64base.com&lt;/a&gt; as the project and ecosystem entrance&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dottalkpp.com/"&gt;dottalkpp.com&lt;/a&gt; as the technical artifact room&lt;/li&gt;
&lt;li&gt;&lt;a href="https://grimwood.family/"&gt;grimwood.family&lt;/a&gt; as the family site&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;derald.com&lt;/strong&gt; as the personal workbench and field journal&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="principle-for-the-season"&gt;Principle for the season&lt;/h2&gt;
&lt;blockquote&gt;
&lt;p&gt;Use new tools without surrendering the long view.&lt;/p&gt;
&lt;/blockquote&gt;</content></item><item><title>Photography</title><link>https://derald.com/photography/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://derald.com/photography/</guid><description>&lt;h1 id="photography-and-visual-work"&gt;Photography and visual work&lt;/h1&gt;
&lt;p&gt;Programming trains the mind to follow structure. Photography trains the eye to notice structure before it disappears.&lt;/p&gt;
&lt;p&gt;This section will hold selected photographs, older work, visual experiments, and notes about seeing. It is intentionally separate from the technical project sites.&lt;/p&gt;</description><content>&lt;h1 id="photography-and-visual-work"&gt;Photography and visual work&lt;/h1&gt;
&lt;p&gt;Programming trains the mind to follow structure. Photography trains the eye to notice structure before it disappears.&lt;/p&gt;
&lt;p&gt;This section will hold selected photographs, older work, visual experiments, and notes about seeing. It is intentionally separate from the technical project sites.&lt;/p&gt;
&lt;h2 id="planned-collections"&gt;Planned collections&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Places and landscapes&lt;/li&gt;
&lt;li&gt;Family and history&lt;/li&gt;
&lt;li&gt;Working objects and old machinery&lt;/li&gt;
&lt;li&gt;Architecture and geometry&lt;/li&gt;
&lt;li&gt;Retro-computing visual studies&lt;/li&gt;
&lt;li&gt;Selected artwork and experiments&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;For now, this is the prepared gallery entrance. Add image galleries here as the photographs are selected and organized.&lt;/p&gt;</content></item><item><title>Sites</title><link>https://derald.com/sites/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://derald.com/sites/</guid><description>&lt;h1 id="site-directory"&gt;Site directory&lt;/h1&gt;
&lt;h2 id="grimwoodfamily"&gt;&lt;a href="https://grimwood.family/"&gt;grimwood.family&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The family home: family history, photographs, records, and material that belongs together under the Grimwood name.&lt;/p&gt;
&lt;h2 id="x64basecom"&gt;&lt;a href="https://x64base.com/"&gt;x64base.com&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The polished public entrance to x64base, its architecture, product family, documentation, research context, and educational direction.&lt;/p&gt;</description><content>&lt;h1 id="site-directory"&gt;Site directory&lt;/h1&gt;
&lt;h2 id="grimwoodfamily"&gt;&lt;a href="https://grimwood.family/"&gt;grimwood.family&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The family home: family history, photographs, records, and material that belongs together under the Grimwood name.&lt;/p&gt;
&lt;h2 id="x64basecom"&gt;&lt;a href="https://x64base.com/"&gt;x64base.com&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The polished public entrance to x64base, its architecture, product family, documentation, research context, and educational direction.&lt;/p&gt;
&lt;h2 id="dottalkppcom"&gt;&lt;a href="https://dottalkpp.com/"&gt;dottalkpp.com&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The technical artifact room: manuals, generated references, proof packets, downloads, governance notes, and supporting material for DotTalk++ and x64base.&lt;/p&gt;
&lt;h2 id="github--deraldg"&gt;&lt;a href="https://github.com/deraldg/"&gt;GitHub / deraldg&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;The source workshop: repositories, active construction, history, experiments, and project evidence.&lt;/p&gt;
&lt;h2 id="deraldcom"&gt;derald.com&lt;/h2&gt;
&lt;p&gt;This site is the personal front door. It is about the person behind the projects: service, systems, teaching, visual work, memories, and current field notes.&lt;/p&gt;</content></item><item><title>Work</title><link>https://derald.com/work/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://derald.com/work/</guid><description>&lt;h1 id="work"&gt;Work&lt;/h1&gt;
&lt;p&gt;My current work joins classic database ideas with modern C++ development, documentation, education, and multiple user-interface surfaces.&lt;/p&gt;
&lt;h2 id="x64base"&gt;x64base&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://x64base.com/"&gt;x64base&lt;/a&gt; is an open, cross-platform database architecture in the xBase lineage. It explores 64-bit table structures, memo storage, indexing, work areas, constraints, relations, APIs, and educational tooling.&lt;/p&gt;</description><content>&lt;h1 id="work"&gt;Work&lt;/h1&gt;
&lt;p&gt;My current work joins classic database ideas with modern C++ development, documentation, education, and multiple user-interface surfaces.&lt;/p&gt;
&lt;h2 id="x64base"&gt;x64base&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://x64base.com/"&gt;x64base&lt;/a&gt; is an open, cross-platform database architecture in the xBase lineage. It explores 64-bit table structures, memo storage, indexing, work areas, constraints, relations, APIs, and educational tooling.&lt;/p&gt;
&lt;p&gt;The project is deliberately developed alongside its documentation. Runtime evidence, manuals, source structure, and teaching material are treated as parts of the system rather than as an afterthought.&lt;/p&gt;
&lt;h2 id="dottalk"&gt;DotTalk++&lt;/h2&gt;
&lt;p&gt;&lt;a href="https://dottalkpp.com/"&gt;DotTalk++&lt;/a&gt; is the readable command and scripting environment around the database work. It includes the CLI, DotScript automation, tuple and relation tools, validation surfaces, documentation systems, and experiments in TUI, GUI, and Python integration.&lt;/p&gt;
&lt;h2 id="technical-background"&gt;Technical background&lt;/h2&gt;
&lt;p&gt;My experience includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;COBOL payroll and scheduling systems&lt;/li&gt;
&lt;li&gt;xBase, FoxPro, DBF-centered business applications&lt;/li&gt;
&lt;li&gt;data conversion and migration&lt;/li&gt;
&lt;li&gt;barcode and manufacturing systems&lt;/li&gt;
&lt;li&gt;SAP and ABAP&lt;/li&gt;
&lt;li&gt;SQL and enterprise data&lt;/li&gt;
&lt;li&gt;Unix and Linux systems&lt;/li&gt;
&lt;li&gt;C and modern C++&lt;/li&gt;
&lt;li&gt;technical instruction&lt;/li&gt;
&lt;li&gt;cross-platform and command-driven development&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="working-principles"&gt;Working principles&lt;/h2&gt;
&lt;h3 id="the-operator-matters"&gt;The operator matters&lt;/h3&gt;
&lt;p&gt;A system is not complete merely because the internal code is elegant. It must make sense to the person using it, maintaining it, teaching it, or repairing it.&lt;/p&gt;
&lt;h3 id="documentation-belongs-near-the-implementation"&gt;Documentation belongs near the implementation&lt;/h3&gt;
&lt;p&gt;When documentation is postponed, it becomes archaeology. I prefer systems that can describe and verify themselves while they are being built.&lt;/p&gt;
&lt;h3 id="old-ideas-can-remain-useful"&gt;Old ideas can remain useful&lt;/h3&gt;
&lt;p&gt;DBF-style tables, command environments, explicit work areas, and scriptable workflows are not automatically obsolete. They may still offer clarity when rebuilt without pretending that modern requirements do not exist.&lt;/p&gt;
&lt;h3 id="ai-is-an-assistant-not-the-architect"&gt;AI is an assistant, not the architect&lt;/h3&gt;
&lt;p&gt;AI can accelerate research, coding, documentation, and testing. Architectural responsibility still belongs to the person directing the work.&lt;/p&gt;</content></item></channel></rss>