> Thinking only changes things if it manifests itself as work of some kind. I never said I "changed" anything. Little bits get flipped on a hard disk somewhere

> Thinking only changes things if it manifests itself as work of some kind. I never said I "changed" anything. Little bits get flipped on a hard disk somewhere, or in a ram chip. A computer spits out a different answer, or a new answer, or retains an old answer. Maybe it answers things it didn't answer before. But "work" and "change", these aren't words I'd ever use to describe that. > Perhaps you are a manager of a team. Nope, just got passed over for that promotion a few weeks ago. > In that case your work is the communication with Nope, that's not work either. Thinking out loud, maybe. > In that case your work is the actual writing of code, testing, debugging, deploying, Not work. My grandfather worked. Tried to farm on and off throughout his life. Also held down a job as a construction worker well into his 60s. He couldn't do what I do (he's pretty sharp, I think he would have had the mind for it... but his fingers are damn near 2 inches wide). To call what I do work would feels like an insult to him. Though I think he's proud that I do what I do, rather than what he did. Work is physical labor. Not everyone is employed to do actual work. Some are in offices, some supervise. They even (often) earn/deserve what they get. Doesn't make it work though. In a way, considering that the software I produce reduces the need for actual work, I do anti-work. Less of it is accomplished because of my efforts.