Groovy Developer Manifesto

Vladimír Oraný
Jul 27, 2018 · 1 min read

Groovy is not an excuse to write sh***ty code.

Image for post

As a Groovy Developer I hereby promise:

  1. I will write code in Java unless writing in Groovy would add some value; removing semicolon does not add value
  2. I will follow Effective Java rules even when I am writing Groovy code
  3. I will use @CompileStatic annotation by default unless I really need dynamic language features
  4. I will never ever use def keyword
  5. I will never use Map as an excuse not to create meaningful class
  6. I will use @NamedParam, @NamedDelegate and @NamedVariant instead of raw Map method parameters
  7. I will never use raw Closure without a type parameter
  8. I will use @ClosureParams for every Closure method parameter
  9. I will use @DelegatesTo for every Closure method parameter with altered delegate
  10. CodeNarc is my best friend forever

Do you have your own statement to add? Please, leave it in the comments. I may update the list in the future.

You can sign this manifest using the hand icon bellow.

Stories by Agorapulse

Agorapulse is a leading Social Media Management platform.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch

Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore

Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store