News for hackers. Stuff that matters.
Re:Technical Writing for Developers by bryanrasmussen on Friday July 15, 2022 @04:41PM (#32112569)
As someone who is a pretty good writer, with a long career, I've never experienced any project or workplace actually caring about my ability to write or rewarding me for it (beyond some lip service)
Re:Technical Writing for Developers by madeofpalk on Friday July 15, 2022 @04:46PM (#32112627)
I think that good writing is one of those things that people don’t consciously realise. Just like actually good UI.
Re:Technical Writing for Developers by layer8 on Friday July 15, 2022 @07:38PM (#32113894)
You do it because you care about it. It's an instance of "be the change you want to see in the world".
Re:Technical Writing for Developers by Timwi on Friday July 15, 2022 @08:20PM (#32114136)
It would help motivation to have some allies though.
Re:Technical Writing for Developers by k__ on Friday July 15, 2022 @09:12PM (#32114426)
The moment I switched from selling code to selling text people started rewarding me for it.
Re:Technical Writing for Developers by therealdrag0 on Saturday July 16, 2022 @12:30AM (#32115240)
How do you measure lip service vs not?
Re:Technical Writing for Developers by bryanrasmussen on Saturday July 16, 2022 @12:59PM (#32119852)
lip service - in interviews and onboarding talking about how they value documentation

not - in actual work no time put aside for actually writing documentation.

Re:Technical Writing for Developers by therealdrag0 on Saturday July 16, 2022 @02:16PM (#32120511)
Somewhere in the middle, my place definitely values good documentation. I’ve gotten kudos for it and I’ve had my manager bemoan poor docs written by other engineers as a sort of “doesn’t meet expectations” signal.

We don’t explicitly put aside time for it, but it’s expected as part of normal work. Though mostly for upfront design. Less often for after the fact design.