Ownership

Who owns the consequences once implementation stops being the hard part.

Building software has become cheap, and the arguments about it are mostly about speed. The part that stayed expensive is the one nobody photographs: somebody has to hold the context, carry the maintenance and answer for the system a year later. These pieces circle that question from three directions, from a classroom, from a team of six, and from the current enthusiasm for building without developers.

All writing →