All software is political, riddled with biases and potential security risks. Most of the time we ignore the policy of the software, because we either agree with that policy, or are conditioned not to clock it as a “policy”, because “this is just Common Sense™”.

I suspect, if the author would have been more honest with themselves, they’d write something along the lines of “turns out, software is a platform for political action, and it scares me” - an opinion that is very valid, valuable and thought-provoking.

Despite whatever your lead/manager says, there is always an option to nuke it from low orbit and start over.

As a programmer, I concur. I sit on my arse all day pushing keys , anybody can do that.

Handwriting has been proven to enhance learning in humans, so you are doing great by keeping the habit!

I don’t have much to recommend, but so far this little tool was very useful for me and my math studies: https://github.com/lukas-blecher/LaTeX-OCR

I am not a student, but I learn like a student all the time. I also enjoy handwriting (got an e-ink tablet for that) and knowledge management. I am often dreaming of a “perfect setup” where all I write gets pushed automatically through OCR into my knowledge vault (Obsidian, Logseq or whatever I/my peers happen to use). Even came up with a plan. I hope this new year will leave me enough energy to execute something useful.

Would you like to collaborate on that perhaps?

I’ve been toying with the same idea. Having Logseq running in server mode + creating an LSP adapter should be doable.

Knowing Typescript is enough to begin and start a career, you are sure to pick up relevant vanilla JS knowledge along the way. There is no way around JS: you’ll see it in tooling, debugging, building etc.

Of course you can really focus and grok everything way in advance, but I would argue it’s not necessary.

Yes, It takes it’s time indexing the graph - and you have to re-index periodically if you want you queries and graph to be in shape. I have a pretty mature KB, and this process takes no more than a few seconds, so it’s fine.

Honestly, I love everything about it, except for the app itself. It ties me to the default editor, which is an Electron-based sluggish resource hog. I’d rather have some software scaffolding to work in an editor of my preference, but that is just me. I suspect most people in most use cases won’t find it as problematic.

I second Logseq. FOSS, completely local, stores everything in text - works well with Git, lots of plugins - it’s almost perfect