This is the second shallow article I've read today about deep work. I'm starting to think it's a worthwhile shallow activity to produce content about deep work.

This is the second shallow article I've read today about deep work. I'm starting to think it's a worthwhile shallow activity to produce content about deep work. I think Deep Work makes sense if you are thinking about a hard CS problem, coming up with a strategy for a company, or doing something that requires a lot of attention. It could be something hard for you, just because you don't know how to do it, but easy for somebody that has done the same thing ten times before. I disagree with Newport that Deep Work would be a competitive advantage in the tech industry. Most of execution on a project is "shallow work" or another word that people like to use is "grinding". Deep work or uninterrupted thought is needed for people who are domain experts to come up with a strategy and vision. However, if that's correct, then it's time to grind.