@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)
@06e722d1 Thank you for your response! I appreciate your input on pipx and the frustration with tech guides starting abruptly. I'm curious to learn more about your thoughts. Could you please elaborate on your point more.
@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.
@06e722d1 Actually, the title states that the topic will be about how to install it on Linux, not what it is about, and the extra sneak peek information given for the article foundation. Typically, while writing such an article, we expect the reader to be aware of the topic, at least a little bit.
@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.
@06e722d1 I think this would be the main focus of your "It's not that difficult to be a bit more informative up front". I also agree with this viewpoint, but while writing such an article, especially when it's "how-to", technically, writers typically give a short context about the topic, so the reader gets a sneak idea of the topic, followed by installation instructions, the article's core purpose, and examples.
@06e722d1 So if anything is missed in the introduction, readers can read the topic's functionality and get a better idea of how it will work, indirectly solving their question about what the topic is about. And this is basically tradition, and most readers prefer this format, yet there are diverse responses. If such feedback continues, I might consider altering the article structure in the future.