Comments by "Tiago D\x27Agostini" (@tiagodagostini) on "Stop Making THESE MISTAKES With BIG DATA" video.

  1. Well it is better that they do not get to production than if they got to production being unfit for it :)
    2
  2. The main cause of that is that ideally notebooks shoudl have some form of specialized version control. Git is problematic because it cannot differentiate automatically the CODE lines from the execution lines. THat result in frequent conflicts and makes everything painful.
    1
  3.  @jangohemmes352  Git is super problematic with notebooks because it does nto understand which lines are code and which are execution results (they are there intermixed). So when you make a pull over one of your own versiosn that was running in other data.. it nearly always result is HUGE number of conflicts and you spending half your day trying to fix it. We need a version control tool that knows how to handle notebooks safely, until then we need to believe everyoen using the notebook remembered to erase every single cell of execution before a commit and that is well like believing in santa claus
    1
  4.  @antoruby  Yes there are, but the more pieces you need to put in a system to work, the more chance something would go wrong. I really wish git had soemthing embedded for that in the sense that it ignores certain things in merges.
    1