Here Kaiser touches on the broader themes inherent in the concepts of atomic notes, which might be used to build up new and interesting structures. He doesn't specify the "size of a note" nor does he say that one will "know it when they see it", but he's suggesting something very close to it.

Rather than define the appropriate size, a feat which is difficult to do at best, he's providing a very narrow set of benefits for encouraging one to cut things down to size as they index them: small pieces are easier to use to build new things.

Andy Sylvester says his engineering type of notes don't fit with the concept of atomic note. A 'how to solve x' type of note would fit my working def of 'atomic' as being a self-contained whole, focused on a single thing (here how to solve x). If the summary can be its title I'd say it's pretty atomic. Interestingly in [[Technik des wissenschaflichen Arbeitens by Johannes Erich Heyde]] 1970, Heyde on p18 explicitly mentions ZK being useful for engineers, not just to process new scientific insights from e.g. articles, but to index specific experiences, experiments and results. And on p19 suggests using 1 ZK system for all of your material of various types. Luhmann's might have been geared to writing articles, but it can be something else. Solving problems is also output. I have these types of notes in my 'ZK' if not in the conceptual section of it.

Vgl [[Ambachtelijke engineering 20190715143342]] artisanal engineering, Lovelock Novacene 2019, plays a role here too. Keeping a know-how notes collection in an environment where also your intuition can play a creative role is useful. I've done this for coding things, as I saw experienced coders do it, just as Andy describes, and it helped me create most of my personal IndieWeb scripts, because they were integrated in the rest of my stuff about my work and notions. Vgl [[Vastklik notes als ratchet zonder terugval 20220302102702]]