Journal ces's Journal: Well this sucks 11
Crap, the guy who's job I'm supposed to learn announced he is quitting the company effective 2 weeks from today.
So I've got 2 weeks to try to get up to speed on a bunch of in-house crap with absolutely no documentation.
I think this qualifies as a "trial-by-fire".
I guess I'll either learn it or go postal during the process.
Done that, not very fun (Score:1)
Just be nice, identify the critical things you need to know, and focus on those.
Hey - its good job security ... (Score:2)
I'm doing the same thing right now, and there's no way to get a new body "up to speed" in less than 3 to 6 months ... and THEN maybe be able to make the necessary alterations ...
So think of it - once you've mastered it, you've become the one person any business should never have - someone who can't be replaced.
Yes, its major suckage to work like that, but that silver lining is nice ...
Aw, c'mon! (Score:2)
Docs?? (Score:1)
--------------sound familiar?
You need to document everything!!!
When? I work nonstop on ever changing processes and requirements and of course, they all are urgent #1 priorities of the moment.
You can do it in your spare time!
Indeed, Ill get right on that.
*scream*! (Score:2)
*apostrophises to the sky* You know, there actually are people in the world who do documentation professionally, because we like doing it and it's our main job. Imagine that. I just wish more IT managers would get a clue already, since there's no shortage of documentation to do, and programmers generally hate doing it (and further generally don't do a good job of it). Sloughing the job off on the developer just makes for a cranky developer churning out bad doc -- everyone wins!*
Re: (Score:2)
*apostrophises to the sky* You know, there actually are people in the world who do documentation professionally, because we like doing it and it's our main job. Imagine that. I just wish more IT managers would get a clue already, since there's no shortage of documentation to do, and programmers generally hate doing it (and further generally don't do a good job of it). Sloughing the job off on the developer just makes for a cranky developer churning out bad doc -- everyone wins!*
Sadly the only time I've seen professional tech writers employed in the IT/Technology industry is when something has to be documented for an outside third party like end-users or partner training materials.
System Administrators also hate doing docs and are only slightly better at it than programmers. Product Managers do OK but their documents are of limited scope and generally have limited application for a technical audience.
If I ever worked at a place with a dedicated internal documetation person for eit
Good Luck (Score:2)