Notebooks as the be-all and end-all in fabric

Hi, I'm quite new in the world of working with data (at least professionally). I have been coding python for quite some time though, and have found that during my job there are little to no problems that I can't solve with python (expected), but also that python is a really simple tool that is easy to re-use. In my team I'm the only one who can really code, my colleagues use Excel and data pipelines to work with the data.

Now my question is (appart from the fact that I might be one of the only ones that can write python): are there any drawbacks of primarily using python (so notebooks) for all data collecting, handling, ...?

I'm currently not that far into the course, so excuse me if my question overlooks some obvious technicalities.

I'll be sure to come back to this topic at the end of the course.

I'd appreciate some real world examples of why python can be a suboptimal tool, inside the Fabric eco-system.

7 comments