@stevenstrogatz Farmers: we need a word for a helpful structure that safely stores food for later
Programmers: no doubt, no doubt, and like what if it also meant that only one person knows how to run the build, so the whole company is screwed
Farmers: 😐
@fig Cool tool. Please don’t ask for my email address until I’m ready to use the sharing features.
Asking before I see any value: 🙅 you get mailinator, and I’m salty.
Asking when I’m actively about to share with a friend: 🤩 zomg, have you seen fig? I gave them my real email.
The original iPod included 20 minutes of audio skip protection in case the primary storage device stopped working.
20 years later, Siri on Apple Watch doesn't have 20 *seconds* of skip protection in case an Internet connection can't be established. It just deletes the request.
I’ve added a new step to my debugging flow:
Ask yourself, “Am I willing to live in a universe where this potential solution solves the problem? If yes, proceed. If not, move right along.”
Working in small chunks is one of the powerful dev skills I have!
Among other things it:
👀 Makes it easier to get code review (smaller PRs)
🏃♂️ Keeps forward momentum
🗑️ Prevents code from going stale
↩️ Makes code easier to revert
a thread on ways to achieve this 🧵
@kevin_j_m@tenderlove@searls I would watch the hell of out a show where DHH is the charismatic power-tool personality with some problematic tendencies, @searls tries valiantly to keep him in check, and @tenderlove peeks over the fence, wearing a chef’s hat and muttering something about card, cons, cdr & cats
If your reaction to a software practice or codebase is to search for some reason that it's Morally Impure, you probably won't ship much software. The world is messy. Being good at the work means, in part, learning which messes will and won't actually catch fire.