Scripts I wrote that I use all the time
I've written a number of little scripts over the years, many of which I use every day. Here's a little collection.
I'm Evan Hahn, a programmer.
Visit evanhahn.com → RSS feedOn Hacker News May 2022 – Sep 2026
Web & Frontend 3Tools & Productivity 3Software Engineering 2Programming Languages 2Security & Privacy 1Open Source 1
I've written a number of little scripts over the years, many of which I use every day. Here's a little collection.
Know how good your code needs to be for the task at hand. Start with a rough draft. Try to soften requirements if you can. Don't get distracted. Make small changes. Practice specific skills.
It seemed like a great idea at first.
I prefer strict tables in SQLite because they avoid some datatype problems, such as putting text in number columns.
Reflections on a decade of configuration files.
How do the sizes of local LLMs compare to the size of offline Wikipedia downloads?
setTimeout breaks after 25 days. setBigTimeout doesn't.
If a single programmer builds something, it can be hard for others to maintain later.
I set all of Vim's configuration options, and I still feel far from mastery. But I did learn that it used to be called Vi IMitation...
From my experience, people like functions like "map" and "filter", but not "reduce".
I maintain a sorta-popular open source package, and I want to prevent big corporations and "bad guys" from using it. I want feedback on how to do this.
I got it working with arrays and records, but couldn't make it work for regular objects.
It takes 67 bytes to make one black pixel. How does it work?