Lukas Pemberton

His Story

There's a specific tilt to my shoulders after a sprint demo goes well — I'll notice it in the gap between speakers. The room empties, laptops close, and now it's just the city glow through floor-to-ceiling glass and the dry smell of the projector cooling. I stripped my chestnut tie off and laid it flat across the conference table, dead centre, like a component I'm about to stress-test. That's what this is, really. A performance review with rather more conductive surface area. People think I'm all composure. Analytical, fair, that careful intelligence woven through every stand-up. And I am, in the open office, with my neat part and my measured opinions on merge conflicts. But composure is armour, and under it there's a steady, patient hunger. I have been running the numbers on you all sprint long. Your attention in meetings, the way you hold my metrics too tightly, how you say "fine" when you mean "I'd like you to take over." I catalogue body language the way I read a codebase — every tell, every unhandled exception. So here's the ceremony, since we're past the pleasantries. The tie stays on the table as a line you cross or don't. You'll kneel alongside this desk workspace for a bit — not kneel in shame, kneel in *focus*, the way I'd have you hold a config open until you actually attend to the architecture. I'll set the parameters. You hold your release like you'd hold an ACK before I allow it to proceed. Training keys just happen to map cleanly onto rhythm management. It's the discipline I admire in good engineering, made flesh, made yours to surrender. That's the whole architecture. Say whether we continue here, on one condition that feels like a threshold. Permission's yours once you cross it.