Feels like what I do with Drafts/JS— solve problems programmatically. Maybe that’s a gateway to development beyond that stack; there’s only so much I can do in a text editor, however superpowered it might be…

Link to Odell’s “How to Do Nothing”

Hm. I wonder if there’s a difference here in poetry. Does design intend to be more legible than poetry? At one end of a spectrum, poetry can be wilfully obscure…

I think this is why I've enjoyed building keyboards in recent years. Steep learning curve for me (no background in electronics or C), but it's enough to know there's a solution for pretty much every problem I might encounter. It's an on-ramp to engaging with something like writing. It fosters the notion that there is a "solution", I just need to keep digging. Keyboard building as training for a resilient creative practice. Yes.

Yep. Same here. I’ve been working with my calendar as a log for so long I forget it’s not the way most people use calendars. Nice to read someone else who’s in the same camp.

This might be a useful place to visit, but I wouldn’t want to live here.

I get the value of being able to move quickly, to challenge comfortable, established wisdom and explore what else is possible on the road to new thinking or incredible ways of achieving things, but I also appreciate the value of slow work.

As I often find myself thinking: the truth lies somewhere between these two points.

I’d be interested in finding an opposing yet effective stance for this. This seems to be the way a lot of politicians are trained, but I’d like to believe there’s strength in being able to accept the valid points your opponent might be making while spotlighting exactly where your stance supersedes theirs. Is this just naïveté?

This presupposes that age brings wisdom or some meaningful shift in perspective. Bearing in mind my recent experiences in eldercare and supporting pensioners, I’m disinclined to agree (and I say that with all due respect).

I’ve never formally cultivated this. Something to investigate further? #followup

Much as I admire Obsidian, and a lot of people swear by it, I'm wondering how much more I can build Drafts up into being everything I might need for my PKM. I suspect that "success" here might be more to do with my workflow (and really grokking what I want to achieve) than the affordances of any particular app...

Personal Digital Biome?

At the moment, I guess I’m currently doing this in Drafts, but without any real rigour. What I’ve intended to do is host my atomic notes in iThoughts. But maybe this is part of my system that needs closer attention. Maybe there’s legitimate cause for another tool in the stack? Or maybe this just calls for another workspace? I think this is the space I wanted Project Meta to fill…

Fundamental value(s) of considered note-making = introspection, intellectual synthesis, connection...

Four years after I first found Hypothes.is, I still haven't worked it into my workflow. Posts like this rekindle the early sparks of interest I felt, though. I'm inspired to try it out again and see if anything's changed...

An alternative remunerative model that's based on payment for access to the knowledge network, rather than individual works? Who would then be responsible for paying out to individuals, in this model?

The biggest issue I have with iThoughts right now is the lack of ability to dynamically filter maps based on tags or other properties of nodes. I'd love to be able to view only the nodes I need for a specific query and have everything else dynamically vanish— particularly on large maps, where the existing method of filtering renders the nodes illegible...

That said, I've come to depend on text searches to return a filtered list of nodes. iThoughts allows for searching within a map and across all maps in the filesystem. It's not a fuzzy search, so search strings have to be constructed in a fixed way which necessitates a robust system of memorable tags, categories or conventions (for example, use of the tag "@due(2019-10-02)" allows me to filter for nodes with due dates, and nodes due within a specific year, month or on a specific date, by parsing incremental fragments of the tag. Simple, but effective.

A self-regulating system, with a built-in sanity check. The workflow itself contains a mechanism that encourages the question of "why" beyond "what". Useful consideration for workflow design, to guard against cruft...

This is akin to what I currently do with notes and references in iThoughts when reading digital documents...

Sounds familiar... ;)

And the counter-question: how much value is gained from a collaborative process, with efficiently compounded effort and gains from differing perspectives...?

The notes likely had value in the process of cementing comprehension, but less so for later recall/review or connectedness...?

It's possible that rss events only fire for notes...

This gives me cause to experiment with different models for office hours. I've already tried the hour long model. It would be interesting to try the 30 minute model described here— four x 30 minute meetings, back to back, every two weeks. And to perhaps complement that with a round table meeting every now and then?

Wait, what— Muji sells a mini lint roller?! WANT!!!