It's fine if line work + hardcore CS positions exist simultaneously. This fighting over the boundaries of where the profession starts and ends is tiring and we should just accept there's a stratification of developer skill levels and start adjusting our attitudes and training accordingly. Development is all of these things because development is a huge job market.
You can't abstract your way out of doing the line work and only have hardcore CS positions in the job market.
Huh, it is already happening. I see everyday so many web services are created via auto generating scaffolding tools like Spring boot etc. One just fill in environment details, bits of JSON parsing and service is ready to be deployed.
Good for you that where you work people are intelligent enough to read Fred Brooks. Most places, including the ones with fancy gleaming buildings, open office floors, lounges with couches and organic smoothie bars are just making CRUD services with some cloud backed data storage. More so terminology I see at work is more inspired by factory floor not some intellectual venture.
If all it took was some scafolding, some database columns and some html and sprinkle, you should be a millionare by now?
There is constant, never-ending pressure to turn it into line work and we need to be aware of it. A lot of software running (barely) in the real world is written this way.
We should not build complex systems that way, but plenty of systems are not very complex.
To write good code, you need to understand the whole program (or at least a very substantial part of it), why certain decisions were made in the past, the potential ripple effects of a “simple” change, etc.
This means that it’s impossible to just swap devs out like factory line workers, otherwise you’re just creating more bugs.
For similar reasons, you can’t paint half a canvas and then hand it over to another painter and have him finish it...
It's easy to write them, but writing the right ones is much harder. Automate or outsource that and you become a trillionaire. Yes, seriously.
Agile do not make developer replaceable. If anything it empower developers to become on equal footing with everyone else.
> And sure, the next developer may fill less cards, but they will improve with time.
I saw projects outsourced to huge teams in India failing to deliver. Reality of software development is that unless you have right mix of experience, skill and people you might never deliver.
Programming require both engineering and creative skills. Some class of problems cannot be brute forced by large number of young bodies.
I'm not saying that this actually works better, to be clear. But I would bet it works cheaper for the time horizons that the folks making those decisions care about.
Toxic companies will twist a good process and make it horrible. It is not Agile or Scrum to blame.
Doing so in an attempt to commodify its application is not inherently bad.
Doing so in an attempt to commodify its application is definitely bad for developers' careers.
"Commodify of application" is a good thing. This means that your team is flexible and can adapt to changes. It mean that there little of key person dependencies. It makes you go for holidays without worrying that your team will be able to finish a new service because you are one of two people that can navigate AWS :P
Just a perspective thing I wonder
That's why I equated Sysads as service workers. Some assistance may be 5m, and others may have looked like a 10m issue but turns into 3h timesink. We're serving others, or serving machines for serving others.
Whereas I see Agile, or the Kanban system, to be set up to send work to either internal or external devs. The only reason why real factories don't use international work is because sending lines and parts is onerous on a short cycle... Whereas software Kanban seems fit for each other.
Sure there's dev work that requires specialty knowledge, but most dev work is a CRUD web app with a DB backend. And those jobs are especially prone to outsourced via a thousand cuts.
Sure, the professional developers are paid well. However the more Jira and agile ideas takes over, you become more replaceable. Why? You're just a card-filling machine dealing with feature requests or problem reports.
And sure, the next developer may fill less cards, but they will improve with time.
And if you don't work in a protected area (federal, etc), then you can buy card-filling devs for 1/5 to 1/8 of US... And have them QA'ed for less than 1 USA dev.
Face it: I, a sysad, am a service worker. And devs are line workers. We're well paid, but so were factory workers at one time.