Comment

Comment on I'm guilty of not reading the f..ing documentation

In my experience, all the Linux documentation I have read has been written for peers of Linux developers, who are familiar with technical terminology and several concepts and steps are left out and implied rather than explained.

It’s a way for developers to ensure that Linux never receives adoption past other developers. Literary equivalent of pulling the ladder up.

source

Sort:hotnew top

gamermanh@lemmy.dbzer0.com ⁨1⁩ ⁨week⁩ ago

who are familiar with technical terminology and several concepts and steps are left out and implied rather than explained.

Said it before and I’ll say it again: had to manually install some software to make Steam tinker launch work, and the instructions for installing it were to download and prepare the GitHub folder, then “do the usual and move the completed file to …”

Ive used git in the past and it still took me multiple minutes to figure out they meant the “make && build” command. Why was that so hard to fucking write??

source
- PerogiBoi@lemmy.ca ⁨1⁩ ⁨week⁩ ago
  Highly specialized people live in bubbles and assume that everyone else lives in their same bubble and so if someone else doesn’t understand, they aren’t worth communicating with.
  
  source
  - OriginalUsername7@lemmy.world ⁨1⁩ ⁨week⁩ ago
    XKCD 2501, basically.
    
    source
    PerogiBoi@lemmy.ca ⁨1⁩ ⁨week⁩ ago
    Thank you for this. It’s beautiful.
    
    source
Xanza@lemm.ee ⁨1⁩ ⁨week⁩ ago
I mean, it’s technical documentation. There’s a limit to how exciting it can be. lol.

source