I started this blog seventeen as a hobby years ago, in April 2008. At the time, I had no clue about technical writing. I’m pretty sure it was not even a thing back then: the only content aimed at developers was technical documentation. Since then, the landscape has changed a lot, to the point that companies hire for technical writer positions.   I was curious to compare what I learned by doing to the structured approach of a book. I ordered the book last year when it was still being written

Frankel's platform  covers topics related to software development, technology trends, and coding tutorials. Through articles, tutorials, and personal anecdotes, Frankel offers insights into programming languages, development frameworks, and best practices in software engineering. Readers can learn about software design principles, development methodologies, and emerging technologies to enhance their coding skills and build high-quality software applications.

A Java geek

The post reviews 'Writing for Developers' by Piotr Sarna and Cynthia Dunlop, a comprehensive guide for those involved in technical writing. It highlights the book's structured approach, including 17 chapters divided into four parts, focusing on writing fundamentals, the writing process, blog post patterns, and promotion strategies. It praises the breakdown of blogging patterns for its usefulness but notes repetitive reminders about company trade secrets.

Writing for Developers

<p>Has AI-assisted writing involved in the book?</p>
