anchor.diff:  
   That’s it! This technique can substantially reduce your startup time during development, particularly as the number of dependencies you load increases.
   
  -== Using a :dev alias
  +== Using an alias for development
   
  -In a deps.edn project, you should create a `:dev` alias for use only during development that includes the `classes` directory:
  +In a deps.edn project, you should create a development alias (like `:dev`) that includes the `classes` directory:
   
   [source,clojure]
   ----
  
positive.code: (compile ‘my.namespace)    ;; writes .class files to *compile-path*
  ----
  
  Subsequently, when any of those compiled namespaces is required, the class file will be loaded, rather than the original `.clj` file. If a source file is updated (and thus newer), it will be loaded instead. Periodically, you will need to re-compile to account for new dependencies or changing code.
  
  One special case is the `user.clj` file loaded automatically by the Clojure runtime, before any other code is loaded. If you are using a `user.clj` in dev, you need to force a reload because it has already been loaded automatically:
  
  
negative.code: user=> (compile ‘my.namespace)
  ----
  
  == Incorporating user.clj into your development alias
  
  If you want to use an automatically loaded user.clj, you should incorporate that into your dev alias by adding a source path `dev`:
  
  [source,clojure]
  ----
  