>
Reading the datasheets and documentation of the stuff you work with is an important characteristic of an capable engineer.I completely agree with this statement, but that doesn't nullify the value of "how to use x" articles. Man-pages are great because:
- they're (mostly) ubiquitous
- they're plaintext, meaning their format is more robust and accessible (e.g. I can read man over SSH without ever encountering issues)
and these are great pros, but in certain relevant aspects they're grossly inferior to articles like this:
- man-pages must be exhaustive, and thus don't have the luxury of focusing on the most common use-cases up front. These are often relegated to the "Examples" section only, or omitted altogether
- screenshots. Even for terminal apps, screenshots are incredibly helpful, and in this particular article they're also used to demonstrate the use of applications your SSH connection will interact with (e.g. browser proxy/network settings)
- (related to the above) contextual information that would otherwise be off-topic/inappropriate in a man-page. How-to articles can cover multiple apps that interact with eachother as one topic; i.e. a how-to article can focus on a use case rather than a single app.