4 ms·

I understood fine. The problem is trying to formalize "ad hoc" versus "production development" practices as if they're meaningful. There isn't some golden trut

I understood fine. The problem is trying to formalize "ad hoc" versus "production development" practices as if they're meaningful. There isn't some golden truth of software development that analysts are too lazy to learn and implement. There's the problem and then there's solutions. Complaining that Jupyter-based development doesn't adequately accomdate version control or some other whistle commonly used in software development is some peak developer entitlement.

otabdeveloper4 5y ago
Your boss will eventually ask to make your "ad-hoc" stuff "production". At which point you'll dump the hot mess in somebody else's lap, and the whole thing will be rewritten from scratch. If that's your thing, then go for it.
- throwaway894345 5y ago
  That’s fine. Why waste time productionizing something that may or may not ever go to production? We do this all the time. Do you think Tesla built a whole fully-automated factory to build its first proof-of-concept car?