I can certainly see a lot of parallels with Oculus / Facebook.
Perhaps unusually, I actually wanted FB to impress itself more strongly on Oculus post acquisition because, frankly, Oculus was a bit of a mess. Instead, Oculus was given an enormous amount of freedom for many years.
Personally, nobody ever told me what to do, even though I was willing to "shut up and soldier" if necessary -- they bought that capability! Conversely, I couldn't tell anyone what to do from my position; the important shots were always called when I wasn't around. Some of that was on me for not being willing to relocate to HQ, but a lot of it was built into early Oculus DNA.
I could only lead by example and argument, and the arguments only took on weight after years of evidence accumulated. I could have taken a more traditional management position, but I would have hated it, so that's also on me. The political dynamics never quite aligned with an optimal set of leadership personalities and beliefs where I would have had the best leverage, but there was progress, and I am reasonably happy and effective as a part time consultant today, seven years later.
Talking about "entitled workers" almost certainly derails the conversation. Perhaps a less charged framing that still captures some of the matter is the mixing of people who Really Care about their work with the Just A Job crowd. The wealth of the mega corps does allow most goals to be accomplished, at great expense, with Just A Job workers, but people that have experienced being embedded with Really Care workers are going to be appalled at the relative effectiveness.
The communication culture does tend a bit passive-aggressive for my taste, but I can see why it evolves that way in large organizations. I've only been officially dinged by HR once for insensitive language in a post, but a few people have reached out privately with some gentle suggestions about better communication.
All in all, not a perfect fairy tale outcome, but I still consider taking the acquisition offer as the correct thing for the company in hindsight.
Often workers are perfectly capable and eager of Really Caring but then the company incentives and politics force them into Just A Job category. Especially when joining Big Tech not via acquihire.
Thanks for sharing this. It just goes to show that even the best of us can find it difficult to effect change in a big company. The nature of a large organization is it requires lots of communication, alignment, and on-the-ground politics to make things happen, which is definitely a challenge for those of us who just want to get shit done.
> The wealth of the mega corps does allow most goals to be accomplished, at great expense, with Just A Job workers, but people that have experienced being embedded with Really Care workers are going to be appalled at the relative effectiveness.
I think the problem is actually deeper than that. I've spent much of my career avoiding megacorps, or even just corps, because I find them pretty frustrating. I have though worked at a couple of larger companies - one of them very large - as much to see what I could learn as anything else.
I sit somewhere on the spectrum between "Really Care" and "Just A Job", and it's varied quite a lot depending on what I'm doing and who I'm working with.
The problem with big companies is the "Really Care" gets beaten out of you: if you show any initiative whatsoever to try to get ahead of a situation or help another team you pretty quickly get shut down and told to stay in your lane.
Big companies tend to fragment and specialise responsibilities, if not actual skills.
Related to this hardly anyone has any decision-making power which means that any change requires a combinatorial explosion of interactions between individuals and teams to happen regardless of how competent or committed those individuals are.
It just favours mediocrity and coasting, along with a high tolerance for boredom, because there often isn't a viable alternative course of action for many employees no matter how good (or bad) those employees might be in another context working for another company. Sometimes you're in the right place at the right time, or have a conversation with the right person, to make something happen.
Another related issue: the vast majority of employees at big companies have no concept of the value of time, which manifests itself in all kinds of ways, but ultimately results in the performance of large quantities of BS/non-value adding work. If you're employed by a smaller company working in partnership with a larger company the asymmetry in understanding of time's value becomes particularly stark: you can often find yourself wondering why these people at the larger company feel so free to waste so much of your time asking you to do things that aren't valuable to the partnership or to the success of either company, or asking you to have the same conversation over and over again with different groups of people.
Back on point, the corporation has to "make do" with "Just A Job" workers because, in large part, the corporation creates them regardless of their initial state of motivation.
While I totally agree with your Really Care and Just A Job characterization, I think that money does play a significant role in overall picture. People behave very differently after they run into six, seven, eight figures. And that behavior isn’t perfectly correlated with how much they put into the job. There’s a fair place for the “entitled” narrative, and when these people have outsized leverage on the company or product, it can create outsized problems.
Joel on Software used to explain that rich entrepreneurs always sound passionate, but it is useless to try to emulate passion, because a big success can make someone passionate for anything. (...and I confirm – since we make 70k€ a month per cofounder, I became more passionate).
A million dollars or some other significant sum of money doesn't nourish the soul the same way something you're actually passionate about does. You can fake it for a long time, but it's never quite the same, at least that I've found.
> but it is useless to try to emulate passion, because a big success can make someone passionate for anything. (...and I confirm – since we make 70k€ a month per cofounder, I became more passionate).
I remember reading an article about a Chinese cockroach farmer that incidentally described how his wife said the cockroaches were misunderstood. "Look how shiny they are!"
I imagine it helped the cockroaches' case that, by her standards, she was rich and successful.
sorry, downvote, that just so viscerally doesn’t ring true. the sibling comment speaks of soul nourishment. yes. at the level of 400k, 1M, 4M it’s a fucking digit on a screen in your bank’s app. come on now...
my experience is the absolute reverse direction. money is so very numbing
But as someone who recently bought a Quest 2, it really is an amazing product, so some things there must have been very right. In retrospect, do you know what those things were?
Honestly, I doubt the Quest line of products would have launched when they did with such a low price if FB was not running the show. Quest 1/2 might not even exist at all. The original founders were mostly focused on PC VR. Carmack was the odd one out in that respect in pushing for standalone VR (as can be seen with the Samsung GearVR).
For what it it’s worth, I was part of the founding team and led the hardware development of Rift, but also kicked off the hardware architecture of Quest 2 (and the original Quest). As much as many of us were and are PC people, by the time we started Quest 2, everyone who was left had come around to standalone.
I was an early backer of Oculus having bought the DK1/Dk2 back in 2012/14 and I was so perplexed when they announced they were putting effort into a mobile headset. It made no sense to me until I put the Oculus Quest 2 on my head last October 2020 and I learned a massive lesson!
There is a third group. Programmer as Artisan/Craftsman they recognize that it is a just a job, but they care about quality and their work most. People that would invest countless hours into their craft and would build applications that provide high value for both users and employer. They are mostly immune to corporate bullshit and have great IC careers.
People that have worse are "Just a Job" crowd that lack real programming skill. They would be quickly hit by ageism and their careers stuck very quickly on Senior Developer position because they do not care enough to be promoted into management.
>Personally, nobody ever told me what to do, even though I was willing to "shut up and soldier" if necessary
i wonder who at FB has the cachet to tell such thing to John Carmack. Zuck probably had the poster of John Carmack on the internal mental wall while going to middle school.
Like happiness, work ethic varies by individual overtime. With happiness, people who won the lottery and people who lost a limb were tracked. After a year (after their windfall or trajedy) each was just as happy orbsad as they were prior to the event. Some folks are happy go getters, some are slackers & whiners. The art of leadership is helping the later become the former so they can truly succeed in life (it’s not always about the explicit compensation package, but fairness helps). The leader needs to be clear about the role, deliverables and boundaries of each member of the team and use a framework (like Agile) to keep them in sync to meet spec, time & cost targets aligned with a shared vision to which all are committed. If you’re heart is not in your work, if you’re not living your dream, do yourself a favor and change leaders, projects, companies or career. Life is too short to sell your time to “work” at something for which you have no passion. Get a dream & follow it. The purpose of life is to struggle at what you love, progressing toward a worthy goal. And if being a parent is part of your dream, being a very good one. BALANCE. No one is perfect. We learn from our mistakes and move on. No regrets or sour grapes. Just loving kindness and respect for one another.
Just curious, what things did you want/expect FB to be more hands-on about? General things like company organization, or more specific product decisions (I'm thinking of one particularly controversial product decision but I understand if that's a sensitive topic)?
I suspect he won't want to get into thorny PR issues, but probably company organization. It's easy to imagine a disorganized startup scaling poorly, and those within it wanting guidance from highly-scaled FB.
> people who Really Care about their work with the Just A Job crowd
These aren't discrete categories.
There are a lot of people who care about their work and also recognize that at the end of the day, it is a job, and the reality is that they can only play a role in shaping the outcome, not dictate it per their vision.
Also, depending on the job, the team, the project, and the product, people can go from one of those perspectives to the other. There are a lot of people whose current job/role situations aren't intrinsically motivating, but then find incredible motivation due to a change in project or role (I've experienced this multiple times).
> but people that have experienced being embedded with Really Care workers are going to be appalled at the relative effectiveness.
Unless you've experienced the Really Care type of team and situation, it's difficult to understand.
I don't mean any disrespect to the Just A Job people. There is nothing wrong with keeping your head down, getting your work done, and checking it at the door when you sign off at 5PM Monday through Friday. Frankly, that's the correct approach for most people.
However, there really are situations and teams where people won't stop until they can get the outcome as close to their vision as possible.
In my experience, this is far more likely to happen at small startups where members have reasonable equity to work with, as well as significant career upside for accomplishing the big tasks. Large companies like Google are so big that finding upside or even a niche to influence can seem impossible. Combine that with guaranteed high income and the motivation to do work that goes above and beyond gives way to a motivation to be associated with the right projects at the right time, regardless of your contribution.
When I look back, the happiest time of my career was when I was embedded among people who Really Care, trying to accomplish a goal that was likely to fail, working well over 40 hours a week (my choice), and not getting paid much. I've since moved to much higher compensation at bigger companies, but I'm often tempted to give it up to get back to a situation that sparks that kind of motivation and happiness again.
Definitely a spectrum. I think my Level Of Care is directly proportional to how much impact I can actually have, given where I am on the reporting chain totem pole. Where I am on the totem pole often correlates strongly with salary/equity. If I'm down at the bottom, and my impact is limited to moving protobufs from one level in an abstraction stack to another, and my equity's value ebbs and flows with whatever the company is doing, I'm more of a Just A Job person. If I'm CTO of Oculus, I'm probably much more on the Really Care side, because in that case I probably have significant equity and the things I do might actually affect the company's stock price. Want me to care? Let's talk about where I am on the totem pole and how strongly my actions have a direct impact on the company's success and its stock price.
I am a finance guy... majored in it, worked at Merrill Lynch, and spent the last year building a trading program. I think mergers and acquisitions, venture capital, private equity, etc. actually greatly damage economic growth. Generally all of those finance activities serve to prematurely remove founders from leadership and take skin out of the game.
I think one aspect we're not mentioning is the nature of the projects themselves.
This spectrum of Really Care vs Just A Job isn't entirely accurate. A lot of projects are honestly just hard to "really care" about. The technical work is uninteresting or the mission itself isn't interesting. The monetary goal of success could be the most interesting aspect (i.e. your startup makes it big and you're rich), but the day to day could just not be that compelling.
Over enough time, you will naturally go from a Really Care person to a Just A Job person given the right project environment. The novelty of a job will wear off.
There's no nobility in trying to really care about everything you are paid to do.
> When I look back, the happiest time of my career was when I was embedded among people who Really Care
I think people who Really Care are as much a product of the environment as they are responsible for creating the environment. I Really Care about what I work on, and I try very hard to make it the best option out there, giving it a huge portion of my creative energy and not just keeping my head down and turning a crank, but I also recognize that in the end, it's also just a job.
Why so? I think this is the way to be promoted/lead things. You don't have to live and die with your project but there are definitely a few opportunities that are opening up if "you care and army that doesn't". I believe calling your colleagues "army that doesn't care" is a bit disrespectful and this is what is wrong with "I care so much" people at big companies.
upd: I did generalize "I care so much" people as well; but I do consider myself one.
This sounds like a nuanced view, but I think you have missed the point - we're using terminology that allows for us to talk past each other and that's part of the problem.
At least in my experience, the Just A Job crowd are generally _very_ vocal about their view that this is Just A Job. Their worldview is not compatible with the worldview of people who Really Care. There is a very healthy middle ground of people who (in NON CAPITAL LETTERS) both really care and for whom this is just a job, but they don't _identify_ with those as their primary worldview.
Even if you really care, you can be vocal about things that make it sound as if you don't, in order to e.g. make another developer stop stressing and go home when they've reached the point where they're creating more work than they're getting done, or encourage greater levels of risk-taking by pointing out that the only thing at risk is your job. Perhaps I'm misinterpreting what you're saying, though.
I think the impedence mismatch may also be that among the Really Care group, there are those who think that people in the Just a Job crowd have a sort of moral responsibility to find a job where they Really Care.
That's, imo, an unreasonable requirement, but if you're super passionate about something, I can see why someone might see it.
It's also possible to really care in a way that doesn't match up with what the company wants. Let's say you work at YouTube and really care about the user experience - you probably wouldn't want to introduce first one, then multiple mid-roll ads. If that's your job, "really caring" is going to burn you out.
I don't think you can separate people who really care about their job vs. people who really care about the company they work for and the mission it's on. Part of the problem could be that you loved the job but not the mission of the company, in which case there is almost no outcome that leads to a happy ending. In other words if the company has a worthy mission it almost doesn't matter what the job is.
My primary concern is for immersive VR media on our Go and Quest platforms, which use Snapdragon 821 and 835 SoC, respectively. The 821 doesn’t support 10 bit on anything, and the 835 only supports it on h265. Software decoding a 4k60 video on mobile isn’t an option, and you can see every bit transition with dark adapted eyes in a vr headset, so getting full 8 bit range is pretty valuable.
You forget to mention which colorspace you're using. It matters.
From Rec. 2020 wikipedia article:
Since a larger color space increases the difference between colors an increase of 1-bit per sample is needed for Rec. 2020 to equal or exceed the color precision of Rec. 709.
The "correct" solution is to use a modern colorspace (rec 2020) with 10 bits encoding (or 12 bits, if you can). UHD standard mandates at least 10 bits.
On the '821 you could gain 1 bit by degrading to an older color space - 709.
Full 0-255 range should never be used - they are invalid according to the standard. None of the hardware codecs are validated for 0-255 - you're asking for trouble here. Expect ghosting and weird motion artifacts accumulating from one I-frame to the next I-frame.
I was prepared to blend the edges, but it turned out not to be necessary. If the compression ration was increased enough that there were lots of artifacts in the low res version it might be more important.
I was originally going to put it into an mp4 file with the base stored first, so normal video players could at least play the low res version, but the Android MediaExtractor fails when presented with more than 10 tracks, so I just rolled my own trivial container file.
Peak bitrate for Henry is around 40 Mbps, so it wouldn't stream for most people. With some rearrangement of the file so each strip has a full gop continuous, instead of time interleaving all 11, the bitrate wold be cut in half, but it would still be a lot of fairly small requests, so it would call for pipelined HTTP2.
Ah, so all the frames for every strip are interleaved in your container, and you just read sequentially and ignore the frames you don't need? That's probably the right thing for local videos.
I had each gop in a separate file like HLS or DASH (except for the background which was a single file also containing the audio track). It's unwieldy but makes HTTP streaming a little simpler because you don't need range requests or an index.
Also, instead of bitstream hacking to stitch three strips into one, I encoded multiple strips into "pre-stitched" views. This means that every strip is encoded redundantly in multiple views, bloating the on-disk video size. But for streaming that only affects the server, not the client, and it's nice for the client to only download/decode one view at a time (plus the background) instead of three strips. Bitstream hacking to join the strips would definitely be better if it can work, though.
In the center of the lenses, the circumference resolution is a bit over 5120, but definitely less than 5760. Even at 5120, it is a bit overkill (and potentially aliasing) at the edges: https://twitter.com/ID_AA_Carmack/status/975198157838499840
You are off by a factor of 2 in your pixel calculation, because 5k x 5k is for a stereo pair of spheres. Equirect projections waste a fair amount, but compared to the 300% miss to get to 60 fps stereo, it isn't dominant.
Need some form of RGB+D for that. I have a player for that, and sometimes it looks fantastic, but the silhouette edge artifacts can sometimes look really bad. Considering some ways of "relaxing detail around the edges".
Would we ever see a dynamic resolution that tracks where you are looking at and just lowers resolution outside the point of interest? Wouldn't that save a lot?
The article is about doing that for pre-recorded video. For live 3D VR rendering, it's already in some game engines. Batman Arkham VR uses it (it's in the settings). More info https://www.youtube.com/watch?v=gV42w573jGA
No, Exynos has the same block limit as the snapdragon chips -- 4k60. The difference is that Exynos doesn't have the same 4096 maximum dimension limit, so it can do 5120x2560 (monoscopic) at 30 fps, while snapdragon can only decode 4096x2560 at 30 fps. The view dependent player is about playing 5120x5120 (stereo) at 60 fps.
I just tried, and while it does decode a 6kx3k 60 fps video, which is very admirable, it doesn't hold 60 fps while doing it. There are probably encoding options to minimize work on the decoder that could let you push it a bit more.
MediaExtractor seems to be arbitrarily limited to a lower resolution, but that can be bypassed.
It was a loaded question, but that doesn't mean that the post was necessarily unbiased. It could have been an attempt to get Zuckerberg to like him, say. Not a likely possibility, but one nonetheless.
Years ago, I felt burned when I wrote several articles for #AltDevBlogADay, and they vanished. I have much more confidence that what I write on FB won't vanish. I agree it isn't a great platform for writing, but I only write public long-form things a few times year, so I don't feel like going to another platform for it.
> I have much more confidence that what I write on FB won't vanish
But it's already not very accessible (almost vanished) without a facebook account. I couldn't find an index to other writings (in fact I didn't come up with a google query to find any of your other writings). I like these stories. Thank you.
I specifically remember your quote "It is always better to not have a problem than to mitigate it" from the "Latency Mitigation Strategies" post on #AltDevBlogADay. It was so poignant to me that I wrote it on a post-it and stuck it to my monitor, where it remained for several years thereafter. Bummer that that content is no longer available (although I found a mirror of that particular post here: https://www.wired.com/2013/02/john-carmacks-latency-mitigati...)
I sincerely wish you would put also this outside of Facebook. Anyone who doesn't have a Facebook account or is not logged in would have a really terrible experience viewing this page and reading it. Facebook is very hostile to user experience on this matter, occupying a large amount of screen space for its own banner and making it difficult to read, unlike any other large platform I have seen. I urge you to check this out for yourself. I believe that history and heritage like this shouldn't be subjected to such obnoxious schemes and experiences.
If longevity is your only concern, you could create a blog on Wordpress.com (which has been around longer) and pay about $20 or so a year to have your own domain as well.
Looks like the m.facebook.com link is a bit less annoying, though it also has the Login/Join popover. On a desktop browser, reading public posts (and pages) is very painful, with nearly one third of the screen always occupied by the Login/Join popover that also makes navigation difficult.
[This is easier to understand through direct experience.]
Right, I was on desktop, but I missed that the link above was to the mobile version (m.facebook), which did not had the login popover, which is very annoying on the desktop version.
Maybe someone will write a metablogging platform that posts to WordPress, Facebook, Twitter (in multiple tweets!), Instagram, etc. all with one button. RAIC, redundant array of inexpensive content.
Actually, I'd be surprised if this didn't already exist.
Hey John, thanks for Doom and Quake. I had lots of fun, and you and Abrash introduced me to 3D rendering techniques and advanced assembly programming techniques for which I am grateful since those skills put a little bread on the table long, long ago.
Would you ever team up with Romero to make another game? I'd love to see your guys' take on a battle royale game. I'm having lots of fun with PUBG, but a game like that needs your engine optimization-fu.
I am aware that my presentations aren't optimal for communicating targeted information, and it does weigh on me more and more as the years go by.
So far, I haven't been able to justify to myself the time required to do a really professional job, so I just show up and talk for a few hours. I like to think there is some value in the spontaneity and unscripted nature, but I don't kid myself about it being the most effective way to communicate important information.
I'm taking some baby steps -- I at least made a rough outline to guide my talking at last year's Oculus Connect instead of being in full ramble mode.
Ha, it's funny because for me the format is just perfect. There are numerous presentations on the internet focused on one specific topic but your free form style is just like I'd talk with a friend. The interdisciplinary nature and hands on examples are nice added bonus.
Please don't change this unique approach too much.
Actually I really like the format of your presentations: just yesterday I watched your live coding session with vrscript (https://www.youtube.com/watch?v=ydyztGZnbNs) and it was fantastic because, first, you were showing to your audience how to work with Racket (and some of the features in DrRacket), and second, you build from zero a demo in a very casual, easy going way. I honestly don't think that a standard slide-based presentation would have been better in any way...
While this may be true, please don't let it cause you to shy away from "full ramble mode" when the opportunity presents itself! I know I speak for many when I say that I have learned much from hearing these sorts of talks of yours over the years. Your willingness to share your wealth of experience is inspirational, regardless of the format.
Agreed, full ramble isn't something many people do well and it's fun too watch. Random but useful information will fall out of peoples brain and it's great!
Along the lines of 'functional' programming, Jonathan Blow reposted an old email of yours which I thought was a nice format for getting across some points about reliability, consistency, and minimizing side effects:
Just to say, from my perspective I love your talks, zero distractions, just a long cogent train of thought to follow. Please don't feel the need to make too many changes.
For me, at least, it's not a problem that it doesn't optimally communicate targeted information. I watch talks like this for entertainment and maybe to pick up some information by osmosis and the undirected style is good for that. This was a very good talk by the way, and reinforced my positive feelings towards functional programming, thanks for doing it.
Really interested in hearing if the ideas on how to transform game programming into a more productive form panned out. Did you end up using the ideas in a later product?
Actually I prefer it a lot more to something scripted. It's normally hard to stay focused watching a guy talking for 1 hour on a youtube video. But with your presentations, I find myself looking for more at the end of the hour!
I find these “shorter work weeks are just as effective” articles to be nonsense, at least for knowledge workers with some tactical discretion. I can imagine productivity at an assembly line job having a peak such that overworking grinds someone down to the point that they become a liability, but people that claim working nine hours in a day instead of eight gives no (or negative) additional benefit are either being disingenuous or just have terrible work habits. Even in menial jobs, it is sort of insulting – “Hey you, working three jobs to feed your family! Half of the time you are working is actually of negative value so you don’t deserve to be paid for it!”
If you only have seven good hours a day in you, does that mean the rest of the day that you spend with your family, reading, exercising at the gym, or whatever other virtuous activity you would be spending your time on, are all done poorly? No, it just means that focusing on a single thing for an extended period of time is challenging.
Whatever the grand strategy for success is, it gets broken down into lots of smaller tasks. When you hit a wall on one task, you could say “that’s it, I’m done for the day” and head home, or you could switch over to something else that has a different rhythm and get more accomplished. Even when you are clearly not at your peak, there is always plenty to do that doesn’t require your best, and it would actually be a waste to spend your best time on it. You can also “go to the gym” for your work by studying, exploring, and experimenting, spending more hours in service to the goal.
I think most people excited by these articles are confusing not being aligned with their job’s goals with questions of effectiveness. If you don’t want to work, and don’t really care about your work, less hours for the same pay sounds great! If you personally care about what you are doing, you don’t stop at 40 hours a week because you think it is optimal for the work, but rather because you are balancing it against something else that you find equally important. Which is fine.
Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week, is going to achieve more. They might be less happy and healthy, but I’m not even sure about that. Obsession can be rather fulfilling, although probably not across an entire lifetime.
This particular article does touch on a goal that isn’t usually explicitly stated: it would make the world “less unequal” if everyone was prevented from working longer hours. Yes, it would, but I am deeply appalled at the thought of trading away individual freedom of action and additional value in the world for that goal.
You're pretty much right here, but it's important to be clear that the article does not suggest restricting working hours, it suggests changing the norm in an unspecified way. Granted, in Britain this has always been done with restrictive laws. The norm used to be for 9 year olds to work in factories for 15 hours a day. This was changed progressively to reduce to a norm of 40 hours a week for adult males only, and then has included adult females and slowly been rising since.
There are ways other than just saying that people can't work more than 35 hours a week. You can require overtime loading, you can change bargaining laws, you can change the employment conditions of people employed directly by the government. This doesn't impinge on anyones freedom more than current laws (i.e minimum wage, health and safetly, child labour, non-discrimination)
It's also important to remember that the having "some tactical discretion", and "being aligned with their job’s goals" in your job is rare. Most people dislike their jobs and most jobs are pretty pointless. There's an equality issue here that isn't the one you're thinking about: more access to meaningful work? If there's only so many hours of meaningful paid work to be done, wouldn't it be better to sacrifice a bit of efficiency to have as many people as possible doing a smaller amount of this work?
It is really important to not confuse individual with collective reasoning. It's pretty clear from the article that it doesn't apply to all cases. (And from what I've heard, you're a famously extreme outlier here) Yes, there will be negative consequences to any change, but you don't make society wide changes by looking at outliers.
> Research shows that shorter work weeks are just as effective.
John Carmack:
> I feel like longer work weeks are more effective.
Does anyone else see the problem with this?
Of course, pop-sci writing is often terrible. Of course, headlines can wildly misrepresent the research they're covering. Of course, there may be issues at stake (such as, in this case, personal freedom) beyond the simple phenomenon being described.
However, if you have an issue with the research's methodology, explain it. It might even be a little interesting to hear a new conflicting hypothesis from your own anecdotal experiences.
As it happens, regarding the quality of pop-sci journalism, on this particular issue, the research on the starkly diminishing returns of overtime and the negative impact it has on work (especially creative work) is all pretty consistent. For those who do not have the luxury of working in cushy chair-sitting industries like Mr. Carmack and myself, overtime is strongly correlated with an increase in industrial accidents, both fatal and otherwise.
I really wish that high-status people in the software industry would stop thinking that their success exempts them from cognitive bias and the need to make a rational argument, or that their experience writing software somehow transfers, with no particular education, to social science or management.
The problem with this opinion is neatly summed up by this statement:
> Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week, is going to achieve more.
which has been all but proven wrong by repeated scientific studies. In the general case, it is not true. In the specific cases of outliers where it appears to be true, my understanding of the research indicates that the "People with the psychological makeup that allows them to productively pursue a goal obsessively for well over 40 hours a week will tend to be extremely successful". But this attribute is highly unusual, and it may not be something you can cultivate; people who are taller also tend to do better in life, but that does not mean that the average person should torture themselves on the rack for 80 hours a week in the hopes of getting taller, either.
These two fall into the awful pop-sci writing category:
http://www.economist.com/blogs/freeexchange/2013/09/working-...
“And it seems that more productive—and, consequently, better-paid—workers put in less time at the office”
“So maybe we should be more self-critical about how much we work. Working less may make us more productive.”
These are clearly confusing correlation with causation, and I doubt very much that any of the actual researchers involved, as opposed to op-ed writers, would even imply that if only the workers in Greece would ease up a bit, they would get the productivity of Germany. Would you make that statement?
I don’t find much to argue with here. I don’t dispute the premise that working very long hours can have a health impact in some cases.
It was interesting to see the clear step function in the leading graph of average annual work hours by country with the US at ~1850 as the highest of the mostly-western countries, but Thailand, Hong Kong, and South Korea in a distinctly different class, topping out at ~2450 for South Korea. That made me smile, because one of the Samsung people we work with referred to us at the Oculus Dallas office as “honorary Koreans” because of how hard we work. I do note that the chart in the Economist link with more recent data has them still at the top, but down to ~2100 hours in 2012.
A couple interesting (unrelated) counterpoints from the studies:
Sokejima and Kagamimori [1998] observed a U-shaped relationship: as compared with 7 to 9 hours of work per day, higher risk (for cardiovascular problems) was associated with both shorter hours (less than 7 hours a day) and longer hours (more than 11 hours a day)
Nakanishi et al. [2001b], however, published the opposite results: white collar workers reporting 10 or more hours of work per day had a lower risk for developing hypertension when compared with workers reporting less than 8 hours of work per day
There are some small bits directly discussing performance:
3.2d Extended Work Shifts and Performance
Two laboratory studies reported deterioration in performance with extended shifts.
In contrast, four field studies reported no differences in their performance measures during extended shifts.
3.4b Very Long Shifts and Performance
A study in Ireland by Leonard et al. [1998] reported declines in two tests of alertness and concentration in medical residents who had worked 32-hour on-call shifts. They reported no significant declines in a test of psychomotor performance or a test of memory. A New Zealand survey of anesthesiologists linked long working hours to self-reported clinical errors [Gander et al. 2000].
I glanced at the other links, and they look potentially interesting, but non-responsive as far as giving actual data showing that working more than 40 hours a week makes you less productive.
Perhaps there is confusion about my position, so let me clarify:
Average productivity per hour will decline with extended work. The highest average hourly productivity could be with shifts as short as six hours for many people; I have no particular thoughts on this, as I have never had reason to care to optimize it. An assembly line job that is embarrassingly parallel with minimal communication overhead may well be better served to have shorter shifts and more workers.
Total net productivity per worker, discounting for any increases in errors and negative side effects, continues increasing well past 40 hours per week. There are a great many tasks where inefficiency grows significantly with additional workers involved; the Mythical Man Month problem is real. In cases like these, you are better off with a smaller team of harder working people, even if their productivity-per-hour is somewhat lower.
This is critical: it isn’t necessary to maintain performance on an extended shift to still contribute value. Productivity per hour can deteriorate, even precipitously, and still be non-negative. Only when you are so broken down that even when you come back the following day your productivity per hour is significantly impaired, do you open up the possibility of actually reducing your net output.
There are cases where the consequences of an increased error rate can be a dominant factor -- airline pilots and nuclear plant operators come to mind. I had to work under FAA mandated crew rest guidelines while operating the Armadillo Aerospace rockets, and I made no complaints.
I believe most research that people glance at and see “declines in productivity with longer hours” are talking about declines in productivity-per-hour, and people jump to the incorrect conclusion that you can get just as much done in less time.
You called my post “so wrong, and so potentially destructive”, which leads me to believe that you hold an ideological position that the world would be better if people didn’t work as long. I don’t actually have a particularly strong position there; my point is purely about the effective output of an individual. If we were fighting an existential threat, say an asteroid that would hit the earth in a year, would you really tell everyone involved in the project that they should go home after 35 hours a week, because they are harming the project if they work longer?
Okay, let's ignore all them pesky negatives of overworking, like killing a patient from time to time or messing with the wrong piece of data somewhere. Let's also ignore the issue of personal freedom vs. the hours mandated by your employer. Let's focus only on maximizing the total output you can generate. As I understand, this is your case.
The metric productivity-per-hour is stupid. It's useless trying to optimize it - just like you said. The natural cycle for humans is a day. The body requires rest and is tuned to have an optimal performance if the do/rest cycles are loosely synced with the day/night cycles of the sun. You need to optimize that cycle, in the long run, to maximize your total output.
"... when you come back the following day your productivity per hour is significantly impaired, do you open up the possibility of actually reducing your net output."
Yes, I do. The burnout today at work has an effect on your productivity tomorrow. In attempt to get a little extra done today, tomorrow you won't be that efficient at your peak, and you'll be more tired and unproductive at the and of the day, compared to the previous. This way your average productivity per day, from both days, can easily be lower than if you had worked 3 hours less the first night and the second day were just as efficient and productive as the first.
This effect extends in a long run. Fatigue accumulation and sleep debt are real phenomenons. Poorly managed day-to-day cycles can render people incapable of doing any meaningful work. The remedy is rest/vacation, which kills your averages even more.
You should know, even better than me, that working people don't only produce output. They are learning too. The work that you'll be required to do in a year or two is not the same as the one you do today. Mental fatigue impairs learning new stuff a lot more than it impairs doing stuff you already know.
"If you don’t want to work, and don’t really care about your work, less hours for the same pay sounds great! If you personally care about what you are doing, you don’t stop at 40 hours a week because you think it is optimal for the work, but rather because you are balancing it against something else that you find equally important."
This is spot on. I think motivation is a huge factor here. Motivated workers are more capable of remaining productive over longer periods. Switching projects/tasks when you run out of gas is usually reinvigorating. Also, some people seem to have more innate motivation like an extended "honeymoon" phase when new people start a job and they are more tenacious and eager to prove themselves.
A cool project is an external motivating factor, or an existential threat ranging from potentially losing your job to being wiped out by an asteroid. As terrible as it is, fear is a great motivator. I've worked on projects so mind numbingly boring and pointless that I've had to change tasks after a couple hours because I found myself staring at my editor hating what I was doing. I've also worked on projects where I could stay motivated and productive 16 hours a day for two weeks at a time trying to meet an important deadline.
Bottom line in my opinion is there's no such thing as a broad rule of thumb for how long someone can stay productive.
> would you really tell everyone involved in the project that they should go home after 35 hours a week, because they are harming the project if they work longer?
Everyone? Maybe not. Those whose could make irrecuperable errors and doom the project because of fatigue, certainly. For many professions, longer hours don't necessarily lend to more production, but can certainly become hazardous.
Sure, as long as everyone is paid 2X salary for every hour over 8. I've been abused at work, greatly. It changed my views. Not everyone has the same experiences and perspective.
I would disagree with you in the basic assumption that we let "everything just work out".
We do need laws that those who work over what has long been considered healthy- 8 hours, are compensated very well for their time. To the point that the incentive lies on the employer to hire more people.
There's nothing to stop you or anyone else from forgoing your pay. But working for free to most of us is unacceptable, we don't have as much money thus our transaction of time for money means more. And many have less power to call shots because they may be less valuable or talented.
Yet everyone receiving a paycheck deserves this basic protection from abuse.
"A living" is a rather broad concept. Two factors are grossly overlooked: the general standard of living is rising, and much of that rise results from making it nigh unto illegal to live below that standard. Even the "poor" expect easy indoor heat & AC, toilets flushed with city-supplied drinking water, one car per adult, a cell phone per teen & up, etc. I grew up on hand-split wood heat & no AC, well water, one car for the household, wired phones with 4-digit numbers, etc. - and we were firmly one-income "middle class". Nowadays wood stoves are regulated into near oblivion (near prohibitory particulate limits), heat & AC standards required for "certificate of occupancy" along with high plumbing standards, cars include a plethora of then-unattainable options and must meet very high gas mileage standards, cell phones are a standard welfare item, etc. - all due to well-meaning but subtly devastating requirements to live even in "functional poverty". Normalization of home mortgages, insurance-paid access to extremely high health care standards, and easy access to crushing loans for education, all seem perfectly justified now yet persuasively "force" people to work more and more "to make a living" which many of us saw as luxurious not all that long ago.
You can live well on a whole lot less - as most people did not all that long ago. Ditch the >1000 sq ft homes, instant shirt-sleeve indoor temperatures, waste-encouraging volumes of drinking water, high-MPG with-all-the-features cars, supercomputer-in-your-pocket phones, etc. Get a catastrophic health insurance plan. Pay your way thru college. Downgrade the phone. And elect leaders who seek to make simple living legal, and otherwise decrease burdensome tax rates.
Your "living" standard is your choice. Really. Contain your costs, and you can live on a whole lot less. As always I'll be derided for these observations, but it's what I grew up on.
Sure you can definitely live with lower standard (nice story of yours by the way, remember us how recent progress revolutionized our lives).
But I mean liberating as much as we can people from the necessity of working, and improving their quality of life in general, is a more realistic fight for humanity than destroying an asteroid.
Someone has to do the work; value is not durable nor zero-sum. Destroying an Earth-threatening asteroid is assuring the continued opportunity of all to produce as they can & will; confiscating the fruits of the productive to give to the idle punishes the former and rewards the latter. What you describe as "liberating" is mutual enslavement of producers & idle to each other. What you describe as "realistic" is unsustainable no less than the extinction event of an asteroid impact.
"Destroying an Earth-threatening asteroid..." But what asteroid ? That's all the point, it's ridiculous to care as much about a non-existing asteroid in the near feature than the plenty of dramatic problems that are causing damages for centuries.
"Someone has to do the work", "confiscating the fruits of the productive to give to the idle punishes the former and rewards the latter".
That's absolutely not what liberating work is about, and what you describe is a pretty narrow view of economics that we're taught since childhood. Investigating a bit economy shows it get way more complicated than that, just defining "productive value" is a very deep subject. I don't believe you and I are able to assess if an economic system is sustainable or not (reality shown even the best economists can't), whereas scientist are pretty accurate about the low probability of an asteroid destroying earth in 2016.
I think these types of studies are all going to be fatally flawed with a bunch of very-hard-to-untangle factors: since "40 hours" (or more) is the "expected norm" then if you're working less you've either fought incredibly hard to do so (which I personally have), you have way more freedom to choose working hours than most people or you're "forced" to work less (or more) for some reason.
e.g. my first thought about the "increased hypertension in workers reporting < 7 hours" (a paper I haven't read, mind) is that they're stressed about finances because they're working part-time (or the "hours" was averaged over the year or something, and they spent some time without a job).
Now, if you've chosen to work many more hours then it seems intuitively obvious that you'll be more productive. There's also the hard-to-study factor of what you're working on. For example, many free-software developers are doing their free-software-developing in their "non-work" hours -- so they might be "working" (in the sense of producing code) 80+ hours a week, but will likely only get "counted" as whatever their day job was. (If there are studies that account for "what you do with your other time" against productivity, I'd be very keen to read them).
In a similar vein -- and as John said in the original post -- if you're "stuck" on something (e.g. can't do any more "design the hard algorithm" thinking) and switch to something "boring" that still needs to be done (e.g. make the Makefile suck less) that's still "more productive". But, as others have pointed out, many developers don't have that freedom -- they have to keep pounding their face against whatever bug they got assigned. And if you're stuck, but have to keep working on it, I'd bet a lot that your productivity goes to shit.
So, all that said, I personally believe (note: not scientific! ;) that we'd be far better off to have shorter expected/forced "working weeks". And I don't mean that everyone should be forced to work less! This may (or may not!) have a "productivity" impact for employers but if you looked at individuals' "productivity" (including work and "non-work" parts) I think it would go way up -- precisely because this would give the vast majority of people way more choice about what they get to work on. This -- I completely unscientifically presume -- would also have a large positive effect on people's reported happiness.
That is, they'd be spending less time smashing their face on that bug at work and get more time to do whatever else they like to do -- free-software, painting, writing, building things, etc.
In any case, I know that for me personally being forced to work 40+ hours a week on the same thing is completely toxic to my creativity and productivity at programming and I've worked very hard to get paid less (to work less). I can also tell you that nearly every co-worker or friend I've told of my myriad different arrangements to achieve this have wanted to do the same (but feel they "can't"). The only exception seems to be when people realize the bit about "paid less" ;) and can't do (or don't want) that. Interestingly, I still have spent a bunch of my increased leisure time writing software -- but for myself, or free-software instead of "for work". Of course, I've also spent a bunch of it doing things for pure enjoyment.
Now, of course, that's all just anecdotal. But, for me, less "must work on X for $" time means a lot more happiness and a lot more "productivity" (if you look at everything I do with my time).
Not everyone is fully utilised at work, nor does every job's output scale linearly with incremental effort. So while the above is true in some cases (particularly for 'assembly line' type jobs, including programming, where there is a constant supply of discrete and valuable tasks) it is also the case that many people are productive for far less than the full time they spend at work and that a shorter working week would result in significant & near immediate productivity increases in a good number of cases. Examples would be bureaucratic work, a lot of generic 'project' roles, and situations where procrastination is common.
Perhaps it's not that people are particularly much more productive over short hours as that presenteeism and the need to be seen to be working long hours masks the true amount of productive time and many people will do less than they could if they think they can get away with it (particularly if they work long hours at a job they dislike), nonetheless it would be better for unproductive time at work to be spent elsewhere and reducing the length of the work week could achieve this.
This is so absolutely true. Your typical corporate office these days is full of wasted time and red tape that acts as a sponge for people's time left on this earth. Just the time a 30 minute commute takes away from one's day is a massive amount of time over one year. Hell if more people could work fewer hours from home, they would probably get the same or more work done and still have more time for themselves.
Most devs can't switch what they're working on: They're on a sprint plan that's estimated to 1/2 day (at least) precision, and checked-on every day at scrum.
Not saying your general point is wrong, but it's not what being an engineer is like for most people today. (BTW, fixing the way work is managed would probably do a lot for both people and firms.)
As you do have a reputation for getting quite a lot done, it would be cool if you'd share a little bit more on how you make long hours productive and manage to maintain focus (or maybe you've written about it elsewhere?).
"people that claim working nine hours in a day instead of eight gives no (or negative) additional benefit are either being disingenuous or just have terrible work habits"
It depends on so many factors (self interest in the job, capacity, health, age, repetitiveness, nature of the job, stress involved, etc...) that it can be true or false in different cases.
“Hey you, working three jobs to feed your family! Half of the time you are working is actually of negative value so you don’t deserve to be paid for it!”
Negative value might be abusive but those people are for sure less productive in their second job compared to if they wouldn't have to do the first one. But the net production is for sure higher for 2 jobs than 1.
"does that mean the rest of the day that you spend with your family, reading, exercising at the gym ... you would be spending your time on, are all done poorly?"
Assuming every activity is consuming the same resource is a very speculative statement. Being exhausted solving a math problem doesn't necessary means you're exhausted to run.
"When you hit a wall on one task, you could say “that’s it, I’m done for the day” and head home, or you could switch over to something else that has a different rhythm"
That's assuming every job is made of very diverses tasks. As a core of modern economy, division of labour actually lead to the opposite in many cases. And that's sort of true for many jobs in game industry where your day job can turn very repetitive and all the tasks, no matter how much, looks the very same.
"Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week is going to achieve more" You would need a study to back it up, I would be very curious of the result of these two people over a period of 40-50 years of career at 80 hours per week for one and 40 for the other.
If I care about what I do - I will do it anyways. I don't need to be an employee and go to work, just to be allowed to do what I already want and am doing. Does this make sense to you?
In the end I'm pursuing employment to get paid, you know, and there are only degrees of alignment between a person's current aspirations and the stuff you're going to be paid for. So, what people are trying to argue here is the balance between the time you are required to sacrifice in order to earn enough for a half-decent living and the free-will time in which your actions are motivated otherwise.
Like you once said - it's nice to be in a position where people can't exert leverage on you.
There certainly is a social and political push to this balance towards devoting yourself more to the company's agenda.
As with everything on the internet, this article and action that's making waves around the internet is an oversimplification on what is a really complex problem with a lot of factors and variables.
Your example with a factory worker is great example for that specific type of work, an assembly line, but much like the mentality of "lets work 6 hours instead of 8" craze that's going on it would only apply and benefit a specific type of employee - the average uninterested employee. This is guy/gal is a programmer, accountant, secretary, QA tester whatever that is good enough at what he does to get by and even promote very slowly, has mild interest in what he does for work but not enough to call it passion and does the work mostly for the money. That is actually the majority of intellectual employees, that need a job to live but can't find the dream role that's perfect for them to pump them full of life and excitement every day.
You see Sir, you are privileged enough to have a passion and set of skills that you've worked to develop over the years that actually enable you to go out and do whatever it is that you do best and have fun with it, while still bringing you quite enough money to live off. You wouldn't be able to say that about the guitarists, painters, artists, etc out there who are in very low demand and extremely high supply. Yes the elite of these people will do well, but only the elite. You are an elite in your field John, a well known and recognised symbol of the IT and Gaming industry. Most people are not and cannot afford to live off their dreams.
Thus while this new 6 hour system would not apply to you, because you are passionate about what you do and can invest non-stop effort in what you're doing (don't get me wrong, I'm the same just not as good or popular, Yet :D, but I am fortunate enough to live off of what I like doing best) for everyone else, this system would bring benefit for average employees that are willing to keep their Facebook time for home and work while at work. They will have a few more hours for themselves, their kids, their wives, and potentially even allow them the two extra hours a day they need to transform their hobbies into actual financial successes. \
In my opinion, the solution to this whole conundrum is to stop treating all businesses as they are assembly lines and analyse them on a case by case basis. For example in a micro games studio where you only have 10 valuable employees, a task based system might be a much better approach. "We need the sprites done by date x, the core mechanics by date y, and the sound by date z. I don't care if you work 9 to 5, 6 to 24 or 20 minutes a day, as long as they are complete in time we're golden. Then we can have meetings with the whole team to analyse the quality of your work and based on everyone's input we can determine a set of bonuses for different traits of your work (quality, speed, efficiency, reusability, etc).". This is of course an off the top of my head idea but it would work well in a very small studio where everyone has their meetings at the local Pub.
Unfortunately doing such an analysis and discovery on a large business would be extremely costly, so what's the next best thing? Follow the already well established trend, and copy whatever solution works for a different company (and copy it poorly without understanding why it works for that company). There is a reason why google employees in the US live on the Google campus, but nobody bothers to find out why thus what we get is silly generalisations like the 6 hour work day.
Blimey I went on quite a ramble didn't I? Oh well... apologies for the wall of text for all those that'll end up reading it.
I agree with this, with all due respect to John. The part I like most about your post is where people can choose what to do with that extra time, which may include actually being able to enjoy their family, or doing what I am doing which is learning new skills in my free time, or hey (go crazy) and do both!
The fact is, most of the jobs people don't like doing are going to be automated in the not-so-distant future, which brings up the question of what we humans will be doing when there are less work hours needed to move our society forward. Many people who are working today will NOT be willing or able to train up to meet the higher skills needed for our new world. So what will they be doing as their jobs go away? Don't get me wrong, I do not believe in keeping old jobs around just to keep people employed, but I still don't see this question being answered. I have a lot of friends who are in their 30's and 40's who have 20-25 years of employment ahead of them, but probably cannot rely on their jobs existing that long.
Another question is why are we working so hard on technology to automate and make our lives easier if all we are going to do with that supposedly easier life is work as much or more? Or rather, how long will people have to work jobs they hate, just to keep from living in a box under a bridge?
I'm running my own IT consulting business, which pays the bills, and also frees up more time for me to tend to my son, and to work on learning new skills to break into VR development. I can work basically part time and charge a high enough hourly rate to afford this lifestyle, but I am the exception, not the rule. I actually feel sorry for my family and friends when I see how unhappy they are working 40+ hours, barely seeing their kids before bedtime all week long, and just not being able to chase something that will really make them happy. When will humanity start coming before corporate productivity?
Unfortunately not soon enough. As you said, we are the exception. I'm currently trying to get a VR games studio of the ground, it's not easy but it's a hell of a lot of fun. You do your consultancy business which I'm sure you enjoy enormously and as you've said, 9 to 5 is just a bad dream for you.
But to move the whole of humanity into that direction, the whole of humanity have to be willing to put themselves in our position and actually self-educate and take control of their lives. As you can probably imagine that's not going to happen any time soon.
Mr Carmack over here is a great example of the humanity I would like to live in, but he is the polar opposite of the humanity we actually live in. Sadly most people do not have ambitious dreams of creating new things! They learn enough to get by and that's it. I am of course talking majorities here, I realise exceptions exist but the very sad truth is that people like being comfortable and stationary with very small aspirations in a world that's actually progressing without them. In London we have this funny problem with the Underground: Most of it can be automated, but because of the mass firing that would result, it's not being done due to humanitary reasons. The same humans that are being protected from this mass-atomisation are at the same time demanding absurdly high wages (£50k+) to do tasks that can be conducted by a £3000-£10000 robot and if these demands are not met, strikes!
Same thing with McDonald's in the US. Although somewhat more reasonable there as their wages were quite low, these people are replaceable with some very basic machines. In the UK there are McDonald's with automated ordering and paying stations. I just tap on a large touch screen what I want and stick a payment method in. That £3000 device just replaced a £15000 employee and is a lot more efficient at their job.
It pains me to say this but going forward this is going to be a self-regulating problem. There will at some point be massive unemployment which may cause quite a financial crisis and then it will regulate itself over time. In the new world that will come out of this crisis there won't be any room for non-intelectual people as most automated jobs will be gone. It's funny to think about it this way, but all those young adults getting university degrees, they might need them sooner than they think. The 20-25 y.o. that don't have higher education right now will probably suffer the most in 10 years time.
TL;DR: While what is happening seems very heartless and cruel, with all the automation, it actually seems like a necessary step to evolve as a sentient species.
(As of writing, account created 325 days ago, 1 comment and 2 karma)
It shouldn't really matter because it's 'appeal to authority', but thoughts on worklife/productivity by the Elon Musk's or John Carmack's of the world really do have more impact
I've read about you as an employer under the development of Quake. I can only relate this to you fascist way to force people work. It's a shame tho since you're such a talent and I hope you've changed.
Most people don't work jobs they care about. In an ideal world how people choose to spend their time would be entirely separate from notions of productivity or wages. But the fact is that we operate under a terrible economic system and people are overworked by largely meaningless jobs. In the context of society as it stands today, not only are people overworked, but most people could work less without their respective employers losing money. Because modern businesses operate solely off the principal of maximizing profit, I think it's poignant to point out that it's in their benefit to reduce the work week for their employees.
You can't apply this notion to people who spend their time in meaningful ways. You couldn't say that Picasso would be just as effective with a shorter work week. If people lived reasonable lives and did genuine work, the whole idea of comparing length of work weeks with effectiveness of work would be meaningless. You point out that when people are worn out with a certain activity, they could benefit by just moving on to another. That's true. Reasonably speaking, people shouldn't do anything for even a minute longer than they feel like. But the corporate world does not offer that kind of flexibility. The corporate world is rigid, and people are forced to operate in unnatural ways. Repetition and narrow focus are the bread and butter of this system, meaning you perform a single task over and over for the duration of your work day and that's it. This is the context with which you must examine the idea that "shorter work weeks are just as effective" because this is how most jobs work. I think the reason for pointing out that "shorter work weeks are just as effective" is really to use the ruthless, disconnected, corporate logic of the modern business world against itself.
Now, let me just dispel a myth you stated. You believe that "Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week, is going to achieve more." This again is modern corporate mentality. Work harder, put in more effort, and you will achieve more. The real world does not operate on these principals. Only menial tasks can be translated into the notion of more effort = higher yields. Lets take the example of Picasso again. Do you think the more time he spent painting in a given week the better his paintings were? Or take Newton. Do you think if he sat down and forced himself to ponder the physical laws of the universe for ten more hours each week he would have made more discoveries? This is a simplistic and completely insubstantial view on the world.
If you examine the lives of truly successful people (by which I mean people like Newton or Picasso or Tchaikovsky, not financially successful like Mark Cuban or Bill Gates) then you realize the only "rule" you can extrapolate from their lives is that people operate best when they do so on their own terms. Not when they work for longer hours or with more perceived "effort", but when they work exactly as they please.
But anyway, that's getting into another topic. I just wanted to point out that the idea that shorter work weeks are just as effective is completely valid when applied to the current and deeply flawed structure of modern work environments. It's not something which can be applied to ideal scenarios which offer flexibility, and frankly that's irrelevant because most people aren't fortunate enough to have that. If we do get to the point where people can work under truly ideal circumstances, the entire notion of productivity or effectiveness will be meaningless. These are concepts which only hinder good work.
Now, let me just dispel a myth you stated. You believe that "Given two equally talented people, the one that pursues a goal obsessively, for well over 40 hours a week, is going to achieve more."
This works for people like Carmack because he's always gotten to choose precisely what he wants to do in each of those 40+ hours.
Perhaps unusually, I actually wanted FB to impress itself more strongly on Oculus post acquisition because, frankly, Oculus was a bit of a mess. Instead, Oculus was given an enormous amount of freedom for many years.
Personally, nobody ever told me what to do, even though I was willing to "shut up and soldier" if necessary -- they bought that capability! Conversely, I couldn't tell anyone what to do from my position; the important shots were always called when I wasn't around. Some of that was on me for not being willing to relocate to HQ, but a lot of it was built into early Oculus DNA.
I could only lead by example and argument, and the arguments only took on weight after years of evidence accumulated. I could have taken a more traditional management position, but I would have hated it, so that's also on me. The political dynamics never quite aligned with an optimal set of leadership personalities and beliefs where I would have had the best leverage, but there was progress, and I am reasonably happy and effective as a part time consultant today, seven years later.
Talking about "entitled workers" almost certainly derails the conversation. Perhaps a less charged framing that still captures some of the matter is the mixing of people who Really Care about their work with the Just A Job crowd. The wealth of the mega corps does allow most goals to be accomplished, at great expense, with Just A Job workers, but people that have experienced being embedded with Really Care workers are going to be appalled at the relative effectiveness.
The communication culture does tend a bit passive-aggressive for my taste, but I can see why it evolves that way in large organizations. I've only been officially dinged by HR once for insensitive language in a post, but a few people have reached out privately with some gentle suggestions about better communication.
All in all, not a perfect fairy tale outcome, but I still consider taking the acquisition offer as the correct thing for the company in hindsight.