I never remember what plastics I can recycle and what I can’t; this is a handy reminder.
]]>I’m a huge fan of people who dive into arbitrary corners of pop culture in insane amounts of detail.
Therefore, I couldn’t be happier to have found this deep dive into the ending of The Sopranos, inspired by the discussion of the scene found in episode 462 of The Incomparable podcast.
Bless all these nerds. ❤️
]]>This is cool. Coming to you from The Village. 😎
(via Tim Ferriss’s 5-Bullet Friday newsletter)
]]>our lives are
held together with
thoughts of where
we might be tomorrow.
And of disappointed
yesterdays.
(via Tim Ferriss’s 5-Bullet Friday newsletter)
]]>I’ve been looking for guides for how to do .NET development in Vim, because Vim has long appealed to me for a variety of reasons too esoteric to get into right now. And, despite it being what I’m using to write this post, I’m hungry to get away from Visual Studio Code and its “I’m secretly Javascript running on Chrome don’t tell anybody”; I mean, I’ve used WAY worse web-simulacra-of-native-apps (I’m glaring at you, Descript), but still. Code is a little janky (for some reason, File > New Window
doesn’t seem to work anymore) and I don’t need my text editor to swallow 2GB of RAM when I’m not using it.
ANYWAY, I’m bookmarking this article because it looks helpful. Actually, Rudism.com just looks all over like the kind of site I want to have. So, also bookmarked for inspiration.
]]>Someday. Yes, someday. Someday I’m going to spend a lot of money on a mechanical keyboard. …Probably this one. This guide is a good quick-reference that summarizes some of the many, many, ridiculous number of options available. 😂
]]>“The most important thing to remember is this: To be ready at any moment to give up what you are for what you might become.”
— W.E.B. Du Bois
(via @patrickrhone)
]]>Great little essay by Patrick Rhone, making the argument against relying on a piece of software to hold your journal:
The history of computing has copious evidence to back me up on that bold statement. The evidence shows that Day One (who I will note bills themselves as a “journal for life”) will likely be long gone in 20 years (Go ahead and bookmark this post and come see me then if I’m wrong).
Maybe when the company dies they’ll give you an exit plan to save your work or maybe they won’t.
Day One is a great app, but I’ve been wanting to move away from it for a long time. Partly to get out from under one more silo—right now, my journal is in their app, on their servers… it doesn’t feel under my control.
I’d rather have whatever I write be in plain text—like the source of this post that you’re reading. Even then, being able to read write I wrote decades from now depends on the bits that make up this post persisting, being available, being readable… and the history of computing has not borne out the likelihood of that.
Couple things I don’t have an obvious replacement for:
Neither of those are insurmountable, even in a hardcopy journal! The lure of convenience keeps me tied to an app. Hopefully not until it’s too late to leave.
]]>I’ve added this to my workouts to start building the strength and stability I’ll need to do full overhead presses eventually. Bookmarking for ease of reference.
]]>^ + `
dotnet-sdk
caskionide-f#
extension, but its website feels outdated, like it talks about needing Mono to get F#, which I’m pretty sure isn’t true. I want to do the most minimal and most up-to-date thingdotnet --help
includes “Additional commands from bundled tools”, which includes fsi
, but fsi
is not a command on my path currently. So I have to figure out how to execute it… (I wonder if Homebrew Cask installed it, but only put dotnet
in my path…)dotnet fsi
😏> Failed to install ctrl-c handler - Ctrl-C handling will not be available. Error was:
Could not load file or assembly 'Mono.Posix, Version=2.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756'. The system cannot find the file specified.
printfn "Hellow World!";;
, it obediently prints it, and its evaluation that val it : unit = ()
> dotnet fsi ~/dev/dotnet-projects/fsharp/test.fsx
^C
did indeed terminate the interactive prompt#
, e.g. #quit
quits the promptIonide-fsharp
- “This extension is recommended based on files you recently opened”, I reckon that’s a good sign.
F#:
, but if you type F#:
into the bar, it ignores the non-alphanumeric characters and finds every fucking command with an F in it, and of course the F#, perhaps because they’re newest, are all at the bottom of the list 🙄i
, and when I typed i
elsewhere (to assign the value as one of the values in a tuple), VSCode’s default Intellisense helpfully suggested “inference” instead of the, you know, actual symbol…~/dev/dotnet-projects/fsharp
fsharpi
Time Passes…
.fsx
(I’m saving it in the project’s directory, I don’t know if this is required, or if it’ll parse any FSX file)