Software Architect at @procoretech, avid SCUBA diver, underwater photographer, organizer of @sbjavascript, father, husband, musician
Santa Barbara, CA
Joined February 2014
- Tweets1.4K
- Following362
- Followers193
- Likes2.4K
Tim Doherty retweeted
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.
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.
Tim Doherty retweeted
"Agile" is not a code word for some rigid corporate process. It's in the dictionary. It means flexible, nimble, &c. Look it up!
Tim Doherty retweeted
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.
Tim Doherty retweeted
"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.
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/
Tim Doherty retweeted
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
ALT snickers with next server action inside
Tim Doherty retweeted
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…
Tim Doherty retweeted
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
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
Tim Doherty retweeted
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.
Tim Doherty retweeted
The 8-hour day is a remnant of 19th c. industrialism. The factory ran 24x7 with three shifts. There's zero reason to keep that convention in software. We don't work shifts. Nobody can can do intense creative work for 8 hours straight, day in, day out.
Tim Doherty retweeted
I’ve also never met a good software architect who was not also a good programmer. Practical experience actually building stuff matters. Don’t see how a cert can cover that. 3/3
Tim Doherty retweeted
A student asked me yesterday why orgs demand estimates of impossible-to-estimate activities. Best answer I could come up with was that an estimate allowed them to deflect blame. Someone yells at them for going too slow, they say, "Yell at them. They estimated it."
Tim Doherty retweeted
The only time when you can definitely and accurately estimate the time it takes to build a story is after it’s done.
Tim Doherty retweeted
Imagine being in a band where each member plays their instrument separately, then sends it to the others who write a letter with their feedback.
That is what your PR / code review process looks like to someone who has experienced ensemble or pair programming.
Tim Doherty retweeted
Module Federation is on the radar: thoughtworks.com/radar/langu…
And that's it! There's a ton of other super interesting stuff on the radar as well, which I need to explore more, like Import Maps, React Hook Form, and Webpack Module Federation. Check it out and let us know what you think! thoughtworks.com/radar
Tim Doherty retweeted
I've open-sourced Medusa! Help us make it awesome
github.com/module-federation…
Tim Doherty retweeted
Our first confirmed keynote speakers for #LAG21 will be @DiversityDana and @cliffhazell. We are extremely excited to welcome them both back to the conference. We are also proud to welcome the other awesome speakers. leanagile.global/speakers/
