Thursday Dec 18, 2014
Saturday Dec 06, 2014
By MkHeck on Dec 06, 2014
Monday Sep 01, 2014
By MkHeck on Sep 01, 2014
Creating Our Robot Overlords: Autonomous Drone Development with Java and the Internet of Things [CON1863]
Tuesday, Sep 30, 2:30 PM - 3:30 PM - Hilton - Continental Ballroom 4
Who wants a mindless drone? Teach it to “think,” and it can do so much more. But how do you take it from Toy Story to Terminator? This session’s speakers discuss their new open source library, Autonomous4j, for autonomous drone development. Combining this library and some components from their mad science toolkit, they demonstrate how to get your Internet of Things off the ground and do some real cloud computing. In the session, you’ll learn how to write an autonomous drone program with Java 8; deploy it to the drone’s “positronic brain,” an onboard Raspberry Pi; have the Pi guide an AR.Drone to accomplish a task; monitor it via a JavaFX console; and create your own robot overlord. Demos are included: you’ve been warned!
With Jim Weaver & Sean Phillips
James Gosling recently stated that “being able to debug and profile robots out at sea is a truly life-altering experience.” He uses a set of tools—consisting of editors, debuggers, and profilers—that are part of the NetBeans IDE. In this session, Gosling and other speakers introduce you to these tools and show you how easily and quickly you can program and interact with devices via Java tools. Come see how well integrated embedded devices are with the Java ecosystem.
With Geertjan Wielenga, Jens Deters, José Pereda, & James Gosling
Using NetBeans and the bundled GlassFish application server, the speakers present each new concept with live code and then help attendees complete hands-on exercises.
With David Heffelfinger (and gracious assistance from Sven Reimers, Josh Juneau, Bob Larsen, & Bruno Borges)
Monday Jun 30, 2014
By MkHeck on Jun 30, 2014
Every so often, the "Powers That Be" pull together leading voices in various fields and host a virtual technology summit, free of charge to attendees. Guess what? It's that time again!
There are four different tracks, and the "summit" is actually "summits" - there will be THREE of these events, hosted at different dates/times to make it easier for anyone to attend, regardless of where on the planet they may be located. Here are the key details:
- July 9, 2014 09:00-13:00 PST Americas
- July 10, 2014 09:00-13:00 BST / 10:00-14:00 CET / 12:00-16:00 MSK/GST EMEA
- July 16, 2014 IST-10:00 / SG-12:30 / AEST-14:30 APAC
For the Java track, key speakers will include Dr. Fabiane Nardon, Reza Rahman, and Angela Caicedo - all respected speakers who know their stuff and convey it brilliantly. Do NOT miss this event!
For More Information
Hope to "see" you there!
Sunday Mar 23, 2014
By MkHeck on Mar 23, 2014
Every developer is a software user/consumer at various levels, and I'm sure that every one of us has run into a dev tool, library, or component that left us cringing. Why is it so difficult to bend to our will? Why does it seem so broken? WHY DID IT STOP WORKING WITH THE LAST UPDATE???
User-facing software shouldn't break or perform in ways that are "ugly", and if your software is a library/component, neither should your API. Whoever your user is, updates shouldn't break things, and failures (of whatever kind) should be handled gracefully. For example...
If your software doesn't facilitate the user's activity, i.e. make it easier, it is at best sub-optimal and may even be unusable. If your library's API doesn't deprecate and migrate changes clearly and gradually, other developers may find it difficult or impossible to use as well.
User Experience (UX) is about so much more than a User Interface (UI). Whatever you develop should be clean, as intuitive as possible to use, and work in expected ways. Highly self-configurable (to the extent possible) is a huge plus as well. If you are developing a library or custom control, its value can be measured by two things:
- The ease with which it can be applied to and cover "default" applications (simplicity)
- The mechanisms you provide to cover edge cases or "the other 20%" (versatility/extensibility)
These two guidelines apply whether you publish your code as open source or not; after all, the goal of open source software is not to taunt other developers with what could have been and force them to do it themselves.
Keeping these things in mind can help a developer craft better software that is more useful to more people.
Just something that has been on my mind for awhile now...
Have a horror story you'd like to share? Please don't post names - no need for public floggings (!) - but if you have a particularly bad example that you use as a reminder to write better code, please share it in the comments so we can shudder with you. Misery loves company. :)
The Java Jungle addresses topics from mobile to enterprise Java, tech news to techniques, and anything even remotely related. The goal is to help us all do our work better with Java, however we use it.
Your Java Jungle guide is Mark Heckler, an Oracle Senior Java/Middleware/Core Engineer with development experience in numerous environments. Mark's current work pursuits and passions all revolve around Java and leave little time to blog or tweet - but somehow, he finds time to do both anyway.
Mark lives with his very understanding wife & kids in the St. Louis, MO area.
- Point of Clarification: NetBeans, JSF, and MySQL Primary Keys
- How to Create a Positronic Brain for Your Drone
- Join Us at JavaOne 2014!
- Virtual Technology Summit
- Don't Create Brittle Software
- MonologFX Update: Timed JavaFX Dialogs
- Join me at JavaOne 2013
- Virtual Developer Day: Java ME, SE, and EE
- Java EE 7: Get Ready!
- How to "Pretty Up" Your JavaFX TableViews