News for hackers. Stuff that matters.
Re:Why Jupyter is data scientists’ computational notebook of... by ubernostrum on Wednesday October 31, 2018 @04:49AM (#18344118)
Show me the reproducible research in programming about the merits of different type systems (murky at best). Or of different approaches to testing. Or software architecture. Or... well, most of the stuff day-to-day working programmers actually do. There are barely even attempts at rigor in most of our practices, let alone the kind of reviewed and reproduced results we demand from the sciences.
Re:Why Jupyter is data scientists’ computational notebook of... by kazagistar on Wednesday October 31, 2018 @10:58AM (#18346206)
I run my unit and integration tests with every build, and they reproducibly pass if my code is working. If you have code, it doesn't take much to make it able to run again and get the same result, and it's frustrating to see Jupyter users mess it up.
Re:Why Jupyter is data scientists’ computational notebook of... by analog31 on Wednesday October 31, 2018 @01:53PM (#18347840)
In Jupyter, I do a "restart kernel and run all cells." While it's not to the level of test driven development, it catches the worst of the issues.