brennen @brennen@mastodon.social

that feel when you type "ls" in a directory and then it hangs and you remember that it's actually a fuse mount from some cloud storage mechanism with a vast number of objects in it and you ctrl-c while hoping that nothing segfaults

as marketing exercises for companies i work for go, this is substantially better content than average: https://www.youtube.com/watch?v=OA4OsgxLPAQ

i think i like this guy:

https://www.douthitforcolorado.com/

i'm sure there's a metric fuckload of prior art here, but i'm sort of tempted to just rough something out in perl and sqlite.

(paging @natecull to tell me this should probably be some kind of universe-consuming grammar in an as-yet nonexistent language form well out beyond the conceptual boundaries of a bunch of CS concepts i don't grok at all.)

(4/4)

like, concretely, a utility that stashes a bunch of relationships in sqlite, say, and lets you say things like:

file path <-> vimwiki page
url <-> vimwiki page
file path <-> tag
file path <-> file path
git commit <-> url
url <-> tag
thing <-> date

for practical use, it could be kind of haphazard and lossy. you could link a ton of stuff and even if some links decay (because of course they do), you'd have meaningful structure emerge over time. 3/n

...or rely on things being in version control, or safely assume that you can drop a file into a directory, and so on.

and then how do you store notes? you can have a table in sql or what-have-you, but it's also really nice to just work with plain old files for so many purposes. there's no really satisfying compromise there.

but! if instead of trying for an absolutely perfect scheme, i just had a simple way to relate things to other things... (2/n)

so after work i went down to the distillery and had a couple of gin & tonics and thought about the note taking system that's been coalescing in my head for a couple of years.

i think i had kind of an epiphany, which is that what i should actually build is a little pragmatic collection of types of relationships between things, or something like that.

i'd been all worried about how hard it is to definitively annotate, say, file paths or URLs... (1/n)

every couple of years i think about that t-shirt and wish i knew where it had gone, but for some reason i haven't just, you know, found a sharpie and a t-shirt

i used to have this t-shirt that a local band made by writing "ethnic slurs" on a t-shirt and then x-ing it out in sharpie

third restart seems to be the charm.

cats are weird.

cat walks across keyboard, but i think that i've escaped any real damage until i discover that the `r` (for replace) key no longer works in vim.

_only_ in vim, mind, and a restart has no effect.

some haphazard notes on setting up a personal code repo: https://p1k3.com/2018/6/24/

the temptation, of course, is to write my own git repo viewer.

which would be a terrible idea.

terrible.

one of the afternoon's projects has been deciding what to put on https://code.p1k3.com/ - i think gitea is a pretty decent piece of software, after a few days of use (i appreciate little details like how it handles ssh access to repos and just stores them in a straightforward dir path), but i guess i'm also not exactly going to _commit_ to any one thing at this stage.

i think maybe since gitea is fairly sensible about where it stashes repositories, i can add another read-only view.

my strongly-worded-letter backlog is getting kind of out of control.

first of all, fuck no, and second of all you people sure are gonna get a strongly worded letter about this one.

this is delightful:

https://www.youtube.com/watch?v=2K49QKVR0p0

(superorganism tiny desk.)