Earlier quoted context omitted.
> perhaps better saved for a blog post Please do write it, and submit it to HN! This is the sort of material nearly all of us would love to read.
It'd certainly be interesting to relate a multi-decade software project from the outside :-) I will have to talk to my father about this... and explain why folks on the internet must hear his stories. In the interim, would anyone happen to have an example of a good secondhand account of a software project? A basis or, at the least, an inspiration for how to proceed.
https://www.reddit.com/user/36055512/submitted
Start oldest first, bottom of the list, and go upwards for chronological order (identical titles are to different subs, so only comments will be different).
Last I heard a book was in the works. I'm not yet sure if it's surfaced yet, but these posts make for a good few hours' reading. They're great.
The secondary suggestion here is that finding a forum that will appreciate the posts and give feedback - note the upvotes and sheer quantity of gold - can be incredibly encouraging. This format also benefits from the fact that there are so many posts on a daily basis all the readers have plenty to keep busy with while they wait, so each writer can establish a lazy pace of writing and submitting that isn't pressured or hectic.
As for continued inspiration, https://www.reddit.com/r/talesfromtechsupport features some great technical writing. Sort by top/week or top/month to find quality examples and the latest top authors (top/all is also awesome, but changes there are months apart) - just try not to drown in the firehose of cringe-inducing idiocy reporting! xD
The idea here would be that the subreddit's sentiment is grokked, inspiration happens, and a new writer appears :D
(Stop by Reddit's TOS and overview, and do NOT skip installing Reddit Enhancement Suite if you decide you like this particular site.)
Wherever the content ends up - a subreddit like TFTS, another messageboard or forum, or a blog - definitely please do link it. :D