Wrote 20 knowledge base articles this week
Posted by Ragepower529@reddit | sysadmin | View on Reddit | 31 comments
Been feeling super motivated recently I wrote 20 knowledge articles this week. Which brings me to almost 78 for the past month. I plan on doing a deep dive into AD DS tomorrow, and avd user profile / golden image along with conditional access policy’s.
On the other bring side 3 of them knowledge base articles I finished today I was able to use to knock out tickets in sub 5 minutes.
Unfortunately I still have over 400 groups left to document / remove / archive along with almost 60 intune policies to breakdown and decipher, not to mention figure out 50+ enterprise applications and if they do anything or why are they linked.
Grandpaw99@reddit
Any chance of a link to the Sharepoint so I can read them?
sfc-Juventino@reddit
Congrats to you.
Know that nobody will ever read them. But as soon as someone fucks up, you can just point to them. Make sure that everyone knows that they exist or that will be everybody's get out excuse.
Reverent@reddit
I write documentation so someone stupider than me can follow the documentation.
Someone stupider than me is me in 6 months time.
KindlyGetMeGiftCards@reddit
You are very wrong, I read my own KB's or instructions, not because I don't know it, but because I don't want to relearn the lesson why I made the doco in the first place. Some of us actually RTFM, others whine like a chihuahua on heat, which are you?
Intelligent-Magician@reddit
Same. I don´t write KB´s for other, it´s mostly for my future me .
RatsOnCocaine69@reddit
I do both, actually
ellerbrr@reddit
Agree. And as I get older I don’t remember everything so good no more. My own docs save my butt. And my personal OneNote is a godsend - my book of knowledge accumulated over years.
sfc-Juventino@reddit
Yes, I agree with you. But you are missing the point - do others read what you write ?
jmeador42@reddit
Exactly. Real admins document, not because they’re organized, but because they’re lazy. This way when someone asks you a question you can just say “there’s an article for that”.
aXeSwY@reddit
I wouldn't be doing this, I would have written them but not dropping them all at once.
Because you get labeled as the KB guy in your team, you will be doing same work + writing KBs and documentation for evert new process/product.
CA_Dukes90@reddit
Gotta strike while the documentation iron is hot!
layerOneDevice@reddit
Enjoy the Adderall prescription
Fath3r0fDrag0n5@reddit
Google is my KB
DerickL04@reddit
awesome keep up the good work i would defenitly maker use of them. When will you release it
bryiewes@reddit
Whats it stored in?
mlambie@reddit
Personal Obsidian
awit7317@reddit
My preferred choice for the last couple of years. Copy to corp wiki when I have time.
awit7317@reddit
Base64 encoded Klingon. Just to ensure that they can’t be read but can be seen in an index.
I__M__NoOne@reddit
heapsp@reddit
bosses boss sees it and realizes he can point a bunch of 2 dollar an hour overseas people at it and lays you off...
Ragepower529@reddit (OP)
Honestly a terrible take, first no over seas work for compliance reasons, second over documentation never failed me once.
heapsp@reddit
geez it was a joke! haha
CaterpillarFun3811@reddit
Such a lazy excuse not to do documentation.
heapsp@reddit
geez it was a joke! haha
CaterpillarFun3811@reddit
What's a good product for documentation?
Old place used xwiki, I'm looking for something easy to setup and maintain. Also easy to display/view docs.
bbqwatermelon@reddit
Hudu, it is very well thought out.
gryghin@reddit
Documentation is so important. It's the best CYA shield.
budlight2k@reddit
You should make a onenote of them all for keeps or even publish them online, as long as they don't contain your business specific details.
If sure, appreciate a read. I'm going to be posting articles on Linked In soon.
vagueAF_@reddit
cool...
Alaskan_geek907@reddit
I have a strong feeling this will be me soon, our company is so poorly documented
Epileptric@reddit
That's awesome and will be a fantastic help to anyone who joins your team, good work