@02439a38@8388665a With respect, that's profoundly wrong (being polite). Female scientists with children find it immensely difficult to compete for jobs, grants, promotion and recognition, because of the disproportionate burden of child rearing that is borne by women.
Just do a search on "female scientists discrimination".
@d028a7b1 How hard would it be to write something contextual
"Python user? Here's how you can install pipx (brief explanation of benefit / purpose)"
It should not be necessary to read most of an article to find out what it's about.
Let's leave it there. Thanks.
@d028a7b1 As indicated, I knew nothing about pipx. The problem of tech writers presuming familiarity with the topic and dispensing with the courtesy of a summary up front and plunging into detail is one of the reasons for the TL;DR meme's manifestations.
It's not that difficult to be a bit more informative up front.
@d028a7b1 The point was I had no idea what pipx was. Often, having opened a link to see if I need to read further, I find the article BEGINS w an explanation of what the subject is about and it matters / why the reader might want to know. If unpersuaded / topic isn't relevant the reader can leave right away. Now read the article from the perspective of someone who doesn't know what pipx is. Geddit?
Thanks for the constructive engagement. I hope the feedback is useful.
@d028a7b1
Pipx: typically used when you want to install Python programs that you intend to run as command-line tools, keeping them separate from your main Python environment and other projects.
Tldr or Read Most Of This To Find Out?
Remarkable how many HOW TO things written by tech people start with How, forcing the reader to wonder WTF is this about and WHY?; do I need to know / bookmark?
Ironic. (given Tldr idea)
Notes by 2fa1d787 | export