@cazabon the language the silly uses in and of itself isn’t as much an issue to me as much as the lack of OS support beyond running.
To use any of that with other applications or processes is far more complicated than it should be because god knows none of that things maintainers will never implement PowerShell or OSA.
So to build a workflow that uses non-g-imp apps, you’re building a rather massive thing in multiple languages.
> programming new editing commands was so convenient that even the secretaries in his [Bernie Greenberg] office started learning how to use it. They used a manual someone had written which showed how to extend Emacs, but didn't say it was a programming. So the secretaries, who believed they couldn't do programming, weren't scared off. They read the manual, discovered they could do useful things and they learned to program.
#Technical#documentation is too often written by the engineers/etc who built the system being documented. Most of what a normal person first exposed to the system would need to know to make sense of it is so #obvious to them they don't even think about it.
I do my best to try to get into users' headspace when writing docs. But there's something to be said for having a dedicated technical #writer who can be that typical user and document what end users actually need.
@cazabon@pborenstein There can also be a temptation to describe something as “simple” because that’s how we want it to be perceived by readers, even though we all know that’s ineffective at best and alienating at worst.
Add comment