News for hackers. Stuff that matters.
Re:Updating classic workplace sabotage techniques by bitwize on Monday May 16, 2016 @03:40AM (#11704841)
You don't become a "deep worker".

Concentrating deeply means you're keeping too much state in your head. Write more tests instead. If it's still a problem, bring a co-worker over, or better yet, pair program. It's not the 1980s anymore, this industry is not for solitary special-snowflake hackers. You're a part of a team -- like a node in a cluster -- and the team's productivity is what matters.

Re:Updating classic workplace sabotage techniques by kristianp on Monday May 16, 2016 @07:07PM (#11710309)
At first I thought this was serious, but I'm not sure now. Surprising that a couple of responses to the grandparent say that programming doesn't require deep focus!
Re:Updating classic workplace sabotage techniques by BurningFrog on Tuesday May 17, 2016 @02:55AM (#11711777)
Trust me, it was surprising experiencing it too!
Re:Updating classic workplace sabotage techniques by blub on Monday May 16, 2016 @06:08AM (#11705336)
It would be nice if those pesky humans could somehow be re-programmed to behave more like the nodes/cogs that they truly are instead of being mere... free-spirited individuals. Then our ideal of the pair-programming, cluster-based corporation would become reality, comrade.
Re:Updating classic workplace sabotage techniques by SmellyGeekBoy on Monday May 16, 2016 @08:44AM (#11705897)
Why stop at pairs? Clustered collective consciousness is the clearly the future of programming. ;)
Re:Updating classic workplace sabotage techniques by bitwize on Monday May 16, 2016 @12:06PM (#11707221)
Hence all the meetings.