The idea that walking around with a seven-pound ReWalk system is healthier for your body than using a wheelchair is wishful thinking, to use the kindest phrase I can summon.

Next time someone asks if you want to crash at their hacker mansion for the summer […] or team up for a 24-hour hackathon, think twice. They’re probably just trying to cash in on your youth and optimism.

[Y]ou’ve already chosen the medium to make your argument, and it’s your actual design work. By moving from the artifact to words, you game the system: your users won’t have access to your words when they receive your argument in the form of the final design. All they have is the thing you’ve made, and so it needs to offer the complete argument on its own.

When we outsource war to private military contractors, and when we have separate, shorter lines for airport security for those who can afford them, the result is that the affluent and those of modest means live increasingly separate lives, and the class-mixing institutions and public spaces that forge a sense of common experience and shared citizenship get eroded.

There was a research study in marketing that if you offer people 24 different types of jellies, you’re not going to sell as many as if you offer them six.

The factors that allow programs in functional languages to sometimes be more concise than imperative implementations are pretty much orthogonal to the use of pure functions — garbage collection, powerful built in types, pattern matching, list comprehensions, function composition, various bits of syntactic sugar, etc. For the most part, these size reducers don’t have much to do with being functional, and can also be found in some imperative languages.

A palliative care nurse called Bronnie Ware made a list of the biggest regrets of the dying. […] If you had to compress them into a single piece of advice, it might be: don’t be a cog.

Don’t use Cucumber unless you live in the magic kingdom of non-programmers-writing-tests (and send me a bottle of fairy dust if you’re there!)

Every line of code you write has a cost. It takes time to write it, it takes time to update it, and it takes time to read and understand it. Thus it follows that the benefit derived must be greater than the cost to make it.

The commenters mainly took a shit on the app and the concept. […] That’s why they’re commenters and not out there building things.