Software Architect at @procoretech, avid SCUBA diver, underwater photographer, organizer of @sbjavascript, father, husband, musician

Joined February 2014
213 Photos and videos
Pinned Tweet
My talk from @JSConfUS 2019 "TDCD: Test Driven Component Development" is live!
10 Sep 2019
TDCD: Test Driven Component Development by @TimCDoherty youtu.be/SDoq37lXHEw
3
Here's all that matters when it comes to Agile—everything else is complete crap: "We are uncovering better ways of developing software by doing it" It's entirely about learning based on experience. Uncovering, not uncovered. "Individuals and interactions over processes and tools" Rituals, ceremonies, Sprints, SMs, POs, various meetings. NONE of that is useful. Dump it all. Talk to people. Get feedback. Pay attention. "Working software" Anything that's not directly putting working software into customer's hands is just waste. Stop it. "Responding to change over following a plan" We learn as we work, we adapt based on what we learn. That's it. Anybody who says "Agile" is anything other than that is selling you snake oil. Any corporation that's calling anything other than the above "Agile" is either delusional or evil.
9
25
160
11,857
Tim Doherty retweeted
Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.
7
270
960
37,382
"Agile" is not a code word for some rigid corporate process. It's in the dictionary. It means flexible, nimble, &c. Look it up!
2
13
86
6,289
Tim Doherty retweeted
18 Jul 2024
if your brother put dog poo in your milkshake, your problem is not with milkshakes. "Agile is terrible and must die" posts are really about the poo and the brother, but they're written as if all milkshakes are poo milkshakes.
12
9
62
5,301
JSConf Budapest, happening right now
1
70
"Technical Debt" stems from doing the best job you possibly can, but later on you learn something that makes that code have a large 🤮 factor. It's inevitable. As Ward Cunningham says, refactor the code by replacing it with the code you would have written if you know what you now now. Bugs are just crappy programming (e.g. without sufficient automated unit tests), not technical debt.
13
12
98
13,976
Tim Doherty retweeted
JS Summer Time Conference in Amsterdam🌞 50 speakers to inspire you, 1.5K attendees to meet, the biggest JS party to dance,💃sing in karaoke, 🎤 and just unwind. Save the dates: June 13-17🎉 An experience you won't regret: jsnation.com/
135
188
307
19,158
Tim Doherty retweeted
29 Oct 2023
PARENTS: Be sure to check your kids' candy bars for Next.js 14 server actions. My four-year-old nearly got write access to the production db
19
357
2,524
260,838
This.
If you think devs tend to overly focus on trivialities, I’d argue it’s often a symptom of a fractured team. Someone else has the product ideas. Someone else does the UX research. Someone else designs the product. Devs want to have agency. They’ll exercise it on whatever’s left.
1
158
A: Show me data that proves that mob/ensemble programming works. B: Show me data that proves that whatever you're doing now works! A: Erm…
3
5
43
9,226
Henrick Kniberg's picture on the left is often used to illustrate agile dev, but I think it's fundamentally misleading. It's an evolution, not a radical change to the type of vehicle. I prefer the picture on the right. 1/1
28
28
207
Tim Doherty retweeted
might be a nuclear take, but I’d wager more harm is done by devs who love to code & treat their job like a hobby (where they solve fun code puzzles instead of solving their users’ immediate needs) than by devs who do it for the paycheck
180
128
2,496
I think one of the most destructive myths in software is that it costs more or takes longer to develop higher-quality code. IME, the higher the quality, the faster the development goes. You cannot be fast if you can't trust your code.
51
193
858