A place to keep track of things I’ve learned. Inspired by Simon Willison’s TILs.
All thoughts, opinions, etc. expressed herein are strictly my own and not of my employer’s.
Consulting available under the business name Siilikuin. For inquiries please email my first name at siilikuin.com.
Comments at the bottom of every page, including this one - check it out!
I have a suspicion - and let me be clear, that’s all this is, a suspicion, I am taking my own claims even more lightly than usual here - that Claude Code makes most people’s lives better, but it makes the lives of those who struggle with executive function much better. When I have a problem to solve nowadays, I type c, then Enter. This alias opens up a fresh tmux window with 4 separate instances of Claude Code. Then I just… pick one and describe the problem I’m thinking about, and hit Enter again. The loop begins, and suddenly I am collaborating alongside the closest thing to an IRL deus ex machina I’ve ever seen, for the cost of a few keystrokes. ...
I use Claude Code. I like Claude Code. According to Steve Yegge’s Eight-Circuit Model of Claudesciousness, I’m a pretty solid Stage 6, edging into 7 on heavy days. I think most engineers, most of the time, can get most of their work done faster with one of these tools than not, although the force multiplier of that speedup is probably not as extreme as it is in my case. Why is that? ...
Lua and Scheme occupy curiously similar places in my noggin, becuase my primary use case for both has been as scripting languages embedded into other, larger projects. Lua of course is basically designed for this job, but it’s a solid intermediate format to target even if you have no immediate intentions to use the programming language parts at all. A TSV file like 1 2 10.0.0.5 192.168.1.1 80 tcp 10.0.0.6 192.168.1l.1 443 tcp can be given a lot more structure on the cheap by writing a small transpiler of sorts to turn it into ...
1 2 3 4 5 File Explorer drag & drop ########## (112 MBps) Copy-Item ####### (82 MBps) Built in SFTP client ###### (70 MBps) Built in robocopy (/MT:32) ## (25 MBps) WSL 2 rsync # (13 MBps) In table form: Tool Speed (MBps) Difference Drag and drop ~112 — Copy-Item ~82 -27% sftp ~70 -37% robocopy (with /MT:32) ~25 MBps -78% rsync (WSL 2) ~13 MBps -88% I feel like I’m losing my mind. ...
As a teenager first getting into computers in the late 2000s I spent a lot of time reading old revered tomes like ESR’s The Art of Unix Programming and SICP . If present-day me were to isekai back in time and lose all of the technical knowledge I had but retain my current instincts, however, I would have left all of this on the table and just built a terrible new automation tool for the surprisingly scriptable MMORPG I was into in PHP 5, with as much disregard for clean code and security practices that I could muster[^1]. Then I would have put that tool online, continued to add new features to the ball of mud, and kept it running for 5-10 years before my first post-college interview. And then the vibe that would come across is less “He’s an egghead, and we like that, but we really need someone who actually does things” and more “He’s a meathead, but inside of that meathead is an egghead waiting to be revealed. We need this kind of junior dev yesterday.” I would have done this even though an objectively far superior tool had already existed for quite some time, making this project “feel like” dead weight in the wide world of software! But why? ...
I began running Andrew’s Selkouutiset Archive almost exactly two years ago, with a simple goal: Create a straightforward way for Finnish language learners to access the simple news broadcast by YYYY-MM-DD. It has basically accomplished that goal, with only a few tweaks here and there to keep everything running. Earlier in the series: Lessons learned from 6 months of operating a teensy-tiny news archive. I stand by those points, and have some more to add here at the 24-month mark. ...
The cozy world of DevOps has spoiled me with tools like Ansible, Terraform, and Packer. In the situations where I have a Linux machine already booted up, and sometimes already connected to the Internet, I can make things really easy on myself by slinging these tools in my usual way for repeatable, reproducible machines that may or may not come with the attendant headaches of immutable infrastructure (sorry, Nix, I’m not in love with you, I’m in love with the idea of you). ...
Most languages have at least one high quality textbook written for secondary learners of the language. (This is no guarantee that one will be able to read the language that textbook is written in, but English to X is quite common, and some intrepid textbook writers have solved this problem by writing the textbook in the very language it is being taught in, starting with the simplest possible phrases and moving gradually up in difficulty.) ...
I am an ardent capitalist. I am also an ardent Unix philosopher. I have long percieved there to be some interesting tensions between these two wolves inside me. The Unix philosopher in me wants my code to be as simple and flexible as possible, and - not always, but often - to minimize the number of lines of code I need to sling to solve a given problem.1 The capitalist in me wants to cover as many edge cases as possible, make every transition as smooth as possible, and apply as much napalm to the fire of user acquisition and douse its twin flame user churn in liquid death of another kind. What to do? ...