This document discusses 10 ways for developers to be more productive. It recommends removing non-essential tasks, optimizing existing tasks, retaining valuable tasks, sharing knowledge across teams through communication tools like Slack, and using productivity tools like Atlassian, IntelliJ IDEA, JRebel, JBoss Forge, and Arquillian. The document emphasizes that speed should not be the only goal and developers should not lose sight of their overall goals.

1. 10 WAYS TO BE A MORE
PRODUCTIVE DEVELOPER
SIMON MAPLE
@SJMAPLE

2. SIMON MAPLE
@SJMAPLE
DEVELOPER ADVOCATE
VIRTUAL JUG FOUNDER
LONDON JUG CO-LEADER
JAVA CHAMPION
JAVAONE ROCKSTAR
REBELLABS AUTHOR
ABOUT ME

3. GEEKS REVEAL THE INDUSTRY'S BEST TECH
10 KICK-ASS
TECHNOLOGIES MODERN
DEVELOPERS LOVE
Is geek love better
than normal love?

4. HOW CAN WE IMPROVE OUR
PRODUCTIVITY?

5. PRODUCTIVITY i
Removing
non-essential
tasks

6. PRODUCTIVITY ii
Optimising existing tasks
2005
:o)
2015
:)

7. PRODUCTIVITY iii
Retaining awesome tasks

8. DON’T LOSE SIGHT OF THE GOAL
Speed is not our goal
Speed is a measure of how fast
we reach our goal

9. COMMUNICATION

10. COMMUNICATION
Sharing knowledge across a team

11. It isn’t just technology
that increases your productivity
COMMUNICATION

12. COMMUNICATION

13. SLACK
Group channels
Open door chat policy
Smart Integrations

14. ATLASSIAN TOOLING

15. ATLASSIAN TOOLING

16. TOOLING

18. DOWNLOAD &
INSTALLATION
TOOLING
SUPPORT
DOCS &
COMMUNITY

19. PERFORMANCE METRICS

20. PERFORMANCE METRICS

21. Your Ranking
0 11.75 23.5 35.25 47
Tomcat GlassFish JBoss Liberty Profile Jetty
JFOKUS 2015

22. FEATURES

23. FEATURES
NOW
JAVA EE 7
COMPLIANT

24. SPRING BOOT
Just Run Applications
Production Ready
Sensible defaults

25. SPRING BOOT IN ACTION
“Make JAR not WAR!”
— Josh Long (@starbuxman)

26. TOMEE
http://tomee.apache.org/

27. TOMEE
http://tomee.apache.org/

28. GRADLE

29. GRADLE
A DECISION MAKER’S COMPARISON OF
MAVEN, GRADLE AND ANT + IVY
JAVA BUILD TOOLS:
PART 2
Who will win
"Least Annoying Build Tool"?

30. GRADLE

31. GRADLE

32. INTELLIJ IDEA

33. INTELLIJ IDEA

34. INTELLIJ IDEA

35. WASTED TIME
XKCD.COM/303

36. JREBEL

37. 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 (avr)
1 hr/day/dev
WITH JREBEL

38. JREBEL IN ACTION

39. FREE STUFF!
0t.ee/jfokusjr

40. JBOSS FORGE
JAVA EE SCAFFOLDING
RAPID DEVELOPMENT
PLUGIN BASED

41. JBOSS FORGE IN ACTION

42. FAIL EARLY

43. FAIL LEARN EARLY

44. XREBEL
Profiler for Java Web Applications
Understand what is happening
behind your code
Find and fix issues

45. XREBEL IN ACTION

46. FREE STUFF!
0t.ee/jfokusxr

47. ARQUILLIAN

48. ARQUILLIAN
Take your tests to the
container
Connect to that container
View results like unit tests

49. ARQUILLIAN

50. ARQUILLIAN

51. ARQUILLIAN

52. SUMMARY
CARE ABOUT YOUR TIME
DON’T LOSE SIGHT OF YOUR GOAL
EXPLORE PRODUCTIVITY TOOLS

53. 53
FREE STUFF!
0t.ee/jfokusjr 0t.ee/jfokusxr