Be nice to your DevOps team by not using Maven or kitchen sink frameworks.

dodger
2018-06-06T21:06:05Z

Maven tries to be the kitchen sink in a lot of ways - rigid requirements to use plugins instead of scripts, trying to wrap your scm, and even act as a docker wrapper... this is insanely frustrating and an anti-patter for the rest of the software space. I would rather find a new job than work at a company that keeps pumping out maven and jhipster apps. It doesn't play nice with CI, it uses an insanely ugly configuration (xml) and most java developers don't even really know what they are doing when they are using it.

Making a micro-service api? You don't need jhipster or maven or even java - there are so many other better alternatives. Need something simple? flask. Need something performant? go. And there are so many others in between that won't give you a NullPointerException, require you to download the entire internet just to serve some serialized json, or make your devops team hate you.

Interested in hearing rebuttals and other peoples alts and overall preferences.

Comments URL: https://tildes.net/~comp/1t4/be_nice_to_your_devops_team_by_not_using_maven_or_kitchen_sink_frameworks

Votes: 5

Comments: 5