Skip to main content

JavaOne – Day 4 – Exciting Conference Times

By 29 oktober 2015januari 30th, 2017No Comments

Welcome to our blogs on the exciting JavaOne again! First some good news: today, our Grails Workshop is accepted at a conference! It’s the Technical Open Source conference, in Eindhoven. Ted Vinke and I will be having lots of fun with the audience, sharing the coolest Grails tricks and the latest Grails3 knowledge. Ted and I will also soon present this talk at Devoxx Antwerp on the 9th of November.  But today we focus on JavaOne, so let us continue with another great day of this conference!     Groovy DSL Domain Specific Languages (DSLs) have become a valuable part of the Groovy platform. DSLs are used in native Groovy builders, Grails and GORM, and testing frameworks like Spock. Even Gradle uses mainly Groovy DSLs. But how is a DSL implemented? How does it work behind the scenes? How do we add a DSL to Gradle? Cédric Champeau (Gradle inc. employee and one of most active Groovy committers) explained with samples how anyone can add a DSL to the Gradle DSL. If you want to start learning DSL programming with Groovy, try this excellent blog.   Meeting JavaOne speakers Today I discussed a lot with speakers, all eager for discussion about their products. For instance, the Founder of Vaadin (Joonas Lehtinen from Finland) introduced me to his framework. I know Vaadin for some years: a standardised way to do efficient and powerful development with Google Web Toolkit (GWT). Because of my interest in Grails, he has introduced me to the writer of the Grails-Vaadin book. Another speaker I questioned was Mark Buck from Oracle, hoping for in-depth views on project Jigsaw. He advised to start downloading the JDK9 today and help the pleasant OpenJDK community with fixes. He was exciting about the future dependency mechanism inside Java and said it will compete other dependency mechanisms (from Maven or Gradle). So I downloaded the source and tried!  Rise of the (Scrum) Machines A real eye-opener to me came from Atlassian. Everybody likes their good commercial products (respectively a wiki and taskmanager). The reality of these tools is that they do cost overhead in finding the relevant data for you. There are so many tasks, sprints, wiki contents: how to maintain a time saving personalized view? Create 100 bots! Atlassian providers programmable bots to create all kind of smart & realtime views on your current work. For instance: tasks that are open too long, main things to discuss during the standup, important backlog suggestions. This can really improve how good people do their sprints. And creating bots is possible in the current JIRA at I use. So let’s program with those JIRA APIs, when back home, creating good bots (overviews) that improve my Sprints. 

 Rise of the Scrum machines