#107 What trigger me when using Azure Databricks notebook

During my time working with Azure Databricks notebook, I figured out that going with intuition is awesome, but in some cases, it actually makes life easier to have a good pool of information to make better and more sensible decisions. Here are some lessons learnt from my own experience interacting with Azure Databricks notebooks.

The real need to get the vocabulary right

Looking at this screenshot below, what do you call that rectangle box?

It’s up to you to decide to choose either “+Code” and “+Text” to call it a code cell or text cell or command cell for both cases. It’s not a command line, not a command block, not even a command. Yep, I encountered the same mistake not once, but several times. Let’s try to sound professional, shall we? 😂

Be mindful of choosing that programming language

We all know that a broad range of coding language options is offered in Databricks notebook. What triggers me sometimes is that later on, during the development process, I start regretting my fast-paced choice, which sometimes was a bit too late to modify due to a tight deadline. All I could do was suffer from the pain of my own choice and try my best to fit on a real tight pair of jeans. What a traumatising experience!

So, here are some analyses before jumping straight to write your poems in the code cell: