← writing
1 December 2022

What happens around the code

Two client engagements in parallel for much of the year. At that pace, the fatigue comes from reviewing, estimating and handing over, almost never from the model.

Two engagements run in parallel, in retail and distribution, with the sense that technical skill is no longer the limiting factor. The difficulties come from how a team decides, delegates and communicates. Next year I will probably write less code and discuss more how it should be written.

01Chris Riccomini et Dmitriy Ryaboy, The Missing README
Cover of The Missing README

What no course teaches: reading code written by others, getting your own reviewed, estimating, refusing. Worth giving to anyone joining a team, even an experienced one.

02Johanna Rothman, Behind Closed Doors
Cover of Behind Closed Doors

Managing a technical team approached through concrete situations (the one-to-one, delegation, difficult feedback) rather than principles. Useful even without a team, to know what you can expect from your own manager.

03Frederic Laloux, Reinventing Organizations
Cover of Reinventing Organizations

To be read with caution, but with profit. Its typology of organisations explains why two clients of similar size are run very differently. Its promise of a higher stage needs checking somewhere other than in the companies it selected.