Dev of the Week: Antonio Goncalves
Every week here and in our newsletter, we feature a new developer/blogger from the DZone community to catch up and find out what he or she is working on now and what's coming next. This week we're talking to Antonio Goncalves, senior software architect and Java EE Consultant, co-creator of the Paris Java User Group, and author. Some of his most recent DZone posts include:
- Java EE 7 Courses at PluralSight
- Java EE 7 JavaDoc on Dash
- "Oh Lord, won't you buy me a Mercedes Benz" (or RIP GlassFish)
1. What have you been working on lately?
As usual, several topics at the same time. Despite my day to day consulting job, I've created two Java EE 7 courses on the Pluralsight platform, given several talks on Java EE 7, spending some time on JBoss Forge and having fun with my daughter on my spare time ;o) This year was also the 3rd edition of Devoxx France. We were very busy organizing it so the 1500 attendees could get good technical content. And now I'm getting ready to be part of the Java EE 8, CDI 2.0 and the new configuration JSR expert group.
2. You've written a lot about Java EE on blogs and in your published work. Are there any new features you'd like to see in future versions? What does the ideal future of Java EE look like to you?
Java EE has always been about standardizing commons concerns needed by our applications: we needed SOAP, Java EE brought JAX-WS, we needed REST, we had JAX-RS, batch, concurrency and so on. So the future of Java EE will still be about standardizing common needs (configuration, caching, server-side events...). But my ideal future would be to bring more modularity to Java EE (we have monolithic specifications, why not dividing them into smaller parts so that can be re-used by other specifications) and a unique container (at the moment it's a bit messy, we have EJB container, Web container and several providers) that would manage POJOs with services (these services could aggregate other services, think of @Stateless as a stereotype, for example)
3. Are there any particular developer tools or resources you couldn't live without?
I've been using IntelliJ IDEA in my day to day life for more than 10 years, difficult to switch to anything else. I'm a late adopter of Mac OS X, but again, going back to something else would be painful. Otherwise, I've given my soul to the Cloud: I couldn't live without a Google Mail, Google Calendar, Dropbox, Evernote, Trello...
4. Do you have a favorite open source project (or projects) that you've contributed to recently?
I was an early adopter of JBoss Forge (code generation tool). So when the JBoss Forge team was getting the new Forge 2 out, I started to open JIRAs, tested every features, chatted on IRC with the team... and then committed bits of codes here and there. I wish I had more time to contribute, I really like the project and the Forge team is really nice.
5. Do you follow any blogs or Twitter feeds that you would recommend to developers?
That's a difficult question. My feed reader has tons of subscriptions and I follow 400 people on Twitter (mostly in Java/JavaEE). So I recommend you follow me and I promise to give you some hints or re-Tweets on anything related to Java EE ;o)
6. Did you have a coding first love -- a particular program, gadget, game, or language that set you on the path to life as a developer?
Basic! I started development with a Commodore 64 a long time ago. Basic was my first language and then I managed to get a C64 extension and I discovered assembly. That's when I started writing my own games and plugging electronic devices on my C64. Today when I received my Raspberry Pi a year ago, I wish I had more time to play with it, I wish I had a device like that when I was a kid ;o)
7. Is there anything else you'd like to mention?
Commodore, Basic, Java, Cloud, Big Data... computing life is just about having a new toy to play with. When I program today, I build on top of bits and pieces, just like when I was a kid playing with Legos. I feel the digital age shouldn't just be about playing with algorithms. We, developers, are building the Future where everything little thing will end up connected, traced, analyzed... for the best or the worse. We need to step back, think, and bring some philosophy to IT so we understand the consequences of what we are building today so we don't damage our future.