I wonder if any of this is related to the growing hyper-specialization in the industry. When my dad finished grad school in engineering he did a lot of work in

I wonder if any of this is related to the growing hyper-specialization in the industry. When my dad finished grad school in engineering he did a lot of work in military radio communications and engineers were expected to be able to design all of the equipment (including certifying the plans for the transmission towers) and get the entire system working. Being a "programmer" used to mean something similar, we took responsibility for getting everything done. I took a course a few years ago on an "enterprise" development tool and asked a question about how the sample code mapped to fields in the database. The disappointing answer was that I "didn't need to worry about that" because that is something that the database engineers and deployment engineers would handle. Apparently I was supposed to be grateful that my role had been compartmentalized. Now programmers identify themselves as "Language X Developers," or even by their project roles, e.g. "Implementation Manager," "Software Architect." It is time to be a bit more bold. I am a Programmer. Capital P, full stop. Any language, any system, any project, any time.