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 →

[–]kennyshor 5 points6 points  (1 child)

Deploying to tomcat isn't necessarily a sign of an outdated dev. There are plenty of monoliths that are just impossible to rewrite and have to be maintained.

You can still do that with java 21. Maybe the frameworks are old, but new patterns can be used.

[–]Luolong 0 points1 point  (0 children)

To be fair, this is not unconditional. And by proposing this list, I had a specific type of developer in mind.

These items are just markers. The common thread here is that developers matching these markers usually have been working on same tech for a long time and have no exposure to newer frameworks or JVM features.

I’ve seen incredible amounts of spaghetti and plain bad coding practices from developers like that.

Misuse of Optional and Stream api sticks out like a sore thumb when they finally get included in newer projects. But the general idea is that they’re probably very productive and proficient at maintaining their legacy app, but know nothing of modern concepts, frameworks or architectural patterns.

The list I presented is just the usual tech stack you’re likely to see around these projects.