https://vacua.dev/tags/rewrites/Recent content in Rewrites on Brian FaustHugoen-USMon, 01 Jan 0001 00:00:00 +0000https://vacua.dev/thoughts/a-rewrite-needs-a-behavior-ledger/Wed, 01 May 2019 00:00:00 +0000https://vacua.dev/thoughts/a-rewrite-needs-a-behavior-ledger/<p>A desktop rewrite had screens for shipments, reports, settings, and logs. A feature checklist could have marked those areas complete.</p> <p>The old application also had behavior no screen list would reveal:</p> <ul> <li>a failed temporary-file cleanup must not turn a submitted print into a failure, or the next run may print the label again;</li> <li>the first run treats older unprinted records differently from later runs;</li> <li>setup unlocks when a credential setting exists, not when its value is non-empty; and</li> <li>a visible report search box does nothing.</li> </ul> <p>Some of those rules protect operators. One is an awkward contract. One is probably a dead feature. A rewrite cannot treat them all as “parity.”</p>