21 Matching Annotations
  1. Nov 2022
    1. The lowest strata represents Generative ambiguity. Here, words are used as symbols for ideas that are very hard to express; an individual gives a name to a nebulous collection of ideas or thoughts. They struggle to make this approach make sense to others.

      Generative ambiguity is the process of giving names, potentially tentative, to a nebulous collection of nascent and unclear ideas in an effort to help make sense of them both to themselves as well as others.

  2. Aug 2022
    1. Title for My Book

      It's tough to do your own marketing and naming is hard. If you have an obscure short title, be sure to have a sharply defined subtitle, both for definition but to hit the keywords you'll want for discovery and search (SEO) purposes. Though be careful with keyword stuffing, if for no other reason than that Luhmann had a particularly sparse index.

      Zettelkasten doesn't have much value for for native search (yet). Who besides a student that doesn't really want to buy it searches for a book on note taking?! Creativity, Productivity, and Writing are probably most of your potential market, so look at books in those areas for words to borrow (aka steal flagrantly). Other less common keywords to consider or throw into your description of the book, though not the title: research, research methods, literature review, thesis writing, Ph.D., etc.

      Perhaps you've limited the question Scott. Instead ask everyone: What title would you want to see on such a book that would make you want to buy and read it? Everyone should brainstorm for 3 minutes and write down a few potential titles.

      I'll start:

      Antinet Method: Thought Development for Creativity and Productive Writing

      Antinet Zettelkasten: A Modern Approach to Thought Development

      Antinet: The Technique of Unreasonably Productive Intellectual Work (and Fun) [h/t F. Kuntze]

      Mix and match away...

  3. Jun 2022
    1. Are there relevant IPs buried in other projects you’ve worked onin the past?

      Sadly, I've already forgotten his self-defined version of IP and I can only think of intellectual property. Is footnote mention linking it to intellectual property certainly didn't help things.

      This is part of why using popular acronyms that aren't descriptive or clever is a bad naming practice.

    Tags

    Annotators

    1. Douglas Adams noted, "Capital letters were always the best way of dealing with things you didn't have a good answer to."

      from Dirk Gently's Holistic Detective Agency

  4. Oct 2021
    1. serverFetch name is unclear. That the docs need to say in bold that it's external is a bit of a code smell.
    2. Rename to externalFetch. That it runs on the server is already implied by it being located in hooks
  5. Sep 2021
    1. I feel like app/packs (or something like it) is a good name because it communicates to developers that it's not just JavaScript that can be bundled, it's also CSS, images, SVGs — you name it. I realize what can be bundled is wholly dependent on the bundler you use, but even esbuild supports bundling CSS. So couldn't this possibly be confusing?
  6. Mar 2021
  7. Feb 2021
    1. Unlike naming children, coding involves naming things on a daily basis. When you write code, naming things isn’t just hard, it’s a relentless demand for creativity. Fortunately, programmers are creative people.
    2. If we renamed things more often, then it probably wouldn’t be so hard to name them in the first place.
    3. We also find it hard to agree on what good names and bad names look like, which makes it hard to know when renaming improves a name.
    4. This is funny because it’s unexpected. Cache invalidation sounds like a hard thing, while naming sounds more straightforward. The joke works because it violates our expectation that hard things should be technical. It’s also funny because it’s true.
    5. Anyone who has ever tried to name a child knows that naming is hard. Naming things in code is harder. It’s bad enough that you have to commit to a name that someone isn’t going to like. You also have to be able to live with it.
    1. There’s only one hard thing in Computer Science: human communication. The most complex part of cache invalidation is figuring out what the heck people mean with the word cache. Once you get that sorted out, the rest is not that complicated; the tools are out there, and they’re pretty good.
  8. Dec 2020
    1. Maybe something more neutral just meaning a virtual element / no-element container would better express the intention? And regarding the syntax, maybe it would also feel less repetitive / boilerplaty than <svelte:slot slot="name" />... Maybe something like <svelte:fragment slot="name"> or <svelte:virtual slot="name">?
  9. Oct 2020
  10. Sep 2020
  11. Mar 2020
    1. Don't be discouraged when you get feedback about a method that isn't all sunshine and roses. Facets has been around long enough now that it needs to maintain a certain degree of quality control, and that means serious discernment about what goes into the library. That includes having in depth discussions the merits of methods, even about the best name for a method --even if the functionality has been accepted the name may not.

      about: merits

  12. Dec 2019