| function shuffle(tbl) | |
| for i = #tbl, 2, -1 do | |
| local j = math.random(i) | |
| tbl[i], tbl[j] = tbl[j], tbl[i] | |
| end | |
| return tbl | |
| end |
Last Updated: March 2023
IMPORTANT: Ignore the out-of-date steps below for getting Chromium keys.
Instead, read this up-to-date guide (Jan 2023) written by @LearningToPi.
P.S. Thank you to every contributor below who provided tips over the years on what should be a straightforward process: setting up Chromium for local development.
Long live the web!
UPDATE: I have baked the ideas in this file inside a Python CLI tool called pyds-cli. Please find it here: https://github.com/ericmjl/pyds-cli
Having done a number of data projects over the years, and having seen a number of them up on GitHub, I've come to see that there's a wide range in terms of how "readable" a project is. I'd like to share some practices that I have come to adopt in my projects, which I hope will bring some organization to your projects.
Disclaimer: I'm hoping nobody takes this to be "the definitive guide" to organizing a data project; rather, I hope you, the reader, find useful tips that you can adapt to your own projects.
Disclaimer 2: What I’m writing below is primarily geared towards Python language users. Some ideas may be transferable to other languages; others may not be so. Please feel free to remix whatever you see here!
| #!/bin/sh | |
| COMMAND="op read $OP_PIN_ITEM" | |
| echo "OK" | |
| while read cmd rest; do | |
| echo "cmd=$cmd rest=$rest" >&2 | |
| echo "cmd=$cmd rest=$rest" >> $LOG | |
| case "$cmd" in | |
| \#*) |