It's a common expression though what his post was based upon.
"[You don't get paid to write software as a Java dev, you get paid and judged by the amount of lines of code you write.]"
If Java and other imperative devs haven't heard that before then they need to consume more sources of knowledge and widely held opinions.
The quip about being dissolved of any real responsibility as a Java dev is stereotypical of course. And it doesn't solely apply just to Java but to the general mindset shared by the various big imperative enterprise languages. It is _possible_ to use such languages in a _cleaner_ fashion (with lots of hoop jumping) but rarely does the opportunity present itself in such enterprise environments because of politics and backwards thinking. Additionally, _why_ should you have to incorporate countless additional libraries and techniques just to "bend" the language to what it should have been in the first place? That's what everyone ridicules JavaScript for doing.
The best, most experienced programmers will naturally gravitate toward functional practices; which is basically SOLID in OOP land. Unfortunately, at the moment, only the luckier (or pluckier?) ones will actually find themselves in a job that lets them use a real functional language that deprecates the need to jump through so many hoops just to achieve a maintainable and immutable (and all the other good stuff) design.
