javaone 2014 - 10 key learnings

1 key lessonslearned0

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, …

Java 8 Performance benchmarks indicate dramatic performance increases– don’t wait to adopt Java 8

#1

Seek to understand what other teams actually do

#2 Performance is a Social Thing

Ben Evans“ ’’

#3

People don’t do things you want them to do because you’re right

Being Followed: How Individuals Help Teams Exist

Mike Hill “ ’’

#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“ ’’

#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“ ’’

#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“ ’’

#7 Superpowered CI with Git - Sarah Goff-Dupont

Use shallow clones for your CI. This will speed

up your CI build

Don’t track binary files in your git repo: they have a

great impact on the clone time

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)

#8

A good developer does not stick to just one programming 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?“ ’’

#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?“ ’’

#10 Adopt an Evolutionary Architecture

Make sure you know what matters – your

business drivers define the architectural fitness

criteria.

Delay decisions as long as you can, but make

sure procurement is not the bottleneck!

Understand the forms of

technical debt. Testing safety

net will allow for evolution. Implement evidence

based reuse; discover reuse cases and

generalise instead of predicting the feature

San Francisco is not far from HasseltWe 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 ValleyHasselt

www.aca-it.beaca_it

Want to get more inspired by our experts ?

Stijn Van Den Enden

Robin Van Praet

Jan Van den Bergh

Jelle Ghys

Bram Gerits

A presentation by{ }