Tweet
Tweet

Slide 1

Slide 1 text

Why use #groovylang? How to convince your boss and others Jenn Strater @codeJENNerator

Slide 2

Slide 2 text

@codeJENNerator Note For Those Viewing Slides Online • Bulleted text like this indicates the key points mentioned on a previous slide. They may not have been included in the official presentation. • If this view does not support links, the links will work in the pdf. Click the ‘download pdf’ button on the right.

Slide 3

Slide 3 text

@codeJENNerator Follow Along https://speakerdeck.com/jlstrater/why-groovy-berlin-gug-march-2018

Slide 4

Slide 4 text

@codeJENNerator Outline • Why use Groovy? • Truth or Myth? • Ways to Start Using Groovy Today!

Slide 5

Slide 5 text

Unless otherwise indicated, these slides are © 2013-2016 Pivotal Software, Inc. and licensed under a Creative Commons Attribution-NonCommercial license: http://creativecommons.org/licenses/by-nc/3.0/ Follow Along https://speakerdeck.com/jlstrater/test-driven-docs-springone-2017 https://github.com/jlstrater/groovy-spring-boot-restdocs-example https://github.com/ratpack/example-books https://github.com/jlstrater/spring-restdocs-public-api-example 5

Slide 6

Slide 6 text

@codeJENNerator About Me - Working at Zenjob. - Groovy (mostly Grails) user since 2013. - Before moving to Berlin, I spent a year in Copenhagen. - Before that, I was senior consultant at Object Partners, Inc. in Minneapolis, MN, USA. - Co-founder of Gr8Ladies (deprecated) - Passionate about bring new people into the Groovy community through free introductory workshops called Gr8Workshops and supporting underrepresented minorities and their careers in tech.

Slide 7

Slide 7 text

@codeJENNerator Audience Background

Slide 8

Slide 8 text

@codeJENNerator Audience Background • Groovy • Everyday user • Side project user • New to Groovy • Frameworks / Tools • Grails • Spock • Gradle • Griffon • Jenkins • Spring Boot

Slide 9

Slide 9 text

No content

Slide 10

Slide 10 text

No content

Slide 11

Slide 11 text

@codeJENNerator Features

Slide 12

Slide 12 text

No content

Slide 13

Slide 13 text

No content

Slide 14

Slide 14 text

No content

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

No content

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

@codeJENNerator Ecosystem

Slide 19

Slide 19 text

No content

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

No content

Slide 22

Slide 22 text

No content

Slide 23

Slide 23 text

No content

Slide 24

Slide 24 text

No content

Slide 25

Slide 25 text

@codeJENNerator Community

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

No content

Slide 28

Slide 28 text

@codeJENNerator

Slide 29

Slide 29 text

@codeJENNerator Truth or Myth?

Slide 30

Slide 30 text

@codeJENNerator • After spending some time at Java User Groups, Conferences, and reading lots of stuff online, I realized that there are a lot of things people get wrong about Groovy or that just aren’t true in the most recent versions. • All of these assumptions are things are related to conversations I’ve had with real people at some point in my career.

Slide 31

Slide 31 text

@codeJENNerator WARNING • For the online version, the answers have been removed. You’ll just have to see it in person next time ;)

Slide 32

Slide 32 text

@codeJENNerator 1.Groovy is the same thing as Grails

Slide 33

Slide 33 text

@codeJENNerator 2. Groovy is a scripting language

Slide 34

Slide 34 text

@codeJENNerator 3. The original creator of Groovy has left the community

Slide 35

Slide 35 text

@codeJENNerator 4. Groovy’s dynamic nature can mean more runtime errors

Slide 36

Slide 36 text

@codeJENNerator 5. Groovy is a dynamically typed language

Slide 37

Slide 37 text

@codeJENNerator 6. Groovy is for side projects/ scripts/internal projects but not for production apps

Slide 38

Slide 38 text

@codeJENNerator 7. Groovy is slow

Slide 39

Slide 39 text

@codeJENNerator 8. Gradle is switching to Kotlin because Groovy sucks.

Slide 40

Slide 40 text

@codeJENNerator 9. You can use Groovy and still write statically compiled code

Slide 41

Slide 41 text

@codeJENNerator 10. Grails is Rails for the JVM

Slide 42

Slide 42 text

@codeJENNerator 11. Groovy is dead

Slide 43

Slide 43 text

No content

Slide 44

Slide 44 text

@codeJENNerator

Slide 45

Slide 45 text

@codeJENNerator Adding Groovy to your organization

Slide 46

Slide 46 text

@codeJENNerator See if you are already using Groovy in/ with your existing libraries or frameworks • Jenkins (Pipeline, Jobs Plugin, and many more!) • Spring Boot (optional Groovy support) • Apache Spark • SoapUI • JMeter • Tinkerpop • Elasticsearch (deprecated)

Slide 47

Slide 47 text

@codeJENNerator Spock • Groovy can be used in tests, but not in the end product if you don’t need it. • Spock is the BEST testing framework for the JVM

Slide 48

Slide 48 text

@codeJENNerator Try a small POC • Frameworks like Grails are great for trying something out. If the team gets used to using Groovy for small projects, it might be easier to use it in more places later.

Slide 49

Slide 49 text

@codeJENNerator Get Connected • Subscribe to the groovy users mailing list • Join the Groovy Community on Slack groovycommunity.com or sign-in again at groovy- community.slack.com • Contribute by writing documentation or fixing bugs. • Attend conferences like GR8Conf EU 2018. • Join Zenjob!

Slide 50

Slide 50 text

@codeJENNerator Conclusion

Slide 51

Slide 51 text

@codeJENNerator

Slide 52

Slide 52 text

@codeJENNerator • Groovy is a fun language with a great community!

Slide 53

Slide 53 text

@codeJENNerator • Groovy is a fun language with a great community! • You can use Groovy in many different ways!

Slide 54

Slide 54 text

@codeJENNerator • Groovy is a fun language with a great community! • You can use Groovy in many different ways! • It isn’t an all-or-nothing solution. You can start small.

Slide 55

Slide 55 text

@codeJENNerator • Groovy is a fun language with a great community! • You can use Groovy in many different ways! • It isn’t an all-or-nothing solution. You can start small. • Start talking about Groovy with your boss and coworkers and make sure they don’t keep spreading the Groovy myths. Keep them on the Groovy truth.

Slide 56

Slide 56 text

@codeJENNerator Questions? https://flic.kr/p/5DeuzB