11–18 of 18 posts
gless: https://github.com/tpapastylianou/gless it's such a tiny thing, but I can't imagine not having it on my machine. It's one of the first things i always download on a new system. PS. The morse thing sounds cool! Care to share?
Unsatisfied with built-in folder-based bookmarks, I made a tiny site in Flask where I could add links, along with comments and tags. I can then search any of these fields. I'm sure it exists somewhere, but it was a nice learning experience and I use it an awful lot. It's quite satisfying to see my "library" grow.
I miss delicious.
My local newspaper publishes a puzzle called "The Challenger" (where you guess what numbers in a 4 x 4 grid will add up to the totals at the end of each row and column). It frustrated me because there's no one right answer -- you were just supposed to start guessing numbers until you stumbled onto a sequence that worked. So I wrote a nice elegant program that crunched through every possibility (using 12 nested loops)…
`cfg pull` - pull latest git repo and apply via `stow`
`cfg push` - push local config changes to git server
`cfg apply` - apply local changes with `stow`
There are a few other commands too but I don't use them often. This simple script + repo lets me manage my dotfiles across ~7 machines
My local newspaper publishes a puzzle called "The Challenger" (where you guess what numbers in a 4 x 4 grid will add up to the totals at the end of each row and column). It frustrated me because there's no one right answer -- you were just supposed to start guessing numbers until you stumbled onto a sequence that worked. So I wrote a nice elegant program that crunched through every possibility (using 12 nested loops)…
There is a rule that lets you transform between valid solutions, right? What happens when you use that rule to help impose additional constraints onto the problem such that you are solving for a particular solution rather than a solution? I feel like that should sometimes let you choose pathologically transformed variants. For example - lets say you were stuck with eight and nine as your valid answers in a bottom left corner, but the constraints don't forbid nine. We ought to be able to pick nine in this situation under the logic that there will be a transformation rule which makes nine a valid solution. Such a choice means we are now solving for a particular solution - not a solution - because eight might have worked just as well.
In other words can you use the "do you know a related problem technique" to make your problem more specific?
I have an iOS shortcut that automatically re-builds and re-deploys a static site on Vercel at the start of every month. The site includes stats/visualisations for the current month, so the code finds the current month at build time and I just re-build it once a month. Completely unnecessary but it's pretty cool seeing that notification that my phone just re-deployed it for me :)