Senior Technical Writer
CurrentBeing a technical writer among engineers that design embedded hardware and software is a never-ending uphill battle, because the subject matter is ... challenging to say the least. However, the other side of the coin—and the very luring one—is relentless professional development. There is simply no other choice but trying your best to keep up.I used to take part in improving hardware documentation by creating templates both for content and tools, developing information architecture and content strategy, improving terminology and taxonomy, developing style guides, designing workflows, automating some things, and documenting it all. I also made attempts in improving the content by sometimes rewriting it, but mostly by editing and reviewing. In retrospect, most of these attempts dabbling with content seem to have been worthwhile as they mostly made it to the outside world.These days, I am a proud member of the DevRel team, learning the trade of creating and maintaining a company blog from both technical and organizational perspectives and gaining better understanding of how open-source communities function. As a backdrop to that, I keep editing, reviewing, and, sometimes, rewriting content, however, this time it is learning materials and articles that pass the information on from, so to speak, human to human point of view or, rather, from developer to developer, as opposed to disembodied technical documentation.All in all, a lot has been done and achieved, yet a lot more is waiting in the wings.