iTranslated by AI
The content below is an AI-generated translation. This is an experimental feature, and may contain errors. View original article
📚
Consider Publishing Internal Docs (or Parts of Them) as Tech Blogs
You likely have opportunities to write internal documents. At such times, let's consider: "Could I make even just a part of this public?"
Benefits
- The impact can reach members outside the company. Theoretically, you can share knowledge with all of humanity.
- You can receive feedback and suggestions for improvement from the outside regarding your knowledge.
However,
- Do not include information unique to the company.
What to publish?
Tips and Knowledge
Procedures, common commands, etc.
Opinions and Policies
These are also recommended. It's easier if you write down how you intend to operate based on your knowledge!
Gemini Conversation
Here is what it looks like when I asked Gemini.



Other Public Disclosure Efforts
They have shared their manuals publicly. They are very easy to understand with illustrations.
It is an open handbook; although the purpose is different, sections such as the back-office part are quite helpful.
A Scrapbox I previously created where I write (or want to write) about general IT knowledge.
Discussion