11–20 of 153 posts
It just requires time, and I would be happy to spend that time (I love writing, whether docs or just thoughts). As long as there's no ticket for it (approved by a stakeholder and assigned to me by the micromanager), I can't clock hours on it, and if I'm not clocking hours on a ticket, I'll eventually get an angry call..
It's not just lack of incentives, it's disincentives.
> Writing is a tough, demanding task. It requires organizing our thoughts clearly, examining them critically, and expressing them clearly. While the expressing part can be simplified to some extent (depending on the quality of writing required), all three steps are taxing when done properly. Wow, almost sounds like some other aspect of a job a software engineer is required to do... > If a developer doesn’t write docu…
> It should.
Perhaps, but it doesn't.
Good software, bad doc is probably okay.
Bad software, good doc is downright bad.
Therefore, people/exec/management don't prioritize it.
If it were to be compensated with 100k, you would get the best doc ever.
We can't improve things if we don't incentivize. We don't incentivize because it's not that important.
> Writing is a tough, demanding task. It requires organizing our thoughts clearly, examining them critically, and expressing them clearly. While the expressing part can be simplified to some extent (depending on the quality of writing required), all three steps are taxing when done properly. Wow, almost sounds like some other aspect of a job a software engineer is required to do... > If a developer doesn’t write docu…
the last is bs. if you dont ship you wont make money, the compaby dies. if you dont write docs, you might incur tech debt but the company keeps on living. ofc if there is enough time and manpower: write docs, write unit tests, discuss architecture. no prob. but for a lot of companies speed is king
Yes there are trade offs with everything you do in IT, one of them is creating a shit place to work in the name of speed.
It might work for a little while but eventually you're going to realize you're shitting where you eat.
Earlier quoted context omitted.
the last is bs. if you dont ship you wont make money, the compaby dies. if you dont write docs, you might incur tech debt but the company keeps on living. ofc if there is enough time and manpower: write docs, write unit tests, discuss architecture. no prob. but for a lot of companies speed is king
It's not bs. They said should, not must. Yes there are trade offs with everything you do in IT, one of them is creating a shit place to work in the name of speed. It might work for a little while but eventually you're going to realize you're shitting where you eat.
Not only for your external documentation... for all of it.
If you are afraid of the costs, do the math.
1 technical writer for every 20 developers.