markdown
-
✉️ Drafting emails in Markdown
As developers, we use Markdown all the time: in documentation, GitHub issues, etc. Pretty much every tool supports it now, except email. With email, we are still stuck with a 2005 MS Word experience. Why Markdown? Once you know the simple s…
-
📝 You can't improve an email
I’ve been moving discussions out of email and into versioned Markdown files. Here’s what I’m noticing. Email has a structural problem: the only options are reply and quote. The original message can never be improved. When someone joins a pr…
-
🌱📈 Simplicity scales
When programming, we learn that simple interfaces and simple data structures are good, because they are flexible. Simple file formats are the same. We can do way more with a CSV or Markdown file in terms of presentation and automation than …
-
📝 Personal vs. collaborative documentation
Yesterday, we discussed the importance of a personal note-taking tool. We can also extend this concept to a team or company using Wikis, Markdown in Git, shared Google Docs, etc. Collaborative documentation is very valuable – IF you can get…
-
📧 Inbox zero
Thanks to a nudge from Khem, I’m back to Inbox-zero. The big question is what to do with emails that need action or have valuable information in them? Some put them in a special folder. Others tag them. Others forward them to lots of people…