As someone with a broad database development background, but with little experience shipping "software" I totally agree with the sentiment of the article. A wor

As someone with a broad database development background, but with little experience shipping "software" I totally agree with the sentiment of the article. A working prototype can be as simple a handful of shell scripts that write simulation data, and that process it in the form of the primary use-cases. Iterate the core functionality from there before jumping into the more advanced engineering part(?) I cringed on this part, as perhaps an all-too-common software QA scenario: > It came down to trying to create a fake customer, with a fake order, with a fake item, with a fake item category, with a "paid" invoice, with exceptions sprinkled throughout the codebase to handle all of these special cases and probably more that I no longer remember.