Earlier quoted context omitted.
If I was on that team I'd welcome the opportunity to tell John Carmac why he was wrong or if I agreed start looking for another project to work on. When I was on nuclear submarines we'd call what you are advocating "keep us in the dark and feed us bullshit."
This assumes that you would be sincerely listened to, which you wouldn't in a case like this. Higher ups in large organizations don't have the bandwidth to listen to everybody. Your sub's officers also need to constantly be aware of what to communicate to whom and in which language. Your superiors certainly kept you in the dark about a ton of concerns that were on their plate because simply mentioning them to subordi…
John Carmack's arguments against building a custom XR OS at Meta
251–260 of 675 posts
Re: John Carmack's arguments against building a custom XR OS at Meta
#252Earlier quoted context omitted.
One could argue that if it’s not in your swim lane, you just let it fail. And if you aren’t that person’s manager, you tell them the code or design that you are reviewing and thus the gatekeeper is not adequate. Politely. You said your part and no need to get yourself in trouble. Document and move on. If the company won’t listen then you move on. No need to turn it into a HR issue.
Carmack's swim lane was exceptionally wide. My understanding was that this sort of criticism was actually his main job duty.
Why the fuck is he even hired there if you are not going to listen to him.
Dude has forgotten more things about game development than you will ever know...
Re: John Carmack's arguments against building a custom XR OS at Meta
#253Re: John Carmack's arguments against building a custom XR OS at Meta
#254Re: John Carmack's arguments against building a custom XR OS at Meta
#255Earlier quoted context omitted.
How would that be better than just grabbing a bsd and starting with that, PlayStation and Apple did it and actually ended up with functional products
Hell, if you're Meta you could just by QNX from RIM.
(Actually I just realised you meant "buy")
Re: John Carmack's arguments against building a custom XR OS at Meta
#256Earlier quoted context omitted.
I remember watching Carmack at a convention 15 years ago. He took a short sabbatical and came back with ID Tech 3 on an iPhone, and it still looks amazing well over a decade later. https://www.youtube.com/watch?v=52hMWMWKAMk&t=1s This is a guy who figures that what he wants to do most with his 3 free weekends is to port his latest, greatest engine to a Cortex-A8. Leading corporate strategy? Maybe not. But Carmack on…
Impressive. JC is always one of the engineers I look up to and read up to when depressed. John Carmack, David Cutler, Tom West, Cameron Zwarich, etc. There are about maybe 50 of them.
Re: John Carmack's arguments against building a custom XR OS at Meta
#257Earlier quoted context omitted.
Carmack is a legend and I admire his work, but he seems to believe his own legend these days (like a few others big-ego gamedevs) and that can lead to arbitrary preferences being sold as gospel.
I'm sure that's true but I've worked with a lot of engineers that are of this caliber and as long as you can form a coherent logical explanation they will bend they're way more open than you expect. But you got to put in the work to make that argument. They won't take it on faith
Re: John Carmack's arguments against building a custom XR OS at Meta
#258Earlier quoted context omitted.
I'll offer a different interpretation: If a professional can't give critical feedback in a professional setting without being rude or belittling others, then they need to improve their communication skills.
Having worked in the valley, I've seen what critical feedback meant in many companies there, and it removes all usefulness of the info because there is a ceiling of what is socially acceptable to say; therefore, you can't know how bad or urgent things are. Everything is ASAP. They are super excited about everything. And nothing you do is wrong, it just could be improved or they like it but don't love it. You don't kn…
Re: John Carmack's arguments against building a custom XR OS at Meta
#259Earlier quoted context omitted.
John can be quite blunt and harsh in person, from everyone I know who’s interacted with him. If he doesn’t believe in something, he can sometimes be over critical and it’s hard to push back in that kind of power imbalance.
Which makes sense when you are one of 3 developers at ID software. There's absolutely no room for waste. This is Meta. Let the kids build their operating system ffs. Is he now more concerned with protecting shareholder value? Who cares.
XROS was an org that hired for specific specialist positions (as opposed to the usual "get hired into FB, go through the bootcamp, and find your place within the company"). At one point we got two separate requests from the recruiting execs: - Your tech screen pass rate is way too low compared to other teams at FB. Please consider making your tech screen easier to expand the pool of candidates. - Your interview-to-offer rate is way too low compared to other teams at FB. Please consider making your tech screen more difficult to reduce time that engineers spend on interviewing and writing feedback.
Anyway, IMO it was a very strong team in a very wrong environment. Most of the folks on the team hated the Facebook culture, despised the PSC process (despite having no problems with delivering impact in a greenfield project), had very little respect for non-technical managers coming from FB proper (the XROS team saw themselves as part of Oculus), and the majority I believe fled to other companies as soon as the project was scrapped. The pay was good however, and the work was very interesting. My overall impression was that most people on the team saw XROS as a journey, not a destination, and it was one of the reasons why it was destined to never ship.
Re: John Carmack's arguments against building a custom XR OS at Meta
#260I was at Google when the Flutter team started building Fuchsia. They had amazing talent. Seriously, some of the most brilliant engineers I've worked with. They had a huge team. Hundreds of people. It was so ambitious. But it seemed like such a terrible idea from the start. Nobody was ever able to articulate who would ever use it. Technically, it was brilliant. But there was no business plan. If they wanted to build a…
Wasn’t Fuchsia supposed to be a platform where different OS could run in a virtual environment and software packages would be complete containers? Was not this a new way of tackling the ancient OS problem? These were my imaginations. I thought maybe an OS that could run on the web. Or an OS that could be virtualized to run on several machines. Or an OS that could be run along several other instances on the same machi…