When capturing to-do’s, be sure to include enough information that your future self isn’t confused.
When reporting an issue, make it clear what the impact is.
A playbook for tech managers in dealing with significant outages.
The smaller the individual pieces of work, the greater the chance that a large piece of technical debt will be addressed.
On improving your communication by making request clear and obvious, and not assuming the other person will figure it out.
A way to protect analytics events against refactors and unintentinal breakage - analyics classes in your HTML.
How we went about removing jQuery from a large application that had depended on it for many years.