diff --git a/docs/developers-guide.md b/docs/developers-guide.md
index 648ead707ef15738bea525dcaf4e440430b0ec4c..498a7d91466d58355c7dea0ca69f9077f5316f45 100644
--- a/docs/developers-guide.md
+++ b/docs/developers-guide.md
@@ -211,12 +211,54 @@ yarn run test-karma-watch # Watch for file changes
 ```
 
 ## Backend development
-Leiningen and your REPL are the main development tools for the backend.  There are some directions below on how to setup your REPL for easier development.
+Leiningen and your REPL are the main development tools for the backend. There are some directions below on how to setup your REPL for easier development.
 
 And of course your Jetty development server is available via
 
+    lein run
+
+To automatically load backend namespaces when files are changed, you can instead run with
+
     lein ring server
 
+`lein ring server` takes significantly longer to launch than `lein run`, so if you aren't working on backend code we'd recommend sticking to launching with `lein run`.
+
+### Building drivers
+
+Most of the drivers Metabase uses to connect to external data warehouse databases are separate Leiningen projects under the `modules/` subdirectory. When running Metabase via `lein`, you'll
+need to build these drivers in order to have access to them. You can build drivers as follows:
+
+```
+# Build the 'mongo' driver
+./bin/build-driver.sh mongo
+```
+
+(or)
+
+```
+# Build all drivers
+./bin/build-drivers.sh
+```
+
+The first time you build a driver, it will be a bit slow, because Metabase needs to build the core project a couple of times so the driver can use it as a dependency; you can take comfort in the
+fact that you won't need to build the driver again after that. Alternatively, running Metabase 1.0+ from the uberjar will unpack all of the pre-built drivers into your plugins directory; you can
+do this instead if you already have a Metabase uberjar (just make sure `plugins` is in the root directory of the Metabase source, i.e. the same directory as  `project.clj`).
+
+### Including driver source paths for development or other Leiningen tasks
+
+For REPL-based development or when running other Leiningen tasks you can add the `include-all-drivers` profile to merge the drivers' dependencies and source paths into the Metabase
+project:
+
+```
+# Find out-of-date dependencies for the core Metabase project and all drivers
+# (Assuming you have the lein-ancient plugin in your ~/.lein/profiles.clj)
+lein with-profiles +include-all-drivers ancient
+```
+
+When developing with Emacs and CIDER sending the universal prefix argument to `cider-jack-in` (i.e. running it with `C-u M-x cider-jack-in`) will prompt you for the command it should use
+to start the NREPL process; you can add `with-profiles +include-all-drivers` to that command to include driver source paths, which will let you work on the core Metabase project and all of
+the subprojects from a single REPL. :sunglasses:
+
 
 #### Unit Tests / Linting