I am not happy with how programming is done in my part of the industry (Java, Scala, some Big Data, some Docker, some web/Javascript). The work is usually organised in such a way to prevent one from reaching mastery of any specific part of the subsystem - team members are assigned tickets to work all over the system. This means that you spend a lot of the time in parts of codebase where you consider yourself merely a "tourist" and have neither incentive nor time to master it.
I believe that it's not accidental - the companies prefer to have swatches of replacable cogs producing mediocre-to-okish software vs having people who are masters of their respetive domains/subsystems, who can produce good quality product, but who also have lots of leverage when negotiating raises. It is most managers' dream to have a Ford factory level of organization and worker replaceability and in the projects I've worked on it's been pretty much realised.
I wonder if there are still parts of the industry where people are not just resources assigned tickets to work all over giant codebases? I'm thinking maybe small teams working on embedded software/device drivers or other areas where bugs are more costly. I do not know anything about those places though.
I believe that it's not accidental - the companies prefer to have swatches of replacable cogs producing mediocre-to-okish software vs having people who are masters of their respetive domains/subsystems, who can produce good quality product, but who also have lots of leverage when negotiating raises. It is most managers' dream to have a Ford factory level of organization and worker replaceability and in the projects I've worked on it's been pretty much realised.
I wonder if there are still parts of the industry where people are not just resources assigned tickets to work all over giant codebases? I'm thinking maybe small teams working on embedded software/device drivers or other areas where bugs are more costly. I do not know anything about those places though.