Month: September 2017

“Avoid Changing Code” Should Be Avoided

Of all the bad advice the geek trades inherit from over-simplified manufacturing & engineering, perhaps the worst: "avoid changing code". Take a minute, and think of all the things the trade does to avoid changing code. Virtually every element of "big design up front" policy is based in this view. …

“Avoid Changing Code” Should Be Avoided See Full Post

Using Strategy & Function-Specific To Attack Large Classes

In IT work — "it puts the database on its browser skin" — we often face sooner or later the problem of the gigantic object. Some systems, especially "global monolith reboots", just start there. Others just grow and grow and insensibly slide into it over time. The problem is that …

Using Strategy & Function-Specific To Attack Large Classes See Full Post

Idols of the Schema: Ignoring Data While Overvaluing Ideas

The ‘idols of the schema’ is a geepaw-ism, and deserves some background & explanation. When we value the simplicity & clarity of an idea over the complexity & muddiness of its referent, we’re caught in an idol of the schema. Sir Francis Bacon was an english noble, a famous lawyer, …

Idols of the Schema: Ignoring Data While Overvaluing Ideas See Full Post

Mastery As Motivator: The M of RAMPS

This entry is part of 15 in the series RAMPS

Let’s talk a little about mastery today, in the sense of the RAMPS conversation from yesterday. What is mastery-as-motivator, and what can we do about increasing its motivational force? As I said before, the motivational force called mastery is about how humans value their own growth. All of us carry …

Mastery As Motivator: The M of RAMPS See Full Post

Scroll to Top