Structure by idea, not by time.
List of problems I want to grapple with.
Empty here for new. Need to brew some more.
Gotta catch them all!
A good strategic process requires tools that enable that process. I believe in text. I believe in named documents. I believe in the web. I like how I’ve built this page.
But this page is not enough.
play.teod.eu is optimized for my writing. I don’t want to do strategic work alone. I want a dynamic interactions with others. I want us to remix ideas collectively.
Org-roam provides indexing capabilities for play.teod.eu. For now. But I’m not really using that much of Org-roam:
And I’ve written a mapping from Org-roam id:...
links to stuff that works for HTML
myself.
And “navigate to file via title” and “link to page by UUID & name” doesn’t work for more than one site. I want interlinked sites.
teod/dbx: a toolkit for building your own personal
knowledge base is the tool I hope to shell out to for this. Create a
tiny dbx
wrapper for Emacs. A tiny dbx
wrapper for VSCode.
But who can I work with for this? Perhaps just test with Sindre? Probably a good idea.
Could be nice to pair on too — we do have a plan to do continuous pairing.
Ever since I went into IT in 2019, I’ve felt shackled by the time horizon of the teams I’ve been working with. Where is the long term thinking? For Unicad, it’s vital that we’re able to work with what matters long term. Research is a better analogy for much of what we do than “coding stuff”.
See also: https://cutlefish.substack.com/p/tbm-3052-why-do-we-have-no-strategy
See also: Why don’t we have a strategy?
New relevant page: OGGPOW: A non-coercive strategic framework.
What? Problem? Are C and OpenGL problems?
Well, not really. But there’s stuff here I want to learn.
What specifically?
Which I can get with Mathbox. Hmm. Hmmmmmmmmmmmm.
THAT WOULD BE NICE.
A new developer arrives. We want to:
We build our knowledge as a language. We prioritize its words. For those words, we write motivating essays.
Welcome, knowledge worker! - I gave this to some people, and I think it helped a bit.
Case: I want to create “intermediate” pages for remote references. But I don’t want the to create confusion about what the canonical page for something is. How can I achieve that?
Ideally, there’s some HTTP / HTML stuff. A W3C spec or something. “Please do not treat this page as canonical”. I want to ask Sindre, Oddmund, Richard and Sean about this.
Right now, they are lumped in with “seeds”.
I honestly cannot be bothered to maintain links to specific article IDs. Especially before I’ve shared them for public consumption. Meaning “Ready for comments” and above.
2022-09-17 FIxed!
2023-01-14
I can’t remember what shis problem was. Vague description! Ah well, done is done. Apparently I fixed it.
p
and teod_fzf_cd
to babashkaHere’s the ZSH code:
teod_fzf_cd () {
root="$1"
depth="$2"
folders=$(cd "$root" && find . -mindepth "$depth" -maxdepth "$depth" | sed "s|^./||g" | sort )
folder=$(echo "$folders" | fzf)
cd "$root/$folder"
}
Why babashka?
cd
doesn’t work.2022-09-17 probably don’t want to do that.
2022-09-25 this is a special case of dbx!
I want to make eu.teod/dbx: a toolkit for building your own personal knowledge base instead.
Closing!
2023-01-14 yeah, this doesn’t have to be done
It works as it is, no need to move to babashka.
Possibly store.teod.eu
.
Why?
“Personal information architecture”
2022-09-17 I haven’t had much need yet.
Just plaintext is nice. But it limits interactivity.
2022-09-25 Closing this one.
Morn.
Possible actions.
ACTION TIME
dump
doing
yes – need to build those skills
yes – then I actually see the stuff I’m making.
Yes! I did. this was rewarding.
raw sql
CREATE TABLE files (
file UNIQUE PRIMARY KEY,
title ,hash NOT NULL,
NOT NULL,
atime NOT NULL
mtime
)
CREATE TABLE nodes (
id NOT NULL PRIMARY KEY,
file NOT NULL,
level NOT NULL,
NOT NULL,
pos
todo ,
priority ,
scheduled text,
deadline text,
title ,
properties ,
olp ,FOREIGN KEY (file) REFERENCES files (file) ON DELETE CASCADE
)
CREATE TABLE aliases (
NOT NULL,
node_id
alias ,FOREIGN KEY (node_id) REFERENCES nodes (id) ON DELETE CASCADE
)
CREATE TABLE citations (
NOT NULL,
node_id NOT NULL,
cite_key NOT NULL,
pos
properties ,FOREIGN KEY (node_id) REFERENCES nodes (id) ON DELETE CASCADE
)
CREATE TABLE refs (
NOT NULL,
node_id ref NOT NULL,
type NOT NULL,
FOREIGN KEY (node_id) REFERENCES nodes (id) ON DELETE CASCADE
)
CREATE TABLE tags (
NOT NULL,
node_id
tag ,FOREIGN KEY (node_id) REFERENCES nodes (id) ON DELETE CASCADE
)
CREATE TABLE links (
NOT NULL,
pos source NOT NULL,
NOT NULL,
dest type NOT NULL,
NOT NULL,
properties FOREIGN KEY (source) REFERENCES nodes (id) ON DELETE CASCADE
)
CREATE INDEX alias_node_id ON aliases (node_id )
CREATE INDEX refs_node_id ON refs (node_id )
CREATE INDEX tags_node_id ON tags (node_id )
What about the Emacs lisp source?