• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Selling Groovy to management

 
author
Posts: 71
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Dierk,

Congratulations on your book. My question is: what are the strong selling points that you have to convince that using Groovy within a Java project will give a return on the investment, the investment being that developers have to do the language context switching and also deal with any issues that arise from having Groovy integrated within the project?

In other words, how do you convince your boss that adding Groovy in a project would be a Good Thing?

Thanks,
Freddy
--
 
author
Posts: 43
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for your kind words Freddy,

well, strategies are different, depending on the context.

With management being totally non-technical, they are not likely to understand any of the technical points you may bring forward. This leaves us with promising time or money gains, which I personally dislike - even if they are true. Therefore, in this scenario, I follow Scott Davis in telling them that we do is all-Java (which is true) with some elaborate config files (the Groovy files).

With technical management I would show them some Groovy code. Some that's very close to Java and some that reduces the verbosity of Java dramatically.

When there is fear about introducing Groovy in your project, then you can start using it outside the production code: replace build automation scripts with Groovy, use it for unit- and functional-testing, for prototyping, and so on.

cheers
Dierk
 
reply
    Bookmark Topic Watch Topic
  • New Topic