Explore >> Select a destination
|
You are here 
|
nextjournal.com | ||
| | | | |
gouthamanbalaraman.com
|
|
| | | | | Some notes on profiling python code in the Jupyter notebook environment | |
| | | | |
www.ethanrosenthal.com
|
|
| | | | | I make Python packages for everything. Big projects obviously get a package, but so does every tiny analysis. Spinning up a quick jupyter notebook to check something out? Build a package first. Oh yeah, and every package gets its own virtual environment. Let's back up a little bit so that I can tell you why I do this. After that, I'll show you how I do this. Notably, my workflow is set up to make it simple to stay consistent. | |
| | | | |
stribny.name
|
|
| | | | | ||
| | | | |
pen.so
|
|
| | | After Apple's announcement, I ordered an M1 Mac Mini and canceled it when I noticed the non-upgradable RAM. I then reordered it (16G/1T), and it has just arrived today :grin: You've probably seen many online reviews (I watched tons of them on youtube) and what everyone says is true. It's fast! Pretty stable, and I can't hear the fan even while compiling. Looking at my geekbench you'll see it's the fastest machine I own, CPU wise, even more than my MBP 16" 2020. On the compute GPU level, it's slower, but ... | ||
