15 Matching Annotations
  1. Last 7 days
    1. File structure
    2. Collapsing directories Say some directories in a project exist for organizational purposes only, and you prefer not to have them as namespaces. For example, the actions subdirectory in the next example is not meant to represent a namespace, it is there only to group all actions related to bookings: booking.rb -> Booking booking/actions/create.rb -> Booking::Create
  2. Oct 2021
    1. power doesn't give up power easily. Power doesn't topple very easily. All of these organizers are working in tremendous conditions of uncertainty. 
  3. Sep 2021
  4. Jun 2021
    1. We’ve broken our project up into three different types of packages: apps which are preact apps intended to be bundled and deployed somewhere, modules which are plain npm packages for node/browsers and do not bundle their dependencies, and workers which are either Worker or ServiceWorker scripts entirely bundled up with no imports or exports. We don’t have to keep these three types of packages separated, but it helps us navigate around.
  5. Jul 2020
  6. May 2020
    1. Where I track capacity, appetite, & commitments. A place where I can stay organized while also allowing transparency for my teams & anyone else who is interested in what I’m currently focused on.

      "My Plate"

    1. However, please note the following: it will depend on how those subdomains are defined. Are they just subsections of a project that belongs together like help.example.com or blog.example.com (and many other possible arrangements that are part of one and the same setup)? In such a case, using the same policy is appropriate. Problems arise when completely different projects which have little to do with one another and whose data collection practices also differ so significantly that they require different privacy policies.
  7. Dec 2019
  8. burnsoftware.wordpress.com burnsoftware.wordpress.com
    1. Files are sorted by moving them all into a folder with today’s date, and you can organize these folders by day, week, or month.
  9. Oct 2019
    1. All of your main points are contained in the body, and normally this section is prepared well before you ever write the introduction or conclusion. The body of your speech will consume the largest amount of time to present; and it is the opportunity for you to elaborate on facts, evidence, examples, and opinions that support your thesis statement and do the work you have outlined in the specific purpose statement.

      Researching the topic is necessary before writing the body of the speech since you may be unaware of the most critical points.

  10. Aug 2017
  11. Jul 2015
    1. I agree with the conclusion that hierarchies and letting users put things in places is good, but I want to posit a more nuanced explanation than "we are set in our ways".

      I think sometimes we don't remember what exactly it is we're looking for. We may not have a word, or a name, or date. But if we put it some place in particular we can find it spatially rather than linguistically.

      This is why I think labels are superior to hierarchies. When we transcend the limitations of physical space would should not throw out space, but we should throw away the constraints of 3D space with its contiguous, volumetric forms. Labels let you put things in as many places as you like. Labels can, too, be hierarchical.

      The problem with the current crop of systems that eschew hierarchy is that they replace it with a text box.

      One could make the argument that smart indexing is just automatic labeling, but I think there's a memory function in having created the labels oneself.

      I'd like to see systems that experiment with more ways to fold space. Shortcuts are like wormholes. Maybe we should have common actions for creating bi-directional ones. On mobile devices I think we should take more advantage of zooming and z-planes.

  12. Dec 2014