Wind back the clock to the late 1970's. Yes, there were computers in those days.
Some of my earliest billable gigs where conversions from old OS to new OS. (Specifically DOS/VSE to OS/370, now called Z/OS.) Back when a company owned exactly one computer, all of the …
This is important:
Rule One: Writing Software is Capturing Knowledge.
Consequence: Converting Software is Preserving Knowledge.
When software is revised for a new framework or operating system or database or when an algorithm is converted to a new language, then we're "converting" (or "migrating") software. We're preserving code, and preserving …
more ...Step 1. Look at the original HamCalc. Even if you aren't interested in Ham radio, it's an epic, evolving achievement in a specialized kind of engineering support. It's a repository of mountains of mathematical models, some published by the ARRL, others scattered around the internet.
Step 2. Look closely at …
more ...Some background:
I was vaguely pointed at one call in an API, via a 2-page "tutorial" that uses CURL examples. Told "Test this some more." by the guy who'd been doing some amount (none?) of hand "success path" testing via CURL. This has since morphed into "regression testing things, all …
more ...Unit testing RESTful web services is rather complex. Ideally, the services are tested in isolation before being packaged as a service.
However, sometimes people will want to test the "finished" or "integrated" web services technology stack because (I suppose) they don't trust their lower-level unit tests.
Or they don't have …
more ...It's impossible to step into the same river twice; other waters are flowing toward the sea. It's impossible to do "head-to-head" project comparisons. You can't have the same people doing the same thing with only one constraint changed. You can try to resort to having similar people doing the exact …
more ...A random list of cool things.
After spending a couple of years (really) working with a publisher, the deal has gone south.
The problem was—likely—all mine. The book wasn't really what the publisher wanted. Perhaps it was close and they thought they could edit it into shape. And perhaps I wasn't responsive enough to …
more ...Here's an object lesson in bad requirements writing.
"Good" is defined as a nice simple and intuitive GUI interface. I would be able to just pick symbol from a pallette and put it somewhere and the software would automatically adjust the spacing.
Some problems.