If you are inspired during practical and hands-on sessions during the three days at Devoxx UK 2015, have you thought about how you might pass on this knowledge and experience to others? If so, then we have just the right solution for you! Running a Hackday, either at your workplace or within your local community, can be very rewarding. Come along to this session and learn all about the art of running hack session from Richard Warburton, author of Java 8 Lambda and regular organiser of hackdays in the London Java Community. You will be able to answer your own questions like: Why you should run a hackday ? What’s involved in running one ? Examples of successful hackdays Tips for being successful

1. How to run a Hackday
Richard Warburton
http://insightfullogic.com

2. Why you should run a hackday
What's involved in running one
Successful Examples
Pro Tips!

3. As a JUG
● Simple way to get developers enthused
● Good followup to talks/discussion
● Developers are usually pretty hands-on

4. As a Company
● Don’t want to release EJB 2.0
● Release a better product
● Encourage early adoption

5. As an individual
● Improve standards and APIs
● Support and Educate your peers
● Its fun!

6. Why you should run a hackday
What's involved in running one
Successful Examples
Pro Tips!

7. Why you should run a hackday
What's involved in running one
Successful Examples
Pro Tips!

8. What's Involved?
● Pick a target
● Find a space
● Get some help
● Just Do it!

10. Why you should run a hackday
What's involved in running one
Successful Examples
Pro Tips!

11. LJC Examples
● OpenJDK
● Lambdas (JSR 335)
● Date and Time (JSR 310)
● Websockets/Json (JSR 353/356)
● Java REPL

13. Why you should run a hackday
What's involved in running one
Successful Examples
Pro Tips!

14. Establish a goal
● Educate/Inform
● Send feedback to Spec Lead
● Find Bugs
● Fix Bugs
● Talk to Spec Lead / EG
about goals

15. Feedback
● Mailing Lists
● Issue Trackers
● Find out where they live/drink/speak!

16. ● Weekend
○ More time
○ Suitable when people need to explore
● Weekday
○ Less Commitment
○ Requires focus
Picking a Time

17. Getting a Venue
● Just Ask!
● Free marketing to a developer audience
○ Training
○ Consultancy
○ Recruitment
● Maintain a strong relationship

18. Communicate to Attendees
● Opening talk for attendees
● Get assistants to give help during the day

19. Communicate to Project Leaders
● Talk to professionals
● Follow OpenJDK guidelines for submitting
patches
● Contact the JSR's Expert Group

20. Expect a range of experiences
● Not everyone is a strong developer
● Use assistants to support people
● Don't assume prior knowledge
● The wide range makes for more
representative feedback

21. Expect a range of goals/outcomes
● Just learning is fine
● Contribution comes in many forms
● Building a community is a marathon, not a
sprint

22. Consider Exercises
● Can help focus a hackday
● Failing unit tests that are made to pass
● Not always the right choice

23. Summary
● Get developers involved
● Make sure people learn
● Communicate findings back
● Have fun!

24. Thanks for listening!
● Wikis:
○ http://adoptajsr.org
○ http://adoptopenjdk.java.net
○ http://hackdaymanifesto.com
● @adoptajsr / @adoptopenjdk
● Me:
○ @richardwarburto
○ insightfullogic.com