PhD CS scientists shouldn't have to be able to code. They are exploring the science of computing, not the implementation.
Developing queueing theory doesn't make you a great coder for Kafka environments.
Working on file system design and new innovative data structures (a persistence and retrieval environment) has nothing to do with writing kernel drivers.
On the other hand, a lot of SE graduates dont want to code, because they think there should be code writing tools and frameworks and infrastructure and process.
They'll spend endless hours talking about those things and focusing on their own needs instead of the actual purpose of the code they're supposed to be developing.
Developing queueing theory doesn't make you a great coder for Kafka environments.
Working on file system design and new innovative data structures (a persistence and retrieval environment) has nothing to do with writing kernel drivers.
On the other hand, a lot of SE graduates dont want to code, because they think there should be code writing tools and frameworks and infrastructure and process.
They'll spend endless hours talking about those things and focusing on their own needs instead of the actual purpose of the code they're supposed to be developing.