A developer reflects on 10 years of technical blogging, sharing lessons on writing, consistency, and the evolution of topics from JavaScript to React Native.
![[journal] 2025 in Review: Writing](https://alldevblogs.blob.core.windows.net/thumbs/article-8ff9e6160e26-full-8b759916.webp)
A developer's 2025 year-in-review focusing on writing output, including a Rust book update, an AI article, and personal blog & newsletter stats.
A monthly retrospective on writing a book about effective writing for software developers, covering progress, goals, and metrics.
A developer critiques common patterns and 'smells' in AI-generated and low-quality blog posts found on platforms like Medium, offering tips for better writing.
Advocates for including author names and dates on technical documents to ensure proper attribution, support career advancement, and foster a healthy engineering culture.
A software engineer argues that technical blogging remains valuable, inspired by a book on writing effective posts and using AI as an editorial tool.
A guide to implementing inline footnotes in Markdown to add citations and notes without cluttering the main text.
Author shares experience raising $6k via Kickstarter for a self-published technical book aimed at helping software developers improve their writing.
How to configure Vale CLI to ignore front matter when applying consistency rules, preventing false positives in documentation linting.
A tech founder reflects on using Twitter for technical discourse, product development, and personal motivation, while acknowledging its addictive nature.
Argues that politeness markers like 'please' weaken technical documentation and should be replaced with direct, actionable instructions.
Introducing nbsanity, a free service that instantly transforms public GitHub Jupyter notebooks into polished, customizable web pages using Quarto.
Tips for writing effective content for developers, covering the AIDA formula, developer voice, and being genuinely useful.
Strategies for building an audience as a technical writer, focusing on authentic engagement and consistent content creation.
A developer argues that embracing confusion leads to deeper technical understanding and valuable blog content.
An analysis of the financial realities of writing technical books, covering royalty models, potential earnings, and publishing strategies.
An analysis of key qualities that define excellent non-corporate technical blogs, including tackling complex topics and showing working code.
A developer outlines the consistent five-part format for their upcoming technical project tutorials, including Introduction, Materials, kBits, Details, and Wrap-Up.
Introducing 'kBits', a new format for sharing concise, single-topic technical learnings and insights alongside project tutorials.
A software developer shares key writing lessons learned while authoring a book, applying principles like KISS from software development to improve clarity.
