Writing to be read
Practical tips for writing clear, readable technical documentation and notes, focusing on structure, formatting, and user psychology.
Practical tips for writing clear, readable technical documentation and notes, focusing on structure, formatting, and user psychology.
A guide on improving code review communication and avoiding conflict, based on a real-world example of a failed review process.
A guide to improving code reviews by focusing on constructive communication and empathy, treating it as a social process rather than just a technical one.
A product manager shares seven key habits of developers who consistently ship great, user-centric features, focusing on communication and ownership.
A software developer summarizes key lessons from 'On Writing Well' to help fellow developers improve their writing skills.
An IT professional discusses the need for better communication between technical and non-technical business departments to bridge the digital divide.
A tech consultant explains why clear, professional writing is a critical skill in IT, covering grammar, context, and documentation.
A developer reflects on the importance of carving out time to read and study others' work for professional growth and idea generation.
Argues against using Slack for FOSS project communication, advocating for IRC due to its open, standardized, and distributed nature.
Learn how to structure a compelling tech conference talk using Pixar's narrative storytelling framework to engage and persuade your audience.
A critique of DigitalOcean's unclear communication regarding new VAT and sales tax changes for business and individual customers.
A guide to maximizing email effectiveness for feedback and communication, focusing on intentional strategies over inbox management.
Argues that over-reliance on color pickers and palette galleries hinders learning and effective design communication.
Software developers can improve their writing by learning techniques from professional copywriters, as suggested in a review of 'The Copywriter's Handbook'.
Discusses the need for respectful, professional communication in code reviews, using the Linux kernel mailing list debate as a case study.
A developer shares insights on designing tech conferences to foster meaningful hallway track conversations, covering break lengths, venue layout, and social activities.
Explains how to implement framework-level event communication between views in Backbone.js using a central event dispatcher.
A software engineer shares five key principles for successful software delivery teams: flexibility, commitment, respect, communication, and reliability.
A software engineer's perspective on upward micromanagement, offering strategies for managing your manager effectively.