Go Go Java Developer by Piotr Przybyl

“You can never understand one language until you understand at least two.” – Geoffrey Willans

For years I've been developing mostly in JVM languages. Sometimes in other C-derived languages, which was both cool and easy.

A few months ago (due to career shift) I had to learn Go rapidly. While technically Go has keywords looking similar to C, many things are simply different and even unheard of in C-based OOP languages. Learning Go is a great journey and the best are these AH-HA moments, when doing things in Go I suddenly understood Java better.

Sure, during a single talk I won't teach you Go. Thing is: I don't event want to, as all I want is to show you some concepts in Go which can help you (just as they helped me) become better Java developer and understand why we need projects Valhalla and Panama. It's about leaving our comfort zone to get... more comfort.

[nojerome]

I'm 20 minutes in and had to pause to let you know how awesome this presentation is.

As a developer who's been writing Java the past 10 years, these are great tips to have up front for my new Go position.

This is a fantastic way to pic up conventions that would have taken many dev hours to catch on to.

[glaurung]

Good talk. One improvement. I'm fairly certain pro-tip #13 37:47 was incorrect in the explanation for what happened; resizing of slices and their capacity requirements has nothing to do with why the append did not work in the example. It failed because the append operation in Go returns a new slices but the index operations act in place. In Java list.add() does not create a new list but works in place. In the example the assignment of 'd' and append of 'G' both happen on the newly created slice when the append was called.