Live data from Hacker News

The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

azeria-labs.com

171–180 of 202 posts

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#171
post #87

One of the big challenges that I've always had is creating this habits. I recently discovered an interesting thing: * I use email everyday. It's important that it is clean and not full of shit. I care about it. * At my startup (Happy Scribe), we recently implemented a small feature where the tech team gets emailed/called/sms every 10m if there's any user with a problem, or for wired 5xx request (Stripe style [1]). *…

BEWARE. This app is severely insecure. Nothing against the creators but they clearly don't have much familiarity with web security. I can list things that are obviously wrong with it that they haven't spotted, but even if they fix those, they still are not qualified to store sensitive data, and you should not put sensitive data into this app.

Now, most obviously: go to https://headfocus.herokuapp.com/activities and go ahead and view every activity that is active, by any user of the site. It appears you can also delete or edit them without authentication, though I didn't try.

Again, to the creators of the site: It's a cool idea, I have nothing against you, but you're clearly not qualified to work with other people's data, and I recommend that you stop at once.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#172
post #170

Earlier quoted context omitted.

In my experience, even when managing a team of engineers, it doesn't matter if the people in your nearby open environment are working on the same team or a different team. It's much more about the basic environmental factors (e.g. not having people walking around nearby, having adequate privacy, being able to customize your own lighting, have a personal window to glance out, etc.) Even when there are only 5-10 people…

Environmental noise is much lower with 6 people then with 30. It is huge difference in amount of noise and interruptions. On average, 30 people generate five time as much "weekend golf" discussions and all on-topic debates of other teams are off-topic to you. It is also easier to police interruptions with around 6 people, unless they are jerks - but chance of jerk among 6 is still lower. By policing I mean saying som…

The example of colleges seems odd to me, since it’s a common resource at most colleges to get a study carel or private study room at the library, and it’s a place where even in common areas, there is rather strict enforcement of silence, lack of cell phones, and certainly nothing like modern open plan office noise or distraction.

Also, I think it misses the point to talk about whether or not people can make compromises. The question is about how to empower and enable workers to generate their best output.

For example, you could also say something like, “even though people like having two 27-inch monitors, I find they can make compromises and just use one 17-inch model.”

It’s myopic, because the question has nothing to do with whether or not workers can compromise. It’s about whether it’s cost-effective to pay for quality tools (monitors, offices, private workspace).

So when you say something like, “Just that the average worker should be both able to work in non-perfect privacy and simultaneously not to consistently disrupt those who are focused,” it just misses the mark.

The question is, why would a company wrongly think that providing “non-perfect” privacy is somehow good when empirically it’s known to be bad, even for the company’s own bottom line.

Lastly, I think it’s important to totally avoid framing the desire for adequate private space as if the worker wants “perfect” privacy or they are inflexible and uncompromising. This is a false and worker-unfriendly way to look at it.

Having a private office is not “perfect” or overly demanding to request. Rather an office is just a simple, cost-effective tool. Workers who use offices are still good at compromising to have good communication and collaboration, for example with open door policies, scheduled meetings, and all sorts of non-audio collaboration, in addition to getting to use their extra productive time for dedicated focus on things like code review, to directly collaborate in ways that help the whole team.

Open plan offices on the other hand represent zero willingness to compromise on the part of the employer. The employer is saying they will not invest in good tools for you, and instead dogmatically insist there is only one type of communication (real-time, constantly preemptible audio stream) that is permitted, and anything else has to require contortions and inconvenience on the part of the worker (e.g. working from home, using headphones when it is uncomfortable or distracting to do so, etc.)

So really, we have to move past the anti-employee attitude that a private office is some type of primadonna special request from someone who doesn’t compromise. That is what greedy employers would want us to falsely think.

In reality, an office is just a simple, cost-effective tool literallyno different than ergonomic desk chairs, monitors, or the company’s commuter benefits.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#173

Earlier quoted context omitted.

I'm not sure I agree with this because if it were thus, I think 'most organizations' would be out of business quickly. I think the answer is more plain: shared offices cut cost, and and the resulting immediate an ongoing increase in profit is 'the most important of all benchmarks' for most companies, in fact it's not even a 'benchmark' ... it's 'the point'. So - essentially, 'private offices' are an 'investment' and…

“Deep work” is the vast majority of necessary work for software engineers and knowledge workers in most companies. In fact, these jobs are almost defined by the characteristic that almost all of the work is deep work, requiring privacy, and states of flow. I keep seeing this unsubstantiated claim that deep work is rare, or at least a 50/50 split with shallow work. But it’s flat untrue across the board.

"software engineers and knowledge workers " make up a tiny portion of workers in the economy. Tiny. Is my point.

Also, having written software for quite some time, in my experience would be that yes, at the end of the day, 50% of an Eng time is meetings, standups, blackboard discussions, chatting with others, having breaks/wasting time, eating, going to the bathroom. etc.. I think it approaches 50/50. The other issue being that one simply cannot be 'in the flow' for much longer than 4 hours anyhow, pro musicians don't practice 10 hours a day, more like 3. Though for myself, I can see much greater than 4.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#174
post #152

This is delusional. And to be honest I thought I need the same deep and in the zone kind of work/situation. Until I took this Course which is based on real science: https://www.coursera.org/learn/learning-how-to-learn You can get stuff done, learn very sophisticated topics on a highly distractive environment (though you'll probably need short periods of concentrations here and there). The trick is not to force yourse…

Yes... but I won't do any of those things because whenever I could be doing them I'll read reddit instead, or watch youtube 40k videos.

Perhaps you're the type of person who can just "do" what you've described, but lord knows I can't.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#175

Earlier quoted context omitted.

