2,034 karma · joined August 20, 2019
(/s but you never know especially these days)
Passwords+TOTP have that universality going for them that you can always move away to a different password manager/do without one if you ever want. With vaultwarden and that dependency/liability cut off, passkeys have phenomenal UX, especially coupled to a SSO/identity provider like pocketId.
I feel for them because I wouldn't mind paying 2/3 times the price for something of measurably higher quality and durability, but it takes effort and dedication to accomplish that as a customer. Effectively the market is saturated with premium-branded items that are marginally better or sometimes worse (a lot of what you see as "technical clothing" comes across that way at least), you feel gaslit by marketing, fake reviews and astroturfing campaigns, and there are only so many deceptions, defeats and financial losses you can sustain before going back to the devil you know: the default everyone else is buying.
Sheesh, I wonder why.
I'm with you on LLMs being in a different league than good developers curating a fine design with attention to detail, soundness and maintainability. It's just that 1- not all software/components within require that same amount of care: many capabilities are already commodified (as library code or boilerplate, or frameworks, or prior art in the training data that LLMs could easily parrot), and 2- till now, the financial calculus was leaning strongly towards "new developments are expensive, let's use restraint" (irrespective of the actual effort/ratio of commodified code).
So long story short, I don't see LLMs taking out skilled and caring developers: I'll still be reaching out to them for the critical/strategic projects, but on the other hand, I appreciate that the "ancillary" or "fancy" stuff can be cobbled together with the LLM glue gun and remove the impression to my management that engaging with software development is necessarily a costly/risky/exposing endeavour. Some software is to be treated like pets and cherished, and the new reality is to accept that we might have cattle software too, with swaths of prototypes, one-off's, very specific and niche and disposable, and it's fine because this no longer represents an unsustainable financial burden (my bean counting management already likes to kill useful software on a pure spec-sheet matching exercise and shovel everything into large "do it all" systems like ERPs: the fewer things the cheaper, right? Except for those underrepresented users thrown under the bus and their effective productivity).
I think I am, because I want my referenced notes to be typed. And the depth and accuracy of those types defines the extent of the knowledge being keept track of, considering that it also evolves and morphs over time. If I don't care to have categories of notes that I comprehend (Persons, Projects, Vehicles, …) and curated and up-to-date properties for them, I don't even know what kind of content is there and what kind of queries/answer I can expect out of my PKMS. I want determinism on a formal, fundamental level.
We probably have that in common that I went through a pretty long and exhausting journey of looking for the right note-taking app/PKMS, but while I started with the conviction that I needed an outliner, I landed elsewhere.
I do appreciate the theoretical beauty of "everything is a block" (and for the record, that is approximated pretty closely in Trilium by "(almost) everything is a note"), but the execution is often messy (tags/models hierarchies are hard to build and keep consistent/up to date, there is always the duality between embedding and referring because sometimes a sub-block is a block, and that forces you into defining more types or risk losing context and not being able to find the note but by name, if you can even remember it, etc). Tana and its "supertags" comes pretty close to the perfect outliner because it has a convenient UX around all those pain points, but I find it exhausting to use over time/as the PKMS grows.
I think Trilium saves me from a lot of cognitive burden by keeping the shape of the notes collection explicit and visible at all times (via its hierarchy). Also for the record, I'm not trying to brainwash you, only describing that there is a journey into and out of outliners :-)
Personally, I'm not interested, but to each their own.