⚠️ 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/

One of the most important things in Tech Writing is defining your audience.

But don't worry, using personas (usually used in UX) can help you understand your audience needs and expectations. And I have a quick overview for you right here:

https://bufferbuffer.com/using-personas-in-technical-writing/

Do you want to boost your technical writing career?

If so, in this month's post in BufferBuffer, I'm talking about three books (plus an extra) that helped me gain crucial knowledge and improve as a technical writer.

I'm writing another post about non-technical-writing books that may be helpful for technical writers. Any suggestions?

https://bufferbuffer.com/three-books-to-boost-your-technical-writing-career/