anchor.diff:  
   If the change improved build times, make it permanent. If you don't see an improvement, remove the change and try another.
   
  +== Update versions
  +
   [[update_gradle]]
  -== Update to the latest Gradle version
  +=== Gradle
   
   The Gradle team continuously improves the performance of Gradle builds.
   If you’re using an old version of Gradle, you’re missing out on the benefits of that work.
   Keeping up with Gradle version upgrades is low risk because the Gradle team ensures backwards compatibility between minor versions of Gradle.
   Staying up-to-date also makes transitioning to the next major version easier, since you'll get early deprecation warnings.
   
  -== Upgrade to the latest Java version
  +=== Java
   
   Gradle runs on the Java Virtual Machine (JVM). Java performance improvements often benefit Gradle.
   For the best Gradle performance, use the latest version of Java.
   
  -== Upgrade to the latest version of plugins
  +=== Plugins
   
   Plugin writers continuously improve the performance of their plugins.
   If you're using an old version of a plugin, you're missing out on the benefits of that work.
  
positive.code: - auto-complete method names
  
  [[dependency_resolution]]
  == Dependency resolution
  
  Dependency resolution simplifies integrating third-party libraries and other dependencies into your projects.
  Gradle contacts remote servers to discover and download dependencies. You can optimize the way you reference
  
negative.code: 
  == Inspect your build
  
  Before you make any changes, <<inspect.adoc#build_scans,inspect your build>> with a build scan or profiling. A proper build inspection helps
  you understand:
  
  - how long it takes to build your project
  