Month: August 2017

On Pedagogy In The Geek Trades

I find 4 major failings in both how & what we teach in geekery. We mostly don’t. That is, actual teaching of actual geekery-for-a-living is almost non-existent. We suffer in attitude & content & structure from the trivially flawed “information transfer” view of what teaching & learning is. We purport …

On Pedagogy In The Geek Trades See Full Post

Reversible Raincoat Tests

Let’s review "reversible raincoat tests." Sometimes, we build systems in which a downstream collaborator must interface with an upstream one. The two apps are by separate teams, on separate servers, developed at separate times, and still both in development. A reversible raincoat test is a script with two sides. Think …

Reversible Raincoat Tests See Full Post

Why Do We Seek One Ring To Rule Them All?

I’m thinking of this thing called "justifcation privileging," or alternatively "explanation monism". Or even, short hand and jokily, "one ring to rule them all." One constantly sees tweets, blogs, even books, where someone boils down staggeringly complex and ill-understood processes to one factor. Today I saw "people don’t make decisions …

Why Do We Seek One Ring To Rule Them All? See Full Post

The First Coaching Days

I can’t over-emphasize for new coaches the importance of rampant opportunism. Until you’ve established your miracle powers in a team, you won’t be able to move big levers, only small ones. Which small levers will bring you the biggest bang of trust & faith the fastest? Some possible openings: we …

The First Coaching Days See Full Post

Shifting Certainties

Shifting certainties. This is where i’m headed these days. Without belaboring criticism, what i’m seeing is that we have a trade with a whole stack of roles and humans to fill them, and, of necessity, they have assembled a varied, sometimes compatible sometimes not, set of certainties by which they …

Shifting Certainties See Full Post

Refactoring Testless Code

Refactoring in testless code is hard. It’s the perfect demonstration of the manglish "agency" of code. It is simply not possible to change testless code and guarantee you’ve done no damage. It’s one of the most delicate operations geeks do. There are principles, yes. There are tricksy techniques, too. But …

Refactoring Testless Code See Full Post

How I Don’t Apply XP, or Scrum, or Anything

These wrangles over system seem mis-focused. Moreover, they seem part of the surface of the elephant i’ve been trying to describe. A system is inherently an abstraction. It compresses, filters, selects, features from an experienced reality. We formulate systems for at least 3 reasons. First, so we can establish commonality. …

How I Don’t Apply XP, or Scrum, or Anything See Full Post

Why I Write A Test

My intent in writing a test is to satisfy myself by the cheapest means possible that the code does exactly what I think it does. I stress that this is my intent. Believe me, fifteen minutes on the internet will reveal to you a barrage of other possible intents. Surely, …

Why I Write A Test See Full Post

Scroll to Top