11 Matching Annotations
  1. Jan 2026
    1. Waarom ik nooit opruimde#Eerlijk? Omdat ik het niet meer overzag.Als je één map hebt met rommel, ruim je die op. Maar als je tien mappen hebt, op zes verschillende plekken, met allemaal dezelfde soort inhoud - waar begin je dan? Welke is de “echte”? En wat als je per ongeluk iets weggooit dat je nog nodig had?Dus startte ik iedere keer dapper met opruimen. En stopte dan weer net zo snel.

      tidying folders never happens bc you have no overview. (reminiscent of the beginning of setting up a GTD system)

  2. Oct 2024
    1. https://web.archive.org/web/20241017043750/https://alexwlchan.net/2024/static-websites/

      I like this idea of having static html as page to explore folders, I had that in the 90s to better search for image files. Author offers no clues as to how he uses the affordance it provides though, in terms of 'showing the metadata' they care for and the little bits of extra functionality. And I wonder about the effort involved when adding new files. Presumably new files are added manually too, otherwise it's not 'static html'. Stores files by year, type and first letter of file name. That makes no immediate sense to me in terms of finding things back. Then again I never understood why you would have folders for file types. It's like sorting items on the type of box it came in. Good example though of making your computer your own.

  3. Nov 2020
    1. Interaction with stable storage in the modern world isgenerally mediated by systems that fall roughly into oneof two categories: a filesystem or a database. Databasesassume as much as they can about the structure of thedata they store. The type of any given piece of datais known (e.g., an integer, an identifier, text, etc.), andthe relationships between data are well defined. Thedatabase is the all-knowing and exclusive arbiter of ac-cess to data.Unfortunately, if the user of the data wants more di-rect control over the data, a database is ill-suited. At thesame time, it is unwieldy to interact directly with stablestorage, so something light-weight in between a databaseand raw storage is needed. Filesystems have traditionallyplayed this role. They present a simple container abstrac-tion for data (a file) that is opaque to the system, and theyallow a simple organizational structure for those contain-ers (a hierarchical directory structure)

      Databases and filesystems are both systems which mediate the interaction between user and stable storage.

      Often, the implicit aim of a database is to capture as much as they can about the structure of the data they store. The database is the all-knowing and exclusive arbiter of access to data.

      If a user wants direct access to the data, a database isn't the right choice, but interacting directly with stable storage is too involved.

      A Filesystem is a lightweight (container) abstraction in between a database and raw storage. Filesystems are opaque to the system (i.e. visible only to the user) and allow for a simple, hierarchical organizational structure of directories.

  4. Sep 2020
  5. Apr 2019
  6. Mar 2019
  7. Dec 2018
  8. Nov 2017
  9. Nov 2014