This week’s assignments were very interesting, but certainly tricky in some spots. As seems to be the consensus for those posts I’ve read, I did prefer the Observable task over that in Colab, in part because Observable automatically implements changes made in one cell to all cells that use that information (i.e. no need to run cells after every change). I also attribute this to my preference of Javascript over Python (based on what little rudimentary experience I have with each, of course), as Python seems to have a greater complexity of variables in which I often find myself lost. I got bogged down in the Colab task trying to print the array for (external_file), but was eventually able to resolve the undefined variable error by running the functions above it. As it turned out, I hadn’t run the function to define “array,” so the print function wouldn’t work until I did so – hence my preference of Observable. Otherwise, I thought both assignments progressed rather fluidly and stacked concepts logically.
Assignments
<a herf=”https://colab.research.google.com/drive/17Khbqw90FX2CqKMP3xHqYBs56UNIHzRf?usp=sharing”>Colab Task</a>
<a href=”https://observablehq.com/@sfaeth/intro-to-observable”>Observable Task</a>
2 replies on “Module 3 Assignment”
Sent you an access request for the Colabs notebook, but the Observable notebook looks good. Yeah, Colabs can be a bit to juggle because Python often has longer-running processes that you don’t want to start until you’re ready. We’ll see this with the Module 4 assignments–it’s possible in Python to start a process that takes several hours to finish. This is really powerful because it means you can make Python do a lot that would take a human hours but you can set it and walk away from it, but it also means that you don’t want that process starting until you’re ready for it!
Both assignments look good!