3 ms·
I’ve been writing ship software, for my entire career. Most times, I’ve been quite involved in the entire process; from napkin sketch to shrinkwrap. For me, it
by ChrisMarshallNY 3y ago
I’ve been writing ship software, for my entire career. Most times, I’ve been quite involved in the entire process; from napkin sketch to shrinkwrap.
For me, it is quite gratifying to ship, but for many people, the 50% (or more) of shipping software that is non-coding work, isn’t fun, and is usually deprecated, during the planning process.
Examples are things like end-user documentation (not just maintenance docs), training, error handling, accessibility, localization (a huge task), continuing customer support, legal checklists, patent searches, copyright searches, branding strategies, glossaries, distribution channels, evangelists, usage feedback support, synchronization between all of the above, and the Web site, etc.
Big fat, not-fun pain, but needs to be done. A lot of this stuff really needs to be considered before the first line of code is written, and the journey can take years.
The app I’m working on has been in development for over two years (but to be fair, I did “wipe the slate,” and restart, after about a year). The basic “business logic” is in one SDK that I wrote in about a month and a half. All the rest of the work has been chrome.
- Chris2048 3y agosee https://www.marktarver.com/bipolar.html https://www.marktarver.com/bipolar.html
- ChrisMarshallNY 3y agoThat's a great read!