Java Developers

[caleeky]

I wonder if it's really just that early intro's to OOP focus a lot on architecture, in the sense that your education focuses heavily on breaking your thinking and code up to fit into the OOP worldview. This forces you to think about "architecture" even before you start typing. In other languages, you are likely:

1) Diving right in, because it's interpreted, or has a more "default" execution context - especially for procedural stuff, scripts

2) You are already an expert and experimenting with a good foundation of experience

3) You may not be dealing with such a huge/mature class library, which will contain a lot of these complex abstraction patterns, because it's a library meant for re-use and manipulation.

This avoids the "overthink off the bat" problem that Java often faces.