Live coding 12

I just would like to reflect on two wonderful things I saw Jeremy do :slight_smile:

Copying notebooks when trying out a new idea

This is huge to the workflow! I have often suffered in the past because I would just redo the cell with new logic, and then find out I am having a hard time going back to the previous, working state (or state where I would get a better result!).

I sometimes would be rescued by committing often, but this gets messy and is not the real solution. The real solution is to mash that copy button :slightly_smiling_face: Which is what I have now started doing and I absolutely love it.

How to add functionality

When Jeremy started to implement something new (multi-task loss) and it was not working initially, he traced back to the simplest working state with a hint of the new functionality.

This was sooo good. This is precisely the formula for getting your ML code to run and do something interesting :slightly_smiling_face:

Just a reminder to myself on this :slightly_smiling_face: We often get lost in the heat of the action, but there is a methodical way of working on your code that makes a lot of sense to reach out for :slight_smile:

And I guess it sounds simple when watching Jeremy, but it is a little bit like watching a maestro play the violin. Yeah, simple. But take a violin in your hands and things don’t go that well from start :slight_smile:

It’s a gradual process! :smile:

5 Likes