Yes, the Data Science culture around maintainable code does seem to be reaching a critical level of toxicity (in some environments at least). In line with a ne

Yes, the Data Science culture around maintainable code does seem to be reaching a critical level of toxicity (in some environments at least). In line with a nephew comment of mine, I feel that bringing the immediate interactivity or iteration cycle of notebooks to the development experience would help a lot, and not be too bad a thing for common development either. I've heard of the related nbdev project, which seems like an interesting and compelling idea. But it'd be nice to see the reverse: something that makes ordinary python development more immediate than using a debugger/vanilla REPL.