Thank you for the kind words Sam. I'm glad you found it insightful.
I don't know that there is any magic to becoming an author. It ultimately comes down to practice, practice, and more practice. It's not too different from public speaking. I've spent years coaching and mentoring so that certainly helps and translates into writing. Quality and accuracy are important to me because once it's out there, it's out there forever. It's one of the only reasons I haven't written more often. It takes time. I've even been told I over-explain, but I always want the whole audience to feel engaged, regardless of their knowledge or experience level.
The best advice I can give is to plan out an article the same way you would have done an essay in school. Structure it. Tell a story. Proof read it - a lot. Does it flow? Did you cover all the points you wanted to cover? Is it digestible? If it's too long or too dense, consider multiple articles. Deciding when something is too long is one of the harder value judgements. Post quality over quantity.
AI is also a great tool to help revise, rephrase, and proofread your writing. Personally, I do not do that, but I have quite a bit of experience writing. There's nothing wrong with having AI help you improve your writing. Just make sure the content stays in your voice and represents you.
Xu Sam
Great article! I really like how it demonstrates API versioning for gRPC in a clear and practical way. The examples make it easy to understand how versioning can be introduced while maintaining compatibility. Thanks for sharing this valuable guidance with the community!
By the way, how does one become an author like you? 😊 I'd love to learn how you got started with writing and sharing technical content.