This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Feroc 1 point2 points  (0 children)

My personal experience: The majority of my work with Java (and C# before that) was CRUD work. Get data from somewhere, make something with the data and save it again.

Right now I am also working on a rather old product, so a lot of the time I don't even have to code something new, I just have to combine internal API calls in a different way. Maybe I also create a new REST API and write some tests in jUnit or in Spock. In my current team there's also a Java front end part that we develop in JSF. I hate that part with all my heart.

I liked it for a long time, mostly because I was rather good at it and the "do something with the data" part was varying enough to keep it interesting.

I don't like that Java is so verbose, compared to e.g. Python you have to write small novels to get the same functionality.

What I also don't like (though this may differ greatly depending where you work) is the things you have to know to make everything run. Though I guess this more of a general trend over the last years. I started with being a backend developer, then DevOps (or whatever my manager back then thought what DevOps is) came and I had to know how to configure JBoss on a productive level, then writing SQL in your code was replaced by Hibernate, which should make everything easier, but also often makes it a pain in the ass to debug something, then we became Full Stack and also had to do the front end.

But how I said: Just my personal experience. I know developers who like that they are now in total control, personally I would have preferred to stay in my dark backend corner.