We need a better way to track changes within a team over time. I propose borrowing the versioning system we use in software and applying it to teams to track change over time.

A lot of constraints are not that constraining after all.

In this post, we use a tenuous analogy to look at breaking down a project.

In brief, we dedicate one day a fortnight to learning and personal development.

A bug we wouldn't have been able to solve without a native Mandarin speaker.

Using the John Rawls' thought experiment to reflect on best practices

We need to re-define efficiency by redefining what we consider waste.

I wonder if we need a different framing for developers that span the gamut?

Designing a good programming language requires as much of an undertanding of how humans communicate as it does the machine.

A useful quote from Eskil Steenberg