Java is a simple and robust programming language. Unfortunately, one of the most vital parts of Java development—testing changes—takes longer than you think.
Studies show that the process of going from a code change in Java application development to seeing that change averages more than eight minutes – and is repeated several times an hour. This adds up to about 20% of a developer’s time.
Java developers go through four steps to make code changes: rebuild, server startup, redeploy, and test. Each step can take anywhere from just a few seconds to several minutes to complete, depending on the size of the application and the changes being made. Approximately one month if developer time is spent waiting for redeploys to complete on a yearly basis.
From the initial build, to server startup, to application deployment and testing, it’s critical to assess your own Java development process to determine how much redeploys are costing you. Even workarounds, such as bundling, create issues in determining the cause of problems and resolving them.
The assumption has always been that you can’t speed up the fundamental development redeploys. Until now.
Download the Hidden Productivity Killer eBook and learn: