3 ms·
This definitely resonates with me. I got my first paying Java gig in 1996 (really). Back then, one person could be reasonably expected to know all of Java, and
by gaius 17y ago
This definitely resonates with me. I got my first paying Java gig in 1996 (really). Back then, one person could be reasonably expected to know all of Java, and work on any project that was feasible to do in Java, whether that was applets, servers, fancy graphics, database access (no JDBC back then!), anything.
Fast forward a few years, I knew JDBC and Swing pretty well, a little of the EJB stuff, there were whole vast swathes of the Java universe that were simply out of scope. I got out of Java a few years ago, but I imagine it must be even more so now. With my current main languages, Python and OCaml, I still feel as if I've barely scratched the surface (and in the company I count as an "expert").
But this isn't limited to languages, back then a DBA could know all of Oracle 7.3.4, now Oracle 11g is too big for any one person to know it all. There's no such thing as a generalist DBA anymore. You know enough to operate anything your organization uses day to day or fix it if it breaks in the middle of the night, but a tricky problem outside your specialist area will need to wait 'til whoever in the company specializes in that can take a look the next day.