A developer shares lessons from growing an engineering blog to 463k pageviews, focusing on evergreen technical content and traffic distribution.
Explores the decline of written coding tutorials due to SEO changes, AI, and LLMs like ChatGPT.
Analyzes whether telling AI models 'You are an expert' improves responses, concluding clear context is more effective.
Explores the value of caring deeply about craft in tech, contrasting human attention to detail with generative AI's lack of care.
Explores the value of caring deeply about craft in tech roles like design and writing, especially against generative AI's rise.
A software developer's monthly update on his book 'Refactoring English,' covering reader demographics, sales metrics, and personal goals.
Author announces a new blog focused on software architecture, sharing knowledge and practical solutions for building adaptable software.
Author details using Quarto to write a technical book on data visualization with R and ggplot, focusing on its advantages and workflow.
A tech author realizes she wrote the wrong book for engineers, then rewrites it based on community advice about software buying.
Martin Fowler critiques the overuse of bold text in technical writing, arguing it diminishes emphasis and suggests better typographic practices.
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://crawljobs-blogs-media.s3.us-east-1.amazonaws.com/alldevblogs/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 technical writer's analysis of common pitfalls in LLM-generated writing and practical strategies for using AI tools effectively while maintaining quality.
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.
