Found 10 results for "tag:deep_work"

• 4 simple software engineering habits that transformed my productivity

  https://read.engineerscodex.com/p/simple-software-engineering-habits?utm_source=hackernewsletter&utm_medium=email&utm_term=working

  A breakdown of 4 simple software engineering and coding habits that improved my productivity. These include keyboard shortcuts, learning to say no, reaching flow state faster, and keeping a big book of commands handy.

  deep_work

• Context-switching is the main productivity killer for developers

  https://newsletter.techworld-with-milan.com/p/context-switching-is-the-main-productivity

  I am programmer, interrupted.

  deep_work

• Deep work. Essentialism in asynchronous culture

  https://jorzel.github.io/deep-work-essentialism-in-asynchronous-culture/

  Deep work Nowadays, we are getting accustomed to working in a continuously interrupting environment. Smartphone notifications, hundreds of e-mails, open spaces, and meetings slicing our workday. We are feeling busy, and overworked, but are we more productive? If I am a salesman or project coordinator that way of working can bring good effects and even improve my skills. However, for Software Developers, Designers, and other professionals that need a quiet environment for creative effort, it can lead only to frustration and burnout. They need something that is called deep work. Deep work is a concept popularized by Cal Newport in his book under the same title published in 2016. The author divides mental activity into two categories: shallow work, that does not need intensive concentration like sending e-mails, formatting documents, chatting using communicators, etc. deep work, that demands distraction-free focus on one task like writing a document, learning a new skill, designing a software system, etc.

  deep_work

• It takes 23 mins to recover after an interruption

  https://addyo.substack.com/p/it-takes-23-mins-to-recover-after

  It’s time to examine the good, the bad, and the very ugly elements of context switching. Even better, we’ll take a look at some strategies for managing it.

  deep_work

• The surprising connection between after-hours work and decreased productivity

  https://slack.com/intl/en-gb/blog/news/the-surprising-connection-between-after-hours-work-and-decreased-productivity?utm_source=hackernewsletter&utm_medium=email&utm_term=working

  Slack’s Workforce Index uncovers new findings on how to structure the workday to maximise employee productivity, well-being and satisfaction

  deep_work

• Why do programmers need private offices with doors? (Do Not Disturb)

  https://blobstreaming.org/why-do-programmers-need-private-offices-with-doors-do-not-disturb/?utm_source=hackernewsletter&utm_medium=email&utm_term=working

  It’s a common occurrence: You’re sitting at your desk, lost in thought, trying to solve a problem that’s been blocking your work all week. Overcoming depressionThere are often discussions on Hacker News about depression or suicide. Lots of the comments give helpful advice from people who have

  deep_work

• You can code only 4 hours per day. Here’s why.

  https://newsletter.techworld-with-milan.com/p/you-can-code-only-4-hours-per-day?utm_source=weekbyte&utm_medium=email&utm_term=2026-02-24&utm_campaign=Why%2Byou%2Bshould%2Bonly%2Bcode%2Bfor%2B4%2Bhours%2Ba%2Bday%2Bhow%2BClawHosters%2Bwas%2Bbuilt%2Band%2Bthe%2Bcomplete%2Bguide%2Bto%2Bbuilding%2Bskills%2Bin%2BClaude

  Most of us have felt it: after a few solid hours of coding, your brain starts shutting down.

  deep_work

• https://deerflow.tech

  https://deerflow.tech

  deep_work

• https://docs.langchain.com/oss/python/deepagents/overview

  https://docs.langchain.com/oss/python/deepagents/overview

  deep_work

• https://zettelkasten.de/posts/the-scam-called-you-dont-have-to-remember-anything

  https://zettelkasten.de/posts/the-scam-called-you-dont-have-to-remember-anything

  deep_work