Nerd Pride Radio

Our documentation is not the kind of documentation a Top 100 company ought to have. I waste so much time for things that should be written down and aren't.

My administrator frequently gives me projects, takes them back before I've had a chance to get even half-way done, then gives me more projects with a "You seem to be underutilized, and I'm sure you don't want to go down to part time, so I'd like you to work on a project for me..."

Paul should punch that guy in the epiglottis.

I'm not clear if the manager is a man or a woman, but in either case, I think Iantha should punch them in epiglottis.

Tell you what, Caz. You torch your place for poor documentation and I'll punch Dawn in the epiglottis for being a shitty manager and low key threatening my job if I don't take on the projects that she was supposed to be doing in the first place.

I do love Paul, and I do love working on projects with Paul, but I handle my own wet work.

That's where it pays (literally) to be a contractor paid by the hour. If they change their mind and want me to work on something else, that's just more billable hours for me. It's done a lot to help me not give two shits whether they keep changing their mind, or decide to go a different direction halfway through a project, etc.

Yeah, I was a contractor for a few years but with the language industry here it's kind of hit-or-miss on hours. I really need a steady, predictable income right now. Otherwise I'd totally go back to being an independent contractor.

I love the warm, comforting scent of well-conceived policy language. I assume that's rather like documentation? Not red tape, mind you, but just well-conceived policy language.

I'm a huge fan of how documentation (outside of the IT world, in particular) has effectively become viewed as a way to indicate how replaceable you are. "Well, you wrote all this down for us, so what do we need you for now?"

How else are we supposed to figure out what to program the robot to do?