• Use Android Studio (it will only get better)
• Use Gradle (Maven support it's still alive though)
• Use Genymotion
• Android testing still sucks (but you have to do it)
• Have a look at roboletric
• No way to have test coverage with gradle yet

• Javascript unit testing exists
• Use Karma
• Do not use callbacks (unless you like stair code)
• You can have a browser environment within node, but just use phantom

• Just use it
• Use it now

• Treat documentation as source code
• Markdown breaks down

Not directly related to the project notes:

Atwood's Law:

• If you write "Offline First" webapps, you can use Chrome to make them look like normal OS applications
• Google is working on integrating it's services as much as possible
• Vendor lock-in
• Use node-webkit instead with less google integration

• If you use eclipse do not do it because it is free
• Use IntelliJ IDEA
• Use AngularJS
• Use Bootstrap
• Mesure with Page Speed
• Graphs are cool!

• Java tooling for testing is available
• Just use it

• It is unit test centric
• Started as a better test runner for AngularJS unit tests
• You can use without AngularJS
• Looks like the Dart testing part has been skiped

• Some stuff regarding the evolution of a language
• Java has finally lambdas (just another name for closures)
• Java 8 is alive and kicking
• The most interesting part was meta-ex coding band that opened the day

• Thing out of the box
• Get out of your confort zone

• Java can be used on "lite devices"
• Gemalto is trying to provide such devices
• Just another marketing talk

• This tweet describes it all: Tell your managers they suck if they put you in a 2 hour meetings
• One of the talks to watch once available at parleys.com. Till then here are the slides

• Not the application server you used to have
• Can be embedded or run as a "host" environment
• It is polyglot: There was live examples of using it with Java, Python, Javascript, Groovy
• It brings the easyness of nodejs to the jvm
• You can easily create a cluster with many vert.x nodes (Hazelcast is being used by default)

• It only took 20m (why wasn't that a quickie?)
• Talked about how excited he was as a Scala guy to see lambdas on Java
• Tried to show how play's java api could have been with lambdas
• The talk was completelly out of its context
• For sure there are more to expect from Typesafe

• Use AngulaJS
• Vertx works just fine
• Rething mongodb

• Google guys stoped talking about angularJS
• The whole day was a push for dart from Google

• One of the top ten talks
• Nothing to do with programming

• Start putting data into elasticsearch
• Use kibana to make sense of them
• Use logstash to flood your elastic search with data

• If you want stracture with javascript you can wait for latest ECMAScript implementation
• Dart VM will be bundled with Google Chrome next year
• The target was to create a language familiar to developers and push it for web development

• Focused more on web applications
• One language to rule them all feature (runs on both server side and client side)
• Introduced pub which is the npm registry of dart
• All bundled together with a demo

• Voted as the best session

• Prioritize
• Fix the task with the higher priority
• Prioritize again
• Always expect a change

• Continous Delivery does not always make sense
• What happens if your build is some hours long with your build branch?
• What happend if there are more than one teams working on the same branch?

• Mostly a Gradle can do everything talk
• Android studio was the first IDE to take advantage of the gradle api
• Gradleware is about to invest more on that
• One of the features to expect at the next releases is parallel builds

• Start with MR
• When the code becomes more complex move to something like Pig
• If you start missing SQL move to something like Hive
• Then forget everything and start using cascading

• There was a Drone flying at the stage
• The talk was not techical, but...
• It shows the power of open source in general
• Take existing projects, wire them together and you get a prototype for free!