Technical Writing for Software Engineers

If I had to look back at my career—and pick one skill, other than coding, that had the biggest impact on it—I would pick writing. Technical writing, to be precise. Many engineers fall into the trap of becoming a good coding machines, which is not bad, but once you move to more senior positions—you find yourself writing less code, and more technical documents. I had the opportunity to have great mentors who helped me take my career to the next level, and helped me with technical writing. Throughout my career, I’ve perfected my technical writing skills, and produced great technical documents. One of them, a design review, became the gold standard for other design reviews inside the Tel Aviv R&D office of Autodesk. Today, I’m happy to announce my first hand-e-book: Technical Writing for Software Engineers. This handbook is short and concise, and will give you tips and guidelines on how you can improve your technical writing skills. You don’t have to get this handbook in order to become a better engineer. But this handbook is a collection of my mistakes and experience, together with tools and tips on how to improve your technical writing skills.