That's a ridiculously extreme example, IME. Having been working with Java for 25+ years, I've never seen anything like that in code written by a shop I worked at, FWIW. And as a corollary I'm about 100% certain that you could find some equivalent extreme case to use as an example to dunk on any language/platform.

this is what we mean by "JavaCulture" - java | JVM really wonderful things but the culture is what sets these things back

Maybe there are still some Java shops out there living like this. But to me, this is a 20 year old outdated notion. shrug

▲

theflyinghorse a day ago | parent [-]

You have worked at some outstanding java shops then! In my experience the article is precisely representative of Java culture even today

	▲	throwawey1234 a day ago \| parent \| next [-]
		I also have 20+ years of experience and haven't seen that type of code either. I am however struggling to understand an over engineered Rust "micro" service at work. There's no language or framework that is free from this. Maybe it's because I have not worked in typical enterprise companies? Spring Boot can be a really quick way to get things done. My current job is not in enterprise, but we use Spring Boot for most of our services, and rarely have issues related to Spring itself. We have micro services handling many transactions per minute and starts up within 10 seconds. The CPU usage is low and decent memory usage, even on the small pod sizes that we use. There are ways to reduce the startup, but we do not have the need. The code is easy to reason about and new hires are productive within a short time.
	▲	mindcrime a day ago \| parent \| prev [-]
		Let's not go too far! I've seen some crap code, granted. But for the most part, the crap code I've seen is, I believe, stuff written by people who would have written crap no matter what language they were working in. That said, I have in fact also had some outstanding and talented colleagues over the years as well. A point that's probably worth reflecting on, so thanks for the reminder.