Devnexus 2018 keynote – nasa

Title: Designing and Visualizing Deep Space Manned Missions
Speakers: Diane Davis & Sean Phillips

For more blog posts, see the DevNexus 2018 live blogging table of contents


The keynote speakers started with a nice disclaimer about not working for NASA

Lunar Orbital Platform Gateway

  • Next outpost in space
  • ”only” 5 days away
  • Need to find an orbit that is not too hard to get into and out of
  • Big data problem  – can’t look at all the orbits.

Tools/Tech

  • ”We are builders we are creators; it is all about the tools”
  • ”You are more than the lines of code that you write. It’s not about the tools; its about the ideas”
  • ”Disturbing trend where measure based on lines of code. We need code; but we also need ideas Ideas that lift people up. Don’t leave here with the latest API/framework. Leave here with an idea”
  • Look at data points vs orbits to reduce dataspace
  • NetBeans – version 9 in beta
  • Cloud – so can plot more trajectories

JavaFX

  • Tried JavaScript canvas – not fast enough to render *lots* of data points. Redraw anvas every milliseconds based on current data
  • FXyz library – 3D library

Parallel

  • Using parallel stream API
  • Hard to make parallel
  • Lots of math
  • Works great in cloud; lots of cores
  • Generates states/points or spacecraft

”As we all kow, the enemy’s gate is down; space is three dimensional” – nice to have an Ender’s Game reference in there!

My take

This was a fun start to the morning> A current event and very relevant.  The pictures were awesome. Showing code was awkward. Aside from being too small, dark colors on a black background does not look good in the distinace. (And I’m in the fifth row).  They both speak really well and the images of orbits are cool

Iive blogging from DevNexus 2018

This is the table of contents for my DevNexus blog posts.

Wednesday

  • I taught a half day workshop on JUnit 5. You can try it out from the github repo.

Thursday

Friday

General notes

  • 27K attendees and over 100 countries! Outside of JavaOne, this is the largest Java conference in the US.
  • The auditorium would have been full if people took the front seats. Good they had an overflow room.
  • I love that the badges have names on both sides.

setup for DevNexus workshop – BDD with Spock and JUnit 5

Burk Hufnagel and Jeanne Boyarsky will be presenting a full day workshop entitled “Behavior Driven Development with Spock / What’s new with JUnit 5“. at DevNexus this year. Attendees will use their laptops.

If you run into any trouble setting up for the lab, you can post a comment on this blog post or start a thread in the Testing or IDEs forum at CodeRanch.

Here’s what needs to be installed:

Java

The workshop uses Java 8. If you have Java 9 installed, please ensure it is not the default:

  • Windows/Linux: Update your path
  • Mac: mv /Library/Java/JavaVirtualMachines/java 9/Info.plist /Library/Java/JavaVirtualMachines/java 9/Info.plist.disabled

Validation: run java –version at the command line and ensure it prints out a Java 8 version.

Eclipse (recommended)

You can use the IDE of your choice or none at all. We will be able to answer all questions about Eclipse and the command line. If you choose IntelliJ (2017.2.1 or later), please be sure you are comfortable navigating, running tests and running builds in it.

  1. Download and install Eclipse Oxygen. If you already have Eclipse Oxygen, check the splash screen says it is the December version. If not, please download the latest Eclipse Oxygen.
  2. Help > Eclipse Marketplace Install the STS (Spring Tool Suite) plugin

Validation:

  1. Try to create a new empty Gradle project:
  2. File > New > Other > Gradle Project
  3. Give the project a name and finish
  4. Wait a minute or two for the project to be created
  5. File > New > JUnit Test Case
  6. Confirm you have a radio button called “New JUnit Jupiter test”
  7. Click cancel to exist the wizard
  8. File > New > Other > Spring > Spring Bean Definition
  9. Click cancel to exit the wizard
  10. Success, you are ready for the workshop!

Optional: Gradle

We will be using Gradle as the build tool. While the projects will contain a Gradle command line, you are welcome to use your own Gradle install.

Optional: Git

One of the steps will be to pull code from git. If you have a git command line (or git bash), this is a one line operation. If not, you’ll be able to download a zip file from github so this isn’t a hard requirement.