Explore >> Select a destination
|
You are here 
|
beets.io | ||
| | | | |
oldmoe.blog
|
|
| | | | | Introduction Recently, I have been working on a project that dealt with large sets of latency measurements. For these, I always needed to capture percentile values (e.g., p50, p95, p99, etc.). Since I was working with SQLite, I naturally used the stats extension to calculate those percentiles, which worked OK until it didn't! I realized... | |
| | | | |
blog.miguelgrinberg.com
|
|
| | | | | miguelgrinberg.com | |
| | | | |
blog.pecar.me
|
|
| | | | | What you need to know before putting SQLite in production | |
| | | | |
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. | ||