“Deep work” is the vast majority of necessary work for software engineers and knowledge workers in most companies. In fact, these jobs are almost defined by the characteristic that almost all of the work is deep work, requiring privacy, and states of flow. I keep seeing this unsubstantiated claim that deep work is rare, or at least a 50/50 split with shallow work. But it’s flat untrue across the board.

"software engineers and knowledge workers " make up a tiny portion of workers in the economy. Tiny. Is my point. Also, having written software for quite some time, in my experience would be that yes, at the end of the day, 50% of an Eng time is meetings, standups, blackboard discussions, chatting with others, having breaks/wasting time, eating, going to the bathroom. etc.. I think it approaches 50/50. The other issue…

Why would the relative fraction of jobs taken up by software matter? Most jobs aren’t police officer jobs, but we still give police officers handcuffs and police cars, because (for that subset of jobs) those tools are needed, just like private workspace is needed for the subset of jobs in software.

> in my experience would be that yes, at the end of the day, 50% of an Eng time is meetings, standups, blackboard discussions, chatting with others, having breaks/wasting time, eating, going to the bathroom. etc..

Other than when a company mandates a poor meeting-oriented policy, like mandating Agile meetings even when it’s counterproductive for everyone, I’ve never heard of anything remotely like what you describe.

Mandating an inappropriate Agile-style meeting schedule is common, but that’s exactly the sort of thing I am saying the open plan office engenders. The fact that unproductive meetings make up 50% of work time in these companies is in no way any kind of endorsement that software engineering (or even other) workers actually benefit (in terms of productivity).

In other words, the engineering tasks demand 80-90% deep work focus, but engineers are forced, like a square peg in a round hole, to contort unproductively to wedge that somehow into a meeting-centric company policy that hurts both the engineers and the people who mistakenly organize & believe in the udefulness of the meetings.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#176
post #169
post #152

This is delusional. And to be honest I thought I need the same deep and in the zone kind of work/situation. Until I took this Course which is based on real science: https://www.coursera.org/learn/learning-how-to-learn You can get stuff done, learn very sophisticated topics on a highly distractive environment (though you'll probably need short periods of concentrations here and there). The trick is not to force yourse…

For me, the whole point of college was learning how to learn. Everyone is forced to learn through traditional academic models and everyone tries their best to efficiently digest everything for exams. That said, I sucked at learning in an academic environment, but I learned what did not work for me.

You didn’t suck at learning in an academic environment. You just realized that what your friends are doing is not learning.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#177
post #91
post #67

Earlier quoted context omitted.

The archetypes were the "monastic", "bimodal", etc. Called them strategies, but each is backed by a success. But, if you have evidence that these are more successful than alternatives, I'm game. Where is the evidence? For that matter, what are the alternatives? (Currently typing with my 4mo old. So... apologies for any typos.)

> But, if you have evidence that these are more successful than alternatives, I'm game. Where is the evidence? For that matter, what are the alternatives? The strategies (or archetypes) are just 4 different ways to achieve a focus period for doing some work. Regardless of which you pick, the core thing you look for in each (and possibly others, but those seem quite an exhaustive list of such strategies, or at least t…

Is there mountains of evidence? Seems like mountains of anecdotes. Most famous work was work for hire. And yet we don't hear how getting paid for what you produce helps you produce. Often we hear the opposite.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#178
post #117

Earlier quoted context omitted.

There's a lot of truth and value in that quote, but understanding the context behind it is important. It's boxing - everyone understands they will be punched in the mouth, has practiced getting punched, etc. You need a plan, but have to be able to adapt to changing circumstances. For reference, that quote was given in an interview about his upcoming fight against Evander Holyfield. Holyfield dominated the fight, Tyso…

> "You need a plan, but have to be able to adapt to changing circumstances." +1 Unfortunately, not all us are the masters of our own universe of deadlines. Too often they're semi arbitrary, set by someone who's not aware of the intricacies, etc. The point being, even when you have a great plan to get something done, it might not be good enough in the broader (distorted) context? Then what?

You do the best you can? You are always the master of your dealing with your reality.

Communicate. Express your perspective. Manage your reaction. Master what you have domain over, your reactions to the world. Do not be a slave to disappointment.

Re: The Importance of Deep Work and the 30-Hour Method for Learning a New Skill

#180

Earlier quoted context omitted.

> "You need a plan, but have to be able to adapt to changing circumstances." +1 Unfortunately, not all us are the masters of our own universe of deadlines. Too often they're semi arbitrary, set by someone who's not aware of the intricacies, etc. The point being, even when you have a great plan to get something done, it might not be good enough in the broader (distorted) context? Then what?

You do the best you can? You are always the master of your dealing with your reality. Communicate. Express your perspective. Manage your reaction. Master what you have domain over, your reactions to the world. Do not be a slave to disappointment.

Sou, let's say a new deadline sets you up for failure. You communicate this perspective. You manage the pang of panic, get to work, do your best.

It's still failure.

It's not that you disappoint yourself, since you _knew_ it was practically impossible to succeed. You dealt with your reality, you mastered your domain. People will still get angry and disappointed that the deadline was not met. Not always, but some (most) of the time, you'll end up taking the blame, or even disciplined/fired.

What you're met with is "So what, change jobs, reframe your perspective, grab life by the balls".

This kind of positive thinking does not solve anything. It's simplistic and misdirected. You'll eventually find this situation in every job you take (or make). What can you learn from the experience? No amount of "mastering your reality" will make this a positive experience. Ok, maybe the first time, you learn that you can't always win. But that is all, no lessons learned for all subsequent ocurrences.

Yes, I'm bitter. But you're saccharine.

Not your fault, but i'm sick of seeing this kind of naive responses that belong in mugs or motivational posters.

Post reply on HN