One Feature Per Day.

Expanding on the idea to 👉 Deliver one feature per day:

1️⃣📆 A "feature," in this context can fall into any of the following categories:
1. net new: a new piece of functionality,
2. fixes: restores a broken feature, or
3. enhances: adds to existing feature(s).
Generally, I prioritize them in above order.
🧩👍 In this way, I favor solving my own new problems (net new), maintaining my solutions for problems (fixes), and extending my solutions in creative/useful ways (enhances).
🔧✈️ While build the plane as I fly it, I find it useful to engage in lightweight planning. I find this is best done via 🖊️💻 whiteboarding, prior to coding.
▶📖 By Action > Documentation, I try to avoid putting down too many words on paper that are not code or configuration components, which will have chance to directly solve my problems.
I recognize that not every problem can, nor needs to be, fixed by code.
🔄📚 I use version control so I can safely experiment and restore. I also back up my data periodically--first manually. Once the solution proves itself worthwhile, I can invest time to build building automated back-up mechanisms.
⚒️🏃 I hack together the quickest possible solutions so that I can get it into my hands, and use them as fast as possible. I try to use the solutions on a daily basis -- if I don't (or can't), then why the hell am I building them?

The One Feature Per Day "Manifesto"