Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Productive Java Development? You Weak Minded Fool!

Simon Maple
November 03, 2015

Productive Java Development? You Weak Minded Fool!

This session was given at JavaOne 2015

Developers shouldn’t work faster and more effectively; they should work harder. Too much energy is spent learning how to improve, and not enough is spent crushing every hour with manual repetitive tasks to get the job done. This tongue-in-cheek session takes a look at 10 development tools/projects/products—JIRA, Confluence, Tomcat/TomEE, JRebel, XRebel, Arquillian, JBoss Forge, IntelliJ, Jenkins, and Gradle—explaining what they do and how they “supposedly” help your development practices. Fear not, you’ll leave the session knowing what their vendors and project owners don’t want you to know about how they’re ruining your development environments and rotting your development projects from the core.

Simon Maple

November 03, 2015
Tweet

More Decks by Simon Maple

Other Decks in Programming

Transcript

  1. SIMON MAPLE @SJMAPLE VIRTUAL JUG FOUNDER LONDON JUG CO-LEADER JAVA

    CHAMPION JAVAONE ROCKSTAR REBELLABS AUTHOR ABOUT ME
  2. GEEKS REVEAL THE INDUSTRY'S BEST TECH 10 KICK-ASS TECHNOLOGIES MODERN

    DEVELOPERS LOVE Is geek love better than normal love?
  3. DON’T LOSE SIGHT OF THE GOAL Speed is not our

    goal Speed is a measure of how fast we reach our goal
  4. GRADLE A DECISION MAKER’S COMPARISON OF MAVEN, GRADLE AND ANT

    + IVY JAVA BUILD TOOLS: PART 2 Who will win "Least Annoying Build Tool"?
  5. JRebel maps a project workspace directly to your Running application,

    so that: - When a developer makes a change to any class or resource in their IDE the change is immediately reflected in the application, skipping the build and redeploy phases - Developers make a change, see it, approve it – in very fast development cycles JREBEL
  6. To test code changes, developers need to: 0 CODE CHANGE

    1 Compile, build, package 2 SSH/SCP/FTP to target machine 3 Redeploy the application 4 Restart the application server 5 Create state required to test your code change 6 TEST! 0 CODE CHANGE Remove the remote access Saving 1 hr/day/dev WITH JREBEL
  7. ARQUILLIAN Take your tests to the container Connect to that

    container View results like unit tests