I’ve done the same thing and it works very well (deploying Django to Heroku). I get the mise en place metaphor, but it seems a bit stretched. The benefits of mi

I’ve done the same thing and it works very well (deploying Django to Heroku). I get the mise en place metaphor, but it seems a bit stretched. The benefits of mise en place seem to be reduced context switching and taking work (chopping vegetables) out of a more constrained time window (half the food is cooking) into a less constrained time window (before anyone shows up). That does apply here I think (readying for a new version). The big thing with working this way is the incremental jumps between working versions. If you try to switch from local fire storage to S3 and your assets stop loading, you have the problem somewhat narrowed. If you stitch together four tutorials, hit deploy and your assets won’t load your problem is… somewhere? Certainly a bigger search space. I’m not sure this maps that well to mise en place. This more about something like tasting while you cook.