10 Ways to be a More Productive Java Developer
summary
Live code reload replaces rebuilds so a JSP and Java change shows instantly with hot reload and eliminates deploy waits, Gradle’s daemon shrinks repeated build startup, Spring Boot packages apps as run-as-jar with embedded Tomcat and metrics, Tomcat scores fastest in the server benchmarks shown, JBoss Forge scaffolds JPA entities and pages, Arquillian runs container integration tests from unit-style code, and the profiler surfaces an N+1 problem where a page issues 37 SQL calls for ten owners.
AI-written summary · about
chapters (11)
- 0:00Introduction and session overview
- 5:41Communication and team productivity
- 9:50Optimizing development processes
- 17:17Spring Boot for rapid development
- 25:10Gradle vs Maven for builds
- 28:41Choosing the right IDE
- 31:08JRebel for instant code updates
- 36:27JBoss Forge for scaffolding
- 43:22Performance testing and XRebel
- 55:33Arquillian for integration tests
- 57:43Summary and final advice
related talks
50m10 Ways to be a More Productive Java Developer
47m10 ways to get super-productive with Spring Boot
44mDeveloper Productivity Engineering: What's in it for Java Developers?
51mReal World Lean Java Practices, Patterns, Hacks, and Workarounds
51m5 Tips to Make Your Java Apps More Awesome!
41mStriving towards more productive development workflows
01h 10mSpring Boot and JRebel
44mJava, Life is Short!