UX designers who eliminated the filesystem from user consciousness in name of simplicity ruined the world and are morally culpable for shriveling minds of children who are unable to tackle the challenges of today thanks to a choice sold as advocacy for the user but was ultimately motivated by control of a disempowered customer.
I'm shocked at the #TechIlliteracy of post-millenial #Kids despite them having easier access to #Documentation and #HowTos than I could've ever dreamed of, despite having #ISDN in 1999...
Hi there, I'm Kasiandra a Cyber-Witch-Punk from outta 'ciety. I'm not really #newhere/ #neuhier, this is my public account for publishing #Art, #photography, #Recipes, #howtos and more, mostly in German. Feel free to follow me if ya interested in this and #mastoart / #mastodonartist.
«Diátaxis insists that what matters in documentation is the needs of the user, and it’s by paying attention to this that we can correctly distinguish between tutorials and how-to guides.
Sometimes the user is at study, and sometimes the user is at work. Documentation has to serve both those needs.
A tutorial serves the needs of the user who is at study. Its obligation is to provide a successful learning experience. A how-to guide serves the needs of the user who is at work. Its obligation is to help the user accomplish a task. These are completely different needs and obligations, and they are why the distinction between tutorials and how-to guides matters: tutorials are learning-oriented, and how-to guides are task-oriented.»
Say you have a custom virtual environment named myEnv, in which you have meticulously setup an old Python version, together with some arcane packages (activated by source .myEnv/bin/activate), you must install package ipykernel to make this environment capable of interfacing with your host system Python insta