Nerd/Human lvl 37. Erdős 4. ES/EN/DE
👨💻 Technical Writer @ Google | Chrome
🎲 Board Game Enthusiast | Host of La Matatena
📚 Passionate about communication, mathematical concepts, sharing knowledge, and the impact of tech in our world.
🌍 Mexican living in Munich 🇲🇽➡️🇩🇪 | Exploring life and tech one day at a time.
Are my toots my own?
| Technical Writing Blog | https://BufferBuffer.com |
| More about me | https://zapata131.com |
| Technical Writing Links | https://technicalwriting.link/ |
| I discuss board games at | https://la-matatena.com |
⚠️ Warning:
For this post we are exploring when and how to use notes, warnings, and callouts in technical writing.
Truth is that writing callouts can be an art, and is good to follow some guidelines. So I decided to write these mostly for me, because I think is something most writers can improve on.
https://bufferbuffer.com/when-to-use-notes-warnings-and-callouts-in-tech-writing-and-when-not-to/
Learn how small docs can improve your technical writing process. I try to cover everything from how they can help get quicker reviews to how they help achieve better collaboration.
Check it out:
https://bufferbuffer.com/why-writing-small-docs-is-a-game-changer/
I started in technical writing almost 7 years ago. And I thank Meeta, my first manager, and my team for helping me figure out these lessons. The 10 things I learned the hard way about tech writing.
https://bufferbuffer.com/10-things-i-learned-the-hard-way-about-technical-writing-in-tech/