Idea: animated documents. It starts with the core points. and if you have more reading time you move the slider and more detail appears, highlighted.
The thing is in certain fields it takes dekades to be able to do it in just 4 hours — or it takes dekades to do it at all. If you don't like that, go to your nephew and let him do it as an exercise.
It is worse the more people think "they could do it themselves" — e.g. graphic design is one of those fields where customer interaction can become absolutely exhausting if you have the bad luck of gaining the wrong customer base.
Except that in this case your clients are other developers.
The longer I work on a piece of code, the simpler, more easy to read, and less error prone it becomes. None of that work is visible in the end product.
It probably looked more impressive and complex half way through.
This engineer worked for a corporation for 40 years, and retired.
A few months into his retirement, his old company frantically calls him, begging him to come in, and help fix an issue with the system he worked on. Apparently, the new team had managed to hose it, and couldn't figure out how to fix it.
He comes in, sits down at a terminal, looks at it for five minutes, and says "Here's the issue. If you do this, it should be fixed..."
He then presents an invoice for $10,000.
The beancounters go "There's no way we can pay $10,000 for five minutes work! Itemize it!"
He sits down, scribbles a bit, and presents an invoice that says:
Time to fix bug: 5 minutes. $20
Six years of college, and forty years of experience, so I can fix a bug in five minutes: $9,980That sounds like visibility cycling in org-mode (?)