โฒ 799 โผ What self hosting feels like (It's painful, please help ๐ฅฒ) (feddit.uk) submitted 2 years ago by Flax_vert@feddit.uk to c/selfhosted@lemmy.world 192 comments fedilink hide all child comments
[โ] teft@lemmy.world 84 points 2 years ago (1 child) This is why Technical Writer is a full time job. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 64 points 2 years ago (4 children) It's also why the humanities are important. Stemlords who brag about not doing literature classes write terrible documentation. permalink fedilink source parent hideshow 8 child comments replies: [โ] AlexWIWA@lemmy.ml 33 points 2 years ago (1 child) My CS major required me to take two upper division English classes and I think they helped me more in my career than my upper division CS classes. People forget that documentation is for ourselves too permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 13 points 2 years ago (1 child) I'm really thankful that I had a great English teacher in high school, and that my degree required a technical writing class. Being able to write a coherent email got me further in my career than the technical stuff I learned in college. permalink fedilink source parent hideshow 2 child comments replies: [โ] AlexWIWA@lemmy.ml 5 points 2 years ago I completely agree. Most peer feedbacks that I get mention my documentation. It has helped me so much permalink fedilink source parent [โ] floofloof@lemmy.ca 13 points 2 years ago (2 children) I think this is why the "my code documents itself" attitude appeals, even though it's almost never enough. Most developers just can't write, nor do they want to. permalink fedilink source parent hideshow 4 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 6 points 2 years ago The problem with "It's self-documenting" is that there are inevitably questions about what it says, and there's no additional resources to pull from. permalink fedilink source parent [โ] JackbyDev@programming.dev 1 point 2 years ago "my code documents itself" and "no, our CI system doesn't upload the source jars to Artifactory, why?" permalink fedilink source parent [โ] HK65@sopuli.xyz 3 points 2 years ago (1 child) Maybe, just maybe, people have different strengths and weaknesses and cooperating around our differences is what makes us succeed. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 15 points 2 years ago (3 children) If you know your weakness is writing documentation, please hire a technical writer. permalink fedilink source parent hideshow 6 child comments replies: [โ] HK65@sopuli.xyz 12 points 2 years ago (1 child) That's exactly what I'm saying, sorry if it came across somehow askew. My point was there is no point in competing over whose job is "better", we should be working together. permalink fedilink source parent hideshow 2 child comments replies: [โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent [โ] RobotToaster@mander.xyz 5 points 2 years ago* (1 child) Most open source projects rely on volunteers, and few technical writers volunteer. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent [โ] GBU_28@lemm.ee -2 points 2 years ago If the documentation is sufficient for the intended audience, it's good enough. permalink fedilink source parent [โ] Tja@programming.dev -1 points 2 years ago (1 child) Humanities are very important. Robots are not yet capable of flipping burgers! permalink fedilink source parent hideshow 2 child comments replies: [โ] Natanael@slrpnk.net 3 points 2 years ago Robots can definitely flip burgers. Some can even do it twice! permalink fedilink source parent
[โ] Semi_Hemi_Demigod@lemmy.world 64 points 2 years ago (4 children) It's also why the humanities are important. Stemlords who brag about not doing literature classes write terrible documentation. permalink fedilink source parent hideshow 8 child comments replies: [โ] AlexWIWA@lemmy.ml 33 points 2 years ago (1 child) My CS major required me to take two upper division English classes and I think they helped me more in my career than my upper division CS classes. People forget that documentation is for ourselves too permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 13 points 2 years ago (1 child) I'm really thankful that I had a great English teacher in high school, and that my degree required a technical writing class. Being able to write a coherent email got me further in my career than the technical stuff I learned in college. permalink fedilink source parent hideshow 2 child comments replies: [โ] AlexWIWA@lemmy.ml 5 points 2 years ago I completely agree. Most peer feedbacks that I get mention my documentation. It has helped me so much permalink fedilink source parent [โ] floofloof@lemmy.ca 13 points 2 years ago (2 children) I think this is why the "my code documents itself" attitude appeals, even though it's almost never enough. Most developers just can't write, nor do they want to. permalink fedilink source parent hideshow 4 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 6 points 2 years ago The problem with "It's self-documenting" is that there are inevitably questions about what it says, and there's no additional resources to pull from. permalink fedilink source parent [โ] JackbyDev@programming.dev 1 point 2 years ago "my code documents itself" and "no, our CI system doesn't upload the source jars to Artifactory, why?" permalink fedilink source parent [โ] HK65@sopuli.xyz 3 points 2 years ago (1 child) Maybe, just maybe, people have different strengths and weaknesses and cooperating around our differences is what makes us succeed. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 15 points 2 years ago (3 children) If you know your weakness is writing documentation, please hire a technical writer. permalink fedilink source parent hideshow 6 child comments replies: [โ] HK65@sopuli.xyz 12 points 2 years ago (1 child) That's exactly what I'm saying, sorry if it came across somehow askew. My point was there is no point in competing over whose job is "better", we should be working together. permalink fedilink source parent hideshow 2 child comments replies: [โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent [โ] RobotToaster@mander.xyz 5 points 2 years ago* (1 child) Most open source projects rely on volunteers, and few technical writers volunteer. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent [โ] GBU_28@lemm.ee -2 points 2 years ago If the documentation is sufficient for the intended audience, it's good enough. permalink fedilink source parent [โ] Tja@programming.dev -1 points 2 years ago (1 child) Humanities are very important. Robots are not yet capable of flipping burgers! permalink fedilink source parent hideshow 2 child comments replies: [โ] Natanael@slrpnk.net 3 points 2 years ago Robots can definitely flip burgers. Some can even do it twice! permalink fedilink source parent
[โ] AlexWIWA@lemmy.ml 33 points 2 years ago (1 child) My CS major required me to take two upper division English classes and I think they helped me more in my career than my upper division CS classes. People forget that documentation is for ourselves too permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 13 points 2 years ago (1 child) I'm really thankful that I had a great English teacher in high school, and that my degree required a technical writing class. Being able to write a coherent email got me further in my career than the technical stuff I learned in college. permalink fedilink source parent hideshow 2 child comments replies: [โ] AlexWIWA@lemmy.ml 5 points 2 years ago I completely agree. Most peer feedbacks that I get mention my documentation. It has helped me so much permalink fedilink source parent
[โ] Semi_Hemi_Demigod@lemmy.world 13 points 2 years ago (1 child) I'm really thankful that I had a great English teacher in high school, and that my degree required a technical writing class. Being able to write a coherent email got me further in my career than the technical stuff I learned in college. permalink fedilink source parent hideshow 2 child comments replies: [โ] AlexWIWA@lemmy.ml 5 points 2 years ago I completely agree. Most peer feedbacks that I get mention my documentation. It has helped me so much permalink fedilink source parent
[โ] AlexWIWA@lemmy.ml 5 points 2 years ago I completely agree. Most peer feedbacks that I get mention my documentation. It has helped me so much permalink fedilink source parent
[โ] floofloof@lemmy.ca 13 points 2 years ago (2 children) I think this is why the "my code documents itself" attitude appeals, even though it's almost never enough. Most developers just can't write, nor do they want to. permalink fedilink source parent hideshow 4 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 6 points 2 years ago The problem with "It's self-documenting" is that there are inevitably questions about what it says, and there's no additional resources to pull from. permalink fedilink source parent [โ] JackbyDev@programming.dev 1 point 2 years ago "my code documents itself" and "no, our CI system doesn't upload the source jars to Artifactory, why?" permalink fedilink source parent
[โ] Semi_Hemi_Demigod@lemmy.world 6 points 2 years ago The problem with "It's self-documenting" is that there are inevitably questions about what it says, and there's no additional resources to pull from. permalink fedilink source parent
[โ] JackbyDev@programming.dev 1 point 2 years ago "my code documents itself" and "no, our CI system doesn't upload the source jars to Artifactory, why?" permalink fedilink source parent
[โ] HK65@sopuli.xyz 3 points 2 years ago (1 child) Maybe, just maybe, people have different strengths and weaknesses and cooperating around our differences is what makes us succeed. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 15 points 2 years ago (3 children) If you know your weakness is writing documentation, please hire a technical writer. permalink fedilink source parent hideshow 6 child comments replies: [โ] HK65@sopuli.xyz 12 points 2 years ago (1 child) That's exactly what I'm saying, sorry if it came across somehow askew. My point was there is no point in competing over whose job is "better", we should be working together. permalink fedilink source parent hideshow 2 child comments replies: [โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent [โ] RobotToaster@mander.xyz 5 points 2 years ago* (1 child) Most open source projects rely on volunteers, and few technical writers volunteer. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent [โ] GBU_28@lemm.ee -2 points 2 years ago If the documentation is sufficient for the intended audience, it's good enough. permalink fedilink source parent
[โ] Semi_Hemi_Demigod@lemmy.world 15 points 2 years ago (3 children) If you know your weakness is writing documentation, please hire a technical writer. permalink fedilink source parent hideshow 6 child comments replies: [โ] HK65@sopuli.xyz 12 points 2 years ago (1 child) That's exactly what I'm saying, sorry if it came across somehow askew. My point was there is no point in competing over whose job is "better", we should be working together. permalink fedilink source parent hideshow 2 child comments replies: [โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent [โ] RobotToaster@mander.xyz 5 points 2 years ago* (1 child) Most open source projects rely on volunteers, and few technical writers volunteer. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent [โ] GBU_28@lemm.ee -2 points 2 years ago If the documentation is sufficient for the intended audience, it's good enough. permalink fedilink source parent
[โ] HK65@sopuli.xyz 12 points 2 years ago (1 child) That's exactly what I'm saying, sorry if it came across somehow askew. My point was there is no point in competing over whose job is "better", we should be working together. permalink fedilink source parent hideshow 2 child comments replies: [โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent
[โ] vividspecter@lemm.ee 6 points 2 years ago There is a case to be made that people should be a bit more well rounded in general, and not just find a specific niche. So non-technical people should still have a decent familiarity with computers and maybe be able to do some very basic coding. And technical people should spend some time working on their written and verbal communication. Because in both cases, it makes people more effective in their roles. permalink fedilink source parent
[โ] RobotToaster@mander.xyz 5 points 2 years ago* (1 child) Most open source projects rely on volunteers, and few technical writers volunteer. permalink fedilink source parent hideshow 2 child comments replies: [โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent
[โ] Semi_Hemi_Demigod@lemmy.world 2 points 2 years ago (1 child) Totally agree. And I'd argue that we don't even need technical writers. Even if all people do is correct grammar and spelling mistakes it would be helpful, let alone actually writing docs. It's one of the easiest ways non-technical folks can get involved with open source projects. permalink fedilink source parent hideshow 2 child comments replies: [โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent
[โ] JackbyDev@programming.dev 2 points 2 years ago Every time I get stuck on something confusing I'm a README and figure it out I try to submit a patch that makes it more explicit. permalink fedilink source parent
[โ] GBU_28@lemm.ee -2 points 2 years ago If the documentation is sufficient for the intended audience, it's good enough. permalink fedilink source parent
[โ] Tja@programming.dev -1 points 2 years ago (1 child) Humanities are very important. Robots are not yet capable of flipping burgers! permalink fedilink source parent hideshow 2 child comments replies: [โ] Natanael@slrpnk.net 3 points 2 years ago Robots can definitely flip burgers. Some can even do it twice! permalink fedilink source parent
[โ] Natanael@slrpnk.net 3 points 2 years ago Robots can definitely flip burgers. Some can even do it twice! permalink fedilink source parent