Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Some places still have very good tech teams, but it still requires working between the teams. (EX from a company I worked with: https://forums.madcapsoftware.com/viewtopic.php?t=30365)

The writers can't do their work without input from the technical side and the time for that is often not avaliable.

I know I've been punished for taking time to push ideas to tech writers. Not only does it slow me down in other places, it often gets swept away as unnecessary changes because upstream Sr techs disagree.

For example, when I modify ssl configs, I alway reference the files with soft-links. This makes it so you don't need to modify the config files and simplifies keeping old and new certs so you can flip back during the overlap period you should be providing to test. I try to avoid editing production files by hand whenever possible because in my experience it introduces the possibility to create errors.

I rewrote some docs extending alot of areas with example commands showing how to test things, with explanations that fleshed out the previous quick and dirty documentation. I also modified the method from copy and replace certs, edit files, restart service; to copy files, replace or create soft-link, restart service.

Upstream approvers trashed the whole thing because the thought it was unnecessary and disagreed with me about manually editing config files.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: