[Adopt-a-JSR Day] Adopt JSR 385 - Units of Measurement 2.0 for Java

___WARNING___ This is a hacking session. There are limited seats, so please RSVP only in case you are sure you will attend.

On the 1st of June, we have the honor to host Werner Keil, Spec Lead of JSR-385, who will help us to adopt JSR-385.

What is Adopt-a-JSR and why should I get involved?
https://www.youtube.com/watch?v=NgrJZDo9uOM

======================================================================

Agenda

11:00 Welcome
11:15 Learning about JSR 385 by Werner Keil
12.25 Adopt JSR 385 Hacking session with Werner Keil
13:30 Lunch
14:30 Adopt JSR 385 Hacking session with Werner Keil
17:15 Drinks

========
Giveaways
A free ticket for JCON 2019 in Düsseldorf

What should I bring?
This is a hacking session, so, be sure to bring your laptop :-)
========

About the session

Adopt JSR 385 - Units of Measurement 2.0 for Java

In 1999, NASA lost the $125 million Mars Climate Orbiter as it went into orbital insertion. Due to a mismatch between US customary and SI units of measurements in one of the APIs, the spacecraft came too close to the planet, passed through the upper atmosphere and disintegrated. Sadly, this hasn’t been the only instance where a mismatch between units of measurements had catastrophic consequences, but it’s certainly one of the most spectacular and expensive ones.

How could this happen? The bad news: if you use primitive types to handle quantities in your code, due to the same practice at best, you’ve codified the unit in a variable name or database field, e.g. calling it lengthInMetres. Otherwise, you’re only relying on convention, just like Lockheed Martin and NASA did. After a brief history of unit mistakes and how they could have been avoided, we present JSR 385, how it helps to improve data quality and integrity. And how it applies the recent redefinition of SI base units on May 20, 2019.

Followed by hands-on live hacking with JSR 385 and the Units of Measurement projects. From transport and logistics to aviation or health and fitness we cover several potential use cases. You have a choice between Java (anywhere from Java ME 8 to Java 12 or 13) and popular JVM languages like Kotlin, Groovy or Scala.

This is for architects and developers who want to participate in the Adopt-a-JSR movement, and learn how adopting JSR 385 can help them avoid more $125 million mistakes.

About the speaker

Werner Keil is a Cloud Architect, Java EE, Microservice and Embedded expert for a security firm. Helping Global 500 Enterprises across industries and leading IT vendors.
He worked for nearly 30 years as IT Manager, PM, Coach, SW architect and consultant for Finance, Mobile, Media, Transport and Public sector.
Werner develops enterprise systems using Java, Java EE, other Oracle, IBM or Microsoft technologies, JavaScript, Node, Angular, dynamic or functional languages.

Werner is committer at Apache Foundation, Eclipse Foundation, Babel Language Champion, UOMo Project Lead and active member of the Java Community Process in JSRs like 321 (Trusted Java), 344 (JSF 2.2), 354 (Money, also Maintenance Lead), 358/364 (JCP.next), 360/361 (ME Embedded), 362 (Portlet 3), 363 (Unit-API, also Spec Lead), 365 (CDI 2), 366 (Java EE 8), 375 (Java EE Security), 380 (Bean Validation 2), 385 (Unit-API 2, also Spec Lead) and was the only Self-employed Member of the Executive Committee for 9 years in a row till 2017. Werner is currently the Community representative in the Jakarta EE Specification Committee.