Java

Java 11 - Keeping the Java Release Train on the Right Track

Tell us a bit about the work that you are doing today.

I work for a large bank in New York City on the DevOps team, and we're automating the pipeline to enable continuous deployments to production. We've been doing automation for a lot of years. My team does a lot of coding and mentoring of others. It's amazing how much automation there is in order to get something to work for a lot of teams including reporting, security and load testing. We do a lot of Selenium. It's fun to write the code because it's not just another webapp screen, it's something that's unique and different most of the time. There are opportunities to play with things that are new and code. There are a lot of heavy threads and a lot of heavy connectivity testing, which is a lot of fun. Also, the automation programming is nice because each piece is fairly small, something to get out of the door really quickly and see it in production right away.

You're talking about Java 11. What made you decide to pick Java 11?

Java 11 is new, very new, I was looking for something that people need to have an awareness of, and Java 11 is a sweet spot for that because in New York City a lot of big companies, such as financial institutions, have been holding back on using Java 11 because Java 9 and 10 don't have long term support. Which means that Java 11 is the next one that a lot of people are going to upgrade. Java 9 got a lot of exposure, everyone knows what Jigsaw is, but Java 10 got almost no exposure in New York. I suspect Java 11 is going to have a similar problem. This is a way of letting people know what's this about, catching them up with Java 10, getting them ready for Java 11, and be ready and excited for it in late September when it actually comes out.