Live data from Hacker News

Deep Work and the 30-Hour Method for Learning a New Skill (2018)

azeria-labs.com

91–94 of 94 posts

Re: Deep Work and the 30-Hour Method for Learning a New Skill (2018)

#91
How to achieve a flow state easily:

0. Exercise (+5min HIIT)

1. Turn-off distractors (ex. notifications, dumbphone, etc.)

2. Breathe & drink a glass of water

3. Put a timer with your effort (Forget pomodoro!)

4. Put the tab your working on

5. Press F11

6. Start working

7. GOTO step 2. IF sleepy or tired add step 0.

Re: Deep Work and the 30-Hour Method for Learning a New Skill (2018)

#92

Earlier quoted context omitted.

> Do you tell managers this as well? That the developers need deep focus time? It's a delicate balance. When I was in a manager-of-managers position, I didn't explicitly micromanage how managers ran their teams or run their days. People don't respond well to that. Instead, I tried to lead by example by setting my own focus hours, giving ample notice for upcoming meetings, setting expectations for response times at th…

> When I was in a manager-of-managers position Why did you quit your manager-of-managers position?

Not OP, but have limited experience in a manager-of-managers role.

For me, it's miserable. It's like knowing work is being done, but you aren't there doing it. You don't always properly understand it, the people you're managing don't, and it feels like you're the bureaucracy slowing things down.

For me at least.

/rant

Re: Deep Work and the 30-Hour Method for Learning a New Skill (2018)

#93

It's easy to dismiss "Deep Work" articles for their use of buzzwords and pop-psychology, but this sort of structured language really does help drive the point home for some people. The core concept of Deep Work isn't really controversial. Everyone knows that hard problems require focus, but that doesn't seem to stop people from surrounding themselves with notifications and distractions. It also doesn't stop many comp…

Mainly I don't like that the term is just used to sell stuff, like books, now. The entire idea can be encapsulated in two words: deep work.

Re: Deep Work and the 30-Hour Method for Learning a New Skill (2018)

#94
post #84

It's easy to dismiss "Deep Work" articles for their use of buzzwords and pop-psychology, but this sort of structured language really does help drive the point home for some people. The core concept of Deep Work isn't really controversial. Everyone knows that hard problems require focus, but that doesn't seem to stop people from surrounding themselves with notifications and distractions. It also doesn't stop many comp…

I like this idea of phrasing it as branding. In my experience nobody sits in one place and works on one thing for 8 hours a day. I am tempted to say that it's not only rare but it's undesirable. I can work for approximately 5 hours straight without needing any sort of break; but part of becoming a more senior developer was to realize that this is actually a really bad thing for me. The “sweet spot” for me appears to…

The article itself suggests breaking deep work sessions into no more than 4 hours at a time and suggests several "styles" of performing deep work in terms of fitting individual schedules and personality.
Post reply on HN