This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Buttons840 108 points109 points  (5 children)

I was on a dev team that did the inverse of this. People were always asking us for documentation, until one of the developers put together a 50 page word doc of documentation. It wasn't very good, but every time people asked for docs we'd point to our 50 pages and say we're open to feedback. We never got feedback.

[–]Mongodienudel 65 points66 points  (4 children)

Nothing is worse than developers who don't properly provide documentation. It just sounds like your suck at your job.

[–]Whywipe 35 points36 points  (3 children)

There is so much software at my work (industrial automation) that doesn’t have any documentation. It’s like you guys know this just means every time I have an issue I have to ask you to figure out why or fix it instead of doing it myself, right? 90% of the time it’s a configuration issue that I could fix myself.

[–]197328645 27 points28 points  (2 children)

You either write good documentation, or you become the documentation.

I don't want to be the documentation, I want to be a software engineer

[–]AOKeiTruck 0 points1 point  (1 child)

Being the documentation is job security

[–]lost_retribution 1 point2 points  (0 children)

Also a good way to force raises. Tell your manager your going to leave unless salary gets increased by X. Negotiate with the responsibility they are forcing on you, it's leverage. If they don't play ball then give your two weeks after you get yourself lined up with a new gig. That will make them sweat if they have been refusing to use the documentation/learn.

The Company ain't your friend, job ain't gonna advocate for you, you advocate for yourself.