Getting the most out of JavaOne 2014 is a full-time job. Our ACA IT-Solutions experts visited the JavaOne conference and came back with their 10 most important key learnings of the JavaOne conference. A presentation by Stijn Van Den Enden, Robin Van Praet, Jan Van den Bergh, Bram Gerits and Jelle Ghys.

1. 1 key lessons
0learned

2. Java 8 Performance benchmarks indicate dramatic performance
increases– don’t wait to adopt Java 8
#1
see http://www.spec.org/cgi-bin/osgresults?conf=jbb2013
lambda’s are not the only reason; date and time API,
performance, static analysis, Metaspace, …

3. Seek to understand what other teams actually do
#2 Performance is a Social Thing
“ Ben Evans ’’

4. #3
People don’t do things you want them to do because
you’re right
“ Being Followed: How Individuals Help Teams ’’
Exist
Mike Hill

5. #4
Efficiency is not doing things faster but
avoiding those things that should not be done
Java 8 is an enabler for Reactive programming
“ Venkat Subramaniam’’

6. #5
Creating a culture of security is the only way
to get your applications more secure
“ Application Security is a team effort. Is your
security officer a great coach?
Code level security games and puzzles - Brenton Phillips ’’

7. #6
Someone against code reviews should be gradually
convinced otherwise
“ The greatest haters will become the greatest lovers.
Code review adds great value (e.g. bus factor)
Want code code quality, just ask?
The art of code review ’’

8. #7 Superpowered CI with Git - Sarah Goff-Dupont
Don’t track binary files in
your git repo: they have a
great impact on the
clone time
Use shallow clones for
your CI. This will speed
up your CI build
CI on your branches; it
eliminate the risk of
having a broken build on
master
Get immediate
integration feedback
Don’t merge integration
upstream - merge your
feature branch to master
Use server and client
side hooks to smooth
your CI pipeline (see
https://bitbucket.org/
tpettersen/git-ci-hooks)

9. A good developer does not stick to just one programming
#8
language but embraces the best of each of them
“ Don’t avoid using another programming language.
Try to understand the language and leverage the good ’’
parts.
Is avoiding Javascript a good option?

10. #9
On classloader related errors always validate
your assumptions
“ ClassCastExceptions are often easy to solve when you check
your assumptions;
Is it the class loaded by the same classloader?
Is the class the same? ’’

11. # 10 Adopt an Evolutionary Architecture
Make sure you know
what matters – your
business drivers define
the architectural fitness
criteria.
Understand
the forms of
technical
debt. Testing safety
Delay decisions as long
as you can, but make
sure procurement is not
the bottleneck!
net will allow
for evolution. Implement evidence
based reuse; discover
reuse cases and
generalise instead of
predicting the
feature

12. San Francisco is
not far from
Hasselt
We learned a lot during the week, but many
practices are already part of our toolbox for
many years now. Key practices in architecture,
software engineering, agile are shared between
Silicon Valley and Hasselt ;-).
Silicon Valley
Hasselt

13. { Stijn Van Den Enden
Robin Van Praet
}
A presentation byJan Van den Bergh
Jelle Ghys
Bram Gerits
Want to get more inspired by our experts ?
www.aca-it.be
aca_it