I see what you are talking about, but your parable has another side that no one sees - the guy learned a lot of different things in the process :) For people who enjoy learning and exploration it is the true meaning of the whole thing, not a written tune.
Yes, but it's not about the feel of the product which is definitely there, but about the skills required to design. I, personally, would never call anybody who designed his own computer whether with ATMEGA or not, a "cheater". It deserves respect, to say the least.
Well, his argument is not about the number of chips but rather component origins. If you are about to pretend that you are in the 80s and you develop a computer in that time, you've got to use what was available. I argue that ZX Spectrum used custom-made ULA and you kind of emulate that approach to design with ATMEGA and he just laughs :)
The truth is that we live in magnificent times where there's a wide range of choice on how to do things and it is amazing.
Somehow I still get those chills while reading source code of programming languages interpreters / compilers. I guess it's like getting to the origins of life, or something.
My product came out of my own pains of providing end user documentation and tech support, so how can I not recommend it? 50% off BFCM.
Here's a post that summarizes my work, at least partially: https://www.helpinator.com/blog/2019/09/18/recommended-readi...
It does not work this way since Google started to rely on behavioral metrics of content, not just keywords. Useful articles that people read and refer to frequently, go up, junk goes down. So creating articles with only aim to sell something is the sure fire way to anger people and waste your money. Content marketing nowadays is about producing quality content IN HOPE that it will help to sell your product.
I am well aware of Zeal, and it's cool for docs that people read from cover to cover. My primary objective was to not to create a new format, but rather provide means for authoring and displaying structured technical content, pretty much like DITA or DocBook, but way more simple and targeted at software (e.g. providing a context-sensitive help feature).
Epub suffers from the same flaws - only one language per file, freeform styling that makes company-wide style consistency problematic (and when we talk about a ERP system with thousands of users and a miriad supplementary tools created for it - it's a really big problem).
And it was not designed for context-sensitive help of desktop apps, while LiteHelp is.
I know at least a dozen :) Just kidding. I know a lot more. Enterprise systems tend to have so complicated business processes that a detailed help file is a must.