I think _evidencing_ pair/ensemble programming is the biggest barrier to TBD in regulated or audited environments.

I’ve been thinking about this a lot. Audit evidence is exactly what Kosli is for. I would love to chat through some thoughts on this with you.

Is there a better way to have a speed dial to relaxed than an old fashioned?

Notice that all of the execs who are deciding that DEI isn't worth it are white. Meaning the people who are in charge and get to decide what's "worth it" are still white and mostly men.

That was part of the point of seeking more diversity. We know what they're gonna do. We need somebody else.

We were clear when we started what qualities we valued.

Perhaps that’s the key in commercial work is for everyone to be clear about the qualities the team value - and why?

Best is subjective, right? That code, for us, had all the qualities we valued - that were important in that context.

For a lot of commercial work the cost of delay to work like that might outweigh the value of those other qualities.

The space was between the pairing sessions was such a key part of what made that work.

Some of the best code I’ve ever written, paring with @tooky.bsky.social, was made one day a week, over 18 months, with ample space for contemplation in between each weekly session.

We weren’t trying to be (or look) productive, yet 10 years later what we produced was vital to that project’s success.

I’m not one for regrets, but the whole elf on a shelf thing.

Magic of Christmas == 24 days a year of scrabbling around making up an elf-prank when all you want to do is go to bed.

It's Black Friday time at Pragprog
Just use coupon code turkeysale2024 at checkout and take 40% off (ONLY at pragprog.com)
Everything we publish is on sale... including Beta Books!

https://writing.exchange/@tooky/110655008716267602 You’ve written a test. You know it will fail. Run the test before you start fixing the code. Please. I promise it’s worth it.