The article seems all over the place. For example I think the conclusion
"""This is why we see so many developers that can't pass FizzBuzz: they never really had to write any code."""
Doesn't really follow from the previous parts. DevOps is not the reason for this nor is the full stack developer trend.
The author also seems to start from an implied base premise that developers wouldn't do devops/fullstack if they had a choice. I disagree with that. Many developers are very interested in understanding the implications of their code better (more DBA skills help a ton for example) and quite a few gasp actually enjoy devops or understanding the entire product from start to finish at least on some level (full stack).
The benefits of DevOps also seem to be completely ignored. It's precisely the fact that common development best practices are integrated with sysadmin, dba etc. knowhow which makes it useful. It's not just "let the dev be a sysadmin in a pinch". It's systematically improve things by automating them (following development best practices instead of the hacked together bash script approach).
DevOps and fullstack dev are conflated throughout the entire article in a strange way which makes it kind of hard to argue.
"""This is why we see so many developers that can't pass FizzBuzz: they never really had to write any code."""
Doesn't really follow from the previous parts. DevOps is not the reason for this nor is the full stack developer trend.
The author also seems to start from an implied base premise that developers wouldn't do devops/fullstack if they had a choice. I disagree with that. Many developers are very interested in understanding the implications of their code better (more DBA skills help a ton for example) and quite a few gasp actually enjoy devops or understanding the entire product from start to finish at least on some level (full stack).
The benefits of DevOps also seem to be completely ignored. It's precisely the fact that common development best practices are integrated with sysadmin, dba etc. knowhow which makes it useful. It's not just "let the dev be a sysadmin in a pinch". It's systematically improve things by automating them (following development best practices instead of the hacked together bash script approach).
DevOps and fullstack dev are conflated throughout the entire article in a strange way which makes it kind of hard to argue.