
SE Radio 614: Wouter Groeneveld on Creative Problem Solving for Software Development
Software Engineering Radio - the podcast for professional software developers
Deep Work vs. Shallow Work
Taking responsibility for the code you check in is crucial as blaming others is not a valid excuse. Deep work, as defined by Cal Newport, involves concentrated efforts on important tasks, in contrast to shallow work like email and meetings. Creating an environment conducive to deep work, free from interruptions, is essential for maintaining focus and productivity. Research shows that it takes an average of 20 minutes to get back into a state of flow after an interruption, highlighting the importance of minimizing distractions for effective deep work.
00:00
Transcript
Play full episode
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.