HackerTube.dev

Your Brain at Work

Google TechTalks · 353.4K views · 2009-12-02 · 55:03

Open on YouTube ↗

If playback is restricted in your region, try opening the original video. Use Mark watched to add it to your marked videos.

Overview

David Rock gives a Google Tech Talk based on his book Your Brain at Work, using neuroscience to explain why focus and productivity are hard at the office. He gives strategies for managing mental energy and distraction.

On Hacker News

HN commenters point to it as a general overview of the cognitive science of insight and focus that is useful for developers and knowledge workers.

Recommended by 3 HN people across 2 months · HN mentions 2011–2015

Topics

Search by tags

What people said

jochu · 2011-05 · Recommendation

For more specifics into the cognitive science behind why this is - another good book, which has lots of wonderful references to studies on this topic (amongst other things), is "Your Brain at Work" by David Rock. Or, for the general overview you can watch the Google Talk at [VIDEO]

Read the original HN comment ↗
fredoliveira · 2011-05 · Recommendation

People who are into this kind of thing will probably like "Your brain at work" by David Rock. It covers this topic and a few more - it's pretty interesting stuff for developers and knowledge workers. There's also a tech talk here: [VIDEO] Also, get Pragmatic Thinking and Learning by Andy Hunt. Also covers these topics and helps people understand learning, creativity and how to exploit the way you work and think to, well, learn better.

Read the original HN comment ↗
espeed · 2011-03 · Recommendation

1. It doesn't say Einstein was bad at math, it says his math skills aren't the reason he is considered a genius. 2. The Google TechTalk it references explains "insights from weak associations" in more detail: [VIDEO] 3. If you don't have perspective, how do you know the thing you're focused on is of any importance? You can see practical examples of this everywhere: "One of my favourite tuppences for engineers struggling to find a bug is 'breadth first not depth first'. This can be annoying for someone working through complex technical details, because it implies that the solution is actually much simpler if they only looked...I coined this saying because in software matters I find that if we force ourselves to examine the top level considerations first, before tunneling down into the detail of a particular line of inquiry, we can save enormous time" ( [LINK] ).

Read the original HN comment ↗

Sources

Video by Google TechTalks, played through YouTube.

Data and selection notes

HN summaries and labels may contain AI errors. HN dates refer to discussions, not video publication.

HN Library: HackerTube export (2026-10-31) and open-index/hacker-news. Upstream summaries and classifications may contain AI errors.

Views, duration and playback status refresh separately from the published catalog. When an update fails, existing data remains visible.

Selection checks
  • SaaS & AI candidates: Topic keywords do not match
  • Editor-approved picks: Editorial review is required

Rule matches identify candidates. They do not guarantee video quality or financial results.

About the library and its sources