Hopefully it's obvious that the click-to-advance is a style that suits my presentation style, and I would have made different choices if I intended it to be consumed online.
In any case, I've learned a lot since this talk and have on occasion considered updating it. I'm pretty surprised it's trending, TBH.
It's nice to see these patterns and thoughts written out.
Finally somebody understands their ABD's
I would _definitely_ present these ideas differently today; the language we all use to describe problems and solutions has changed quite a bit in the meantime.
And how I _apply_ these tactics and strategies is much less confrontational than when I was in fintech, mostly because I'm older and more patient.
But the essence of the advice in here is still a big part of how I work: having a technical roadmap to match the product roadmap; getting small wins on the path to long-term goals; talking about what you've built and showing it off; taking responsibility for product and design decisions if nobody else is; building a team who will share ownership; diagnosing dysfunction with Vaillant's defense mechanisms; using estimates to pay off technical debt and experiment with new technology and approaches. All of these tactics and strategies are still valuable in my opinion.
Anyway, has it ever been the case that someone asks Pivotal (1) to do something well-specified (2) that they really, truly can't do themselves (3) but actually makes sense to do, like is positive ROI? If those three things align, you are never hiring a contractor!
Only mentioning for fidelity