Many days I feel like my work as an agile consultant is simply internalizing (externalized) costs. First example that comes to mind: software development done too quickly which creates technical debt as it goes. In the short term, a project like that can seem very successful, exceeding expectations for delivery time and customer satisfaction. And then … Continue reading The Economics of Programming: Externalized vs. Internalized Costs
Another point for Haskell In Round 1 I described the task: find the number of "Titles" in an HTML file. I started with the Python implementation, and wrote this test: Very simple: I had already downloaded the web page and so this function had to do just two things: (1) read in the file, and then (2) parse … Continue reading Python vs. Haskell round 2: Making Me a Better Programmer
It's a sappy title, but bear with me. I'm wondering if the best lessons of diversity and inclusion can be applied to software development? For example, if something is offensive to others, then it's worth looking for an alternative — even if I'm not personally offended. I witnessed an interesting disagreement on a software project: … Continue reading Engineering with Empathy: how do we decide when to fix?
This is in response to Why Meteor will kill Ruby on Rails. A pretty big claim, for sure. Now, Meteor is worth checking out, but Josh didn’t name any of the reasons why I and a whole lot of others choose Rails. So here we go. It was its built-in support for these got me interested: CRUD (Create / … Continue reading Meteor Won’t Kill Rails Anytime Soon