How do we help devs unlearn the usage of `git add .`?
The problem/challenge is that it is optimistic that you every single change being made is meant to be commited.
Using a -p gets people to think through what they're changing and avoid accidentally adding changes for things outside the scope of the current task at hand.
Jan 31, 2022 • 7 tweets • 1 min read
🧵 Congrats, it's 2034. You're still responsible for that Ruby on Rails application.
No, you never got a green light to rewrite in some new fancy not-yet-released framework back in the summer of 2029.
Rails 12.1.x has just been released.
What technical debt have you secretly been hoping will mysteriously vanish? What will still be lingering?
Oct 3, 2021 • 7 tweets • 1 min read
How I imagine this unfolded.
Support: "People are reporting errors online when searching their transactions"
Devs: "Hmm. We're seeing errors"
Devs: "Oh, it's searching across all of their historical transactions. Can we limit to 3 mo?"
Product: "Here are some common searches"
FE Devs: "Okay, we have the front-end ready"
