Chris Oldwood
where else to find them
no profile links on file
what they talk about
all 7 in the filters
where they keep going back
- ACCU7 editions2016–2025
on a stage with
never shared a talk
who talks about the same things
- Rob Pleau8 talks
- Joe Houghes6 talks
- Jaap Brasser11 talks
- Kevin Marquette9 talks
- James Brundage10 talks
- Gail Ollis8 talks
| title | conference | date |
|---|---|---|
| UB Forte - Hilarious Programming Humor | ACCU 2025 | 2025-04-01 |
Rapid-fire standup that strings concrete tech gags: an AI text editor called AI Mo says "They're really paying you to write this crap", a self-made font built… | ||
| Software Development - Mob Programming, Pair Programming or Fly Solo? | ACCU 2024 | 2024-04-17 |
Argues ensemble work raises long‑term throughput not raw keystrokes, using concrete cases: a week‑long mob on Couchbase to solve transactional concurrency that… | ||
| CO Routine - Computing Dad Jokes | ACCU 2024 | 2024-04-17 |
Rapid five-minute set of roughly 30 one-liners that land as tech puns aimed at programmers, hitting C/C++/Rust, bash, VPNs, CPU vulnerabilities and algorithm… | ||
| PowerShell for the Curious | ACCU 2021 Online | 2021-03-10 |
History and practical demo of PowerShell from its 2006 Windows origins to cross‑platform PowerShell Core and current 7.x previews, showing the central claim… | ||
| Monitoring: Turning Noise into Signal | ACCU 2019 | 2019-04-10 |
Argues that modest structure and event-style logs turn noisy free-text into actionable monitoring: implement structured events (timestamp, name, value), pass… | ||
| Monolithic Delivery | ACCU 2018 | 2018-04-11 |
Argues that the real problem is monolithic delivery not monolithic code, illustrated by a finance scheduler that hits memory at a million trades and by a… | ||
| A Test of Strength | ACCU 2017 | 2017-04-24 |
Addresses how poorly organized unit tests—bad naming, scope, and structure—turn into brittle, write-only suites that slow development. Recommends practical… | ||
| Waltzing with Branches | ACCU 2016 | 2016-04-20 |
Explains when branches actually buy risk reduction versus when they just hide problems, using concrete contrasts: Google’s monorepo with 10,000 devs (20+… | ||
| nothing matches | ||