Skip to content

Blag

  1. Writing Good Release Notes

    When writing release notes or changelog entries it's important to keep some things in mind. First and foremost it is important to be aware of who the release notes are for.

    Release notes are not for you…now.

    Release notes are for future you.

    Release notes are for a user who wants to know what the latest updates are.

    Release notes are for a stressed-out colleague who's trying to narrow down when they think a particular breaking change might have occurred.

    Identifying the personas of the people who will be reading release notes is important so as to effectively communicate with them. If you don't understand your audience you may end up losing them.

    If you write bad release notes for a product, you may frustrate your users into finding an alternative solution that feels more stable, or is more predictable.

    If you write bad release notes for a client, you may end up confusing or angering them.

    If you write bad release notes for your team, you may end up alienating your maintainers and slow the pace of progress.

  5. Asking the Wrong Questions About Self-Driving Cars

    Permalink: Asking the Wrong Questions About Self-Driving Cars

    I recently watched Iyad Rahwan's TED talk "What moral decisions should driverless cars make?" and I enjoyed his exploration of the moral dilemmas surrounding self driving cars.

    I was particularly interested when he brought up the dilemma of purchasing a self-driving car that might choose to kill its own passengers:

  7. CSS Frameworks are Box Mix Brownies

    CSS frameworks are like box mix brownies. They're great if you're not picky and just want something fast. 30 minutes and a scoop of ice cream and everything's great.

    As soon as the requirements change, you find yourself needing a new box mix, or a new framework.

    Dave has a nut allergy, Sam's gluten free, and the only gluten free box of brownies has walnuts? Now what do you do?

  10. Bad Assumptions

    I'm going to make a bunch of bad assumptions and we'll get to fix them later