personal_code

I remember sitting in the senior study lounge reading the previous Bishop book and implementing the perceptron from it, 22 years ago: https://github.com/llimllib/personal_code/blob/945b017b2915c... (before numarray and numpy merged!)

I use a little shell alias that drops me into duckdb with the file loaded into a table for interactive querying: https://github.com/llimllib/personal_code/blob/c1a74b1b9527f...

I keep mine in a github repository and wrote a little script to sync files in both directions: https://github.com/llimllib/personal_code/blob/6e86441d992ca...

For me, fd is as better than find as ripgrep is to grep The main benefits are: - it skips ignored and hidden files by default - it uses modern regular expressions - it has a more sane UI (`find . -iname '*.txt'` -> `fd -g '*.txt'`) I do use it in scripts as long as I know they're going to run in a context where it's available, ex: https://github.com/llimllib/personal_code/blob/c3d33b4d95f89...

I've found a use for APFS' copy-on-write cloned files. I like to work with git worktrees, and I work on an app that has a large (2 gb) node_modules directory. Previously, every time I made a worktree, I had to `npm install` to get a fresh node_modules, or copy the full directory, which was slow. $ time /bin/cp -r node_modules /tmp/node_modules /bin/cp -r node_modules /tmp/node_modules 1.98s user 58.26s system 63% cpu 1:34.17 total The -c option to /bin/cp on a mac is "copy files using clonefile(2)", making clones instead of full copies. It's still not super fast, but almost a minute less of waiting for the copy is a nice improvement: $ time /bin/cp -rc node_modules /tmp/node_modules_cloned /bin/cp -rc node_modules /tmp/node_modules_cloned 0.43s user 29.85s system 79% cpu 38.211 total The one downside is that GNU has an

That complaint was weird, here's my day 7 solution in zig built in release mode: $ time zig build-exe ./a.zig -O ReleaseSmall real 0m1.728s user 0m1.544s sys 0m0.292s Which is actually slower than running the entire solution in debug mode: $ time zig run a.zig -- input.txt min 337 342641 min 470 93006301 real 0m1.138s user 0m0.789s sys 0m0.270s Totally possible that it's much slower on the dev's machine, but if he's a VR developer it seems weird that he'd have a low-powered box. [1]: https://github.com/llimllib/personal_code/blob/master/misc/a...

"The straightforward and easy path was to join the proprietary software world, signing nondisclosure agreements and promising not to help my fellow hacker.... I could have made money this way, and perhaps had fun programming (if I closed my eyes to how I was treating other people). But I knew that when my career was over, I would look back on years of building walls to divide people, and feel I had made the world ugly." -- Richard Stallman (Open Sources, 1999 O'Reilly and Associates) https://github.com/llimllib/personal_code/blob/master/python...

I got up to exercise 1.18 in Haskell, and didn't have any problems with it. I knew very little haskell when I did it; I know less now. Doing the exercises in both Scheme and Haskell was a fun exercise; I should go back to it at some point. https://github.com/llimllib/personal_code/blob/master/haskel... edit: the excercise the author is talking about is 1.11; my answer starts on line 51. The haskell is pretty!

My pong game in 30 lines of nodebox: http://billmill.org/pong.html . Nodebox rocks; I used it more seriously to create all the EPS files for my article in python magazine about drawing trees. Here's an example; notice how short and to the point the code is, a credit to nodebox's super simple API: http://github.com/llimllib/personal_code/blob/master/python/...