3 ms·

So… macros? This is how it sounds to me.

• Jtsummers 4y ago
  No, more like: 1. Get a feature request. 2. Create a standalone program that does just that thing (pulling in, presumably, whatever is needed from the primary application(s), otherwise you're reinventing the wheel a lot). 3. Do V&V on this, use it, but leave the code alone. 4. Some time later, merge it with the primary application(s) (4) would usually require a refactoring/cleaning up to ensure a clean separation between UI and logic layers in the "snippet". Once done, the logic portion should be incorporable into other applications more easily because it's been converted into a library. I usually don't delay between (3) and (4), but take basically the same approach. Convert the primary application into a suite of libraries and the glue code between them and UI code (this is an ongoing process if it's a legacy application, this is what I try to do early on otherwise). Those libraries can be reused for a "snippet"/spike/whatever you want to call it to avoid reinventing the wheel. The new program is brought up, used enough to be confident in it (combination of testing and real-world use), then its logic is properly modularized (if it wasn't already) and reincorporated into the primary application. Repeat with the next thing. If all the necessary components are present, but not the glue/UI for it, then you can skip that process (or most of it) and just work on the main application.