3 ms·
I get that all the time. In my experience, there's a huge difference between "software that works," and "software that ships." Most of my test harnesses are f
by ChrisMarshallNY 3y ago
I get that all the time.
In my experience, there's a huge difference between "software that works," and "software that ships."
Most of my test harnesses are full-fat applications. They are written in a ship fashion, but they don't have the polish and TLC that I lavish on the ship stuff.
I can write a test harness app in a day or two. It will be a fully-functional, accessible, localizable app, with a non-trivial feature set.
However, if I write something to ship, it may take a couple of months (or longer).
An example is the app I'm writing now. I wrote the "heart" library in about a month and a half. It has a test harness that runs every feature, and the test harness was the largest part of the job.
However, the ship app is coming to beta, about a year later. It knocks the test harness into a cocked hat.
- ActorNightly 3y agoThere is definitely an aspect of raw time that needs to be put into development to make a prod version of software robust, but that still doesn't account for the bloat. The real issue for the bloat is simple lack of engineering skill. Most "engineers" have very little clue of what goes on under the hood when their code is running, and really only rely on learned patterns to complete their job. So many times I have been given code for a service that when run locally doesn't work, with the explanation that you have to test it in beta stage - the reason this happens is because nobody who started writing that code has any idea of what goes on outside of the boilerplate that is provided for them to fill in.