Hey! I created Jeff Dean Facts! Not the jokes themselves, but the site that collected them.
It was in 2008 I think (give or take a year, can't remember). I worked at Google at the time. Chunk Norris Facts was a popular Internet meme (which I think later faded when he came out as MAGA, but I digress...). A colleague (who wishes to remain anonymous) thought the idea of Jeff Dean Facts would be funny, and April 1st was coming up.
At the time, there was a team working on an experimental web app hosting platform code named Prometheus -- it was later released as App Engine. Using an early, internal build I put together a web site where people could submit "facts" about Jeff Dean, rate each other's facts on a five-star scale, and see the top-rated facts. Everything was anonymous. I had a few coworkers who are funnier than me populate some initial facts.
I found a few bugs in Prometheus in the process, which the team rapidly fixed to meet my "launch date" of April 1st. :)
On the day, which I think was a Sunday, early in the morning, I sent an email to the company-wide "misc" mailing list (or maybe it was eng-misc?) from a fake email address (a google group alias with private membership), and got the mailing list moderator to approve it.
It only took Jeff an hour or two to hack his way through the back-end servers (using various internal-facing status pages, Borg logs, etc.) to figure out my identity.
But everyone enjoyed it!
My only regret is that I targeted the site specifically at Jeff and not Sanjay Ghemawat. Back then, Jeff & Sanjay did everything together, and were responsible for inventing a huge number of core technologies at Google (I have no idea to what extent they still work together today). The site was a joke, but I think it had the side effect of elevating Jeff above Sanjay, which is not what I intended. Really the only reason I targeted Jeff is because he's a bit easier to make fun of personality-wise, and because "Jeff Dean Facts" sort of rolls off the tongue easier that "Sanjay Ghemawat Facts" -- but in retrospect this feels a little racist. :(
My personal favorite joke is: Jeff Dean puts his pants on one leg at a time, but if he had more than two legs, you'd see his approach is actually O(log n).
Hi Kenton! No worries at all. I tend to be quieter than Jeff anyway (less public speaking etc.) and I am happy to not have a dedicated website. :-). -Sanjay
Hi Kenton! I was the recent grad you handed this web app off to after you built it, so I expanded Jeff Dean Facts so that anyone could create and rate facts about anyone at Google :). There were a ton of team in-jokes added before I stopped working on it - O(5k) IIRC! :)
This web app was also how I learned the pain of maintaining a live web service with a lot of ever-changing dependencies. How I sighed when the AppEngine version changed and I had to fix things again...
I handed it off again before I left Google but I have no memory of who that was to unfortunately :(.
I’m no expert, but I certainly wouldn’t call that racism. Bias, absolutely. And it’s important that we acknowledge our biases.
But in a more literal sense, the chance of your joke landing was likely higher due to the things that you stated and due to your audience and their biases.
I don’t see your joke as being in any way harmful towards Sanjay aside from potential knock on effects of Jeff Dean being more popular. But if you try to calculate every second and third order consequence of everything that you do, let alone any moments of humor you might have.. Well, you might as well lock yourself in a cell now.
Re Jeff and Sanjay - they recently were on Dwarkesh together I believe - so it looks like the partnership is still going strong. Regarding Dean over Ghemawat facts, the vibe from the convo is that Sanjay is the (very slightly) junior partner of the two, or at least he lets Jeff do more of the talking. Very, very nice vibes hearing them talk, and their war stories are clearly nuts.
My further comment will be buried, but its a rip on Chuck Norris facts, and was pretty ... whatever ... "geek culture". That was only proved by Chuck Norris' endorsement of Mike Huckabee back in 2007:
https://www.youtube.com/watch?v=--EGyU57efY
You still have to create a Youtube channel for Jeff Dean/Sanjay Ghemawat (slayers of code!) like "Entertaining AI" did for "Chuck Norris" - https://www.youtube.com/@Entertaining_AI
> When Jeff Dean goes on vacation, production services across Google mysteriously stop working within a few days. This is actually true. ... It's not clear whether this fact is really true, or whether this line is simply part of the joke, so I've omitted the usual (TRUE) identifier here. Interpret this as you see fit :)
I think this one's true-ish. Back in the day when Google didn't have good cron services for the corp and production domains [1], Jeff Dean's workstation ran a job that made something called (iirc) the "protocol buffer debug database". Basically, a big file (probably an sstable) with compiled .proto introspection data for a huge number of checked-in protobufs. You could use it to produce human-readable debug output from what was otherwise a fairly indecipherable blob. I don't think it was ever intended for production use, but some things that shouldn't have ended up using it. I think after Jeff had been on vacation for a while, his `prodaccess` credentials expired, the job stopped working, maybe the output became unavailable, and some things broke.
Here's a related story I know is true: when I was running Google Reader, I got paged frequently for Bigtable replication delay, and I eventually traced it to trouble accessing files that shared GFS chunkservers with this database. I mentioned it on some mailing list, and almost immediately afterward Jeff Dean CCed me on a code review changing the file's replication from r=3 to r=12. The problem went away.
Ha, I also recall this fact about the protobuf DB after all these years
Another Jeff Dean fact should be "Russ Cox was Jeff Dean's intern"
This was either 2006 or 2007, whenever Russ started. I remember when Jeff and Sanjay wrote "gsearch", a distributed grep over google3 that ran on 40-80 machines [1].
There was a series of talks called "Nooglers and the PDB" I think, and I remember Jeff explained gsearch to maybe 20-40 of us in a small conference room in building 43.
It was a tiny and elegant piece of code -- something like ~2000 total lines of C++, with "indexer" (I think it just catted all the files, which were later mapped into memory), replicated server, client, and Borg config.
The auth for the indexer lived in Jeff's home dir, perhaps similar to the protobuf DB.
That was some of the first "real Google C++ distributed system" code I read, and it was eye opening.
---
After that talk, I submitted a small CL to that directory (which I think Sanjay balked at slightly, but Jeff accepted). And then I put a Perforce watch on it to see what other changes were being submitted.
I think the code was dormant for awhile, but later I saw someone named Russ Cox started submitting a ton of changes to it. That became the public Google Code Search product [2]. My memory is that Russ wrote something like 30K lines of google3 C++ in a single summer, and then went on to write RE2 (which I later used in Bigtable, etc.)
I remember someone telling him on a mailing list something like "you can't just write your own regex engine; there are too many corner cases in PCRE"
And many people know that Russ Cox went on to be one of the main contributors to the Go language. After the Code Search internship, he worked on Go, which was open sourced in 2009.
---
[1] Actually I wonder if today if this could perform well enough a single machine with 64 or 128 cores. Back then I think the prod machines were something like 2, 4, or 8 cores.
[2] This was the trigram regex search over open source code on the web. Later, there was also the structured search with compiler front ends, led by Steve Yegge.
I submitted this "fact" and it is indeed a true story, exactly as you said.
The "global protobuf db" had comments all over it saying it's not intended for production-critical tasks, and it had a lot of caveats and gotchas even aside from being built by Jeff's desktop, but it was so convenient that people naturally ended up using it anyway.
In 2010, due to the China hacking thing, Google locked down its network a lot.
At least one production service went down because it relied on a job running on Jeff Dean's personal computer that no longer had access. Unfortunately I forget what job it was.
During his own Google interview, Jeff Dean was asked the implications if P=NP were true. He said "P = 0 or N = 1." Then, before the interviewer had even finished laughing, Jeff examined Google's public certificate and wrote the private key on the whiteboard.
Jeff Dean wrote an O(n^2) algorithm once. It was for the Traveling Salesman Problem
I read it more as a parody of The Most Interesting Man in the World as opposed to Chuck Norris.
"Chuck Norris facts" was a text-only meme format from the mid '00s. Stuff like "Chuck Norris is the only man to ever defeat a brick wall in a game of tennis" or "When Chuck Norris does push-ups, he doesn't push himself up, he pushes the Earth down." The Jeff Dean Facts use the same format. It doesn't have anything to do with Chuck Norris himself.
> Jeff once simultaneously reduced all binary sizes by 3% and raised the severity of a previously known low-priority Python bug to critical-priority in a single change that contained no Python code.
This sounds really plausible. A change to the C toolchain/library (for example, specialized/inlined memcpy) may affect binary sizes significantly, and may change the behavior of something the C standard leaves undefined (for example, memcpy with overlapping arguments).
I have such a Python bug right now because of something that fork()s in a way that can't posix_spawn(). One of those is a lot easier to make performant than the other.
Yes, Jeff told me this one personally. Knuth came in right before the talk started and the room was full. I think somebody later gave up a seat for him.
It probably is. I think the same thing happened when Randall Munroe (of xkcd fame) gave a talk at Google. I was there, it was crowded, and Don Knuth showed up. 90% sure he sat on the floor.
I am only semi technical so most of these go right over my head, but after watching a ton of Jeff Dean interviews, etc it is really fun to see how a 10-100x engineer can operate over such a long career (while seemingly a normal and kind person to boot)
My 3
When Graham Bell invented the telephone, he saw a missed call from Jeff Dean.
Jeff Dean's PIN is the last 4 digits of pi.
As a young boy, Jeff Dean reprogrammed his Etch A Sketch to play Tetris.
Even with the ellipsized link I knew you were talking about one of a few things because the link shows up as `:visited` for me... had to be either BigTable, MapReduce, or Spanner. All good reads.
One of my more junior teammates got their CL assigned to Sanjay for review, she had no idea who he was and I just told her to look at all her new badges tomorrow.
Ok I'll try. Jeff Dean read the instructions on his family sized bottle of shampoo in the shower. They said lather, rince, repeat. He almost died of hypothermia, but wrote a goto in conditioner just in time.
Funny, but also a reminder of how rare it is to find people who combine deep technical ability with the calm, high-leverage decision-making that scales teams. Memes aside, those are the folks who quietly shape entire fields.
It is a formal process via which it is confirmed that you know enough of X to submit code to the codebase, where X can be c++, java, python, etc. If you don't have X readability, then, in addition to your main code reviewer, you need to have a readability reviewer look at your code, who will be focusing only on X, not the logic of your code.
Maybe I just run in different circles but I was always under the impression that the so called Chuck Norris of programming was Jon Skeet, another rather "famous" google employee
Yeah I thought exactly the same, but I guess Jon Skeet is from a different era altogether, we're moving into a world where many programmers perhaps have never even entered StackOverflow. I feel old.
I also remember that but I think it was attributed to someone else. The site hosted several (internally famous person) facts, but none of them were as famous as Jeff Dean.
My outsider understanding: Google AI (a Google team which Jeff Dean ran) was merged with DeepMind to create Google DeepMind (a subsidiary of Alphabet, like Google).
Demis Hassabis is the CEO of Google DeepMind and Jeff Dean is now the Chief Scientist of Google.
I joined Google in mid-1999, and I'm currently Google's Chief Scientist, focusing on AI advances for Google DeepMind and Google Research. My areas of focus include machine learning and AI and applications of AI to problems that help billions of people in societally beneficial ways. I have a broad variety of interests, including machine learning, large-scale distributed systems, computer systems performance, compression techniques, information retrieval, application of machine learning to search and other related problems, microprocessor architecture, compiler optimizations, and the development of new products that organize information in new and interesting ways.
Yes, but the downside is even highly accomplished engineers feel unworthy.
For example, when I started in 2008, they said everybody should make a "Google Resume" (ongoing list of all the stuff you did at Google) and linked to Jeff's as an example.
He rewrote the entire indexing pipeline at a critical time enabling Google's rapid growth... created mapreduce... helped create bigtable & gfs... wrote the search engine that ran for over a decade... numerous improvements to search and ads quality (back in the days when search and ads quality meant something)...
and that was just the first few years.
not necessarily. It shows the system got one excellent engineer to an appropriate position. But it doesn't show that the system isn't promoting bozos too, and keeping other excellent engineers down.
This is overstating it by a lot. Jeff was the AI lead at the time, and there was a big conflict between management and the ethics team
And I actually think Google needs to pay more attention to AI ethics ... but it's a publically traded company and the incentives are all wrong -- i.e. it's going to do whatever it needs to do keep up with the competition, similar to what happened with Google+ (perceived competition from Facebook)
Jeff Dean is a lot smarter than me, more accomplished, and more talented. But let’s be honest. He was a big part of TensorFlow and TensorFlow sucks. And I imagine it reflects a lot about Jeff Dean internally. Smart, clever, but maybe over complicated or over engineered. And that itself reflects hugely at what Google tends to like, and why he’s so successful (at Google).
And if we’re being brutally honest, I wonder how he would have faired at somewhere like Bell Labs ;)
kentonv|1 month ago
It was in 2008 I think (give or take a year, can't remember). I worked at Google at the time. Chunk Norris Facts was a popular Internet meme (which I think later faded when he came out as MAGA, but I digress...). A colleague (who wishes to remain anonymous) thought the idea of Jeff Dean Facts would be funny, and April 1st was coming up.
At the time, there was a team working on an experimental web app hosting platform code named Prometheus -- it was later released as App Engine. Using an early, internal build I put together a web site where people could submit "facts" about Jeff Dean, rate each other's facts on a five-star scale, and see the top-rated facts. Everything was anonymous. I had a few coworkers who are funnier than me populate some initial facts.
I found a few bugs in Prometheus in the process, which the team rapidly fixed to meet my "launch date" of April 1st. :)
On the day, which I think was a Sunday, early in the morning, I sent an email to the company-wide "misc" mailing list (or maybe it was eng-misc?) from a fake email address (a google group alias with private membership), and got the mailing list moderator to approve it.
It only took Jeff an hour or two to hack his way through the back-end servers (using various internal-facing status pages, Borg logs, etc.) to figure out my identity.
But everyone enjoyed it!
My only regret is that I targeted the site specifically at Jeff and not Sanjay Ghemawat. Back then, Jeff & Sanjay did everything together, and were responsible for inventing a huge number of core technologies at Google (I have no idea to what extent they still work together today). The site was a joke, but I think it had the side effect of elevating Jeff above Sanjay, which is not what I intended. Really the only reason I targeted Jeff is because he's a bit easier to make fun of personality-wise, and because "Jeff Dean Facts" sort of rolls off the tongue easier that "Sanjay Ghemawat Facts" -- but in retrospect this feels a little racist. :(
My personal favorite joke is: Jeff Dean puts his pants on one leg at a time, but if he had more than two legs, you'd see his approach is actually O(log n).
sghemawat|1 month ago
ariwilson|1 month ago
This web app was also how I learned the pain of maintaining a live web service with a lot of ever-changing dependencies. How I sighed when the AppEngine version changed and I had to fix things again...
I handed it off again before I left Google but I have no memory of who that was to unfortunately :(.
peddling-brink|1 month ago
But in a more literal sense, the chance of your joke landing was likely higher due to the things that you stated and due to your audience and their biases.
I don’t see your joke as being in any way harmful towards Sanjay aside from potential knock on effects of Jeff Dean being more popular. But if you try to calculate every second and third order consequence of everything that you do, let alone any moments of humor you might have.. Well, you might as well lock yourself in a cell now.
morley|1 month ago
https://www.newyorker.com/magazine/2018/12/10/the-friendship...
EDIT: And HN at the time:
https://news.ycombinator.com/item?id=18588697
vessenes|1 month ago
oncallthrow|1 month ago
It’s not racist. It’s just to do with name length.
iambateman|1 month ago
:)
xnx|1 month ago
They just got their own (unofficial) Lego set: https://x.com/JeffDean/status/2006581022666928415
omoikane|1 month ago
Later version of the site was generalized so that people can submit facts for any user. I think Jeff Dean still has all the funniest fact though.
swyx|1 month ago
my nonexpert impression is jeff keeps much more of a public profile. hence the natural celebrity goes to him. was this not true way back in the day?
scrame|1 month ago
liquidgecka|1 month ago
rramadass|1 month ago
You still have to create a Youtube channel for Jeff Dean/Sanjay Ghemawat (slayers of code!) like "Entertaining AI" did for "Chuck Norris" - https://www.youtube.com/@Entertaining_AI
westurner|1 month ago
You could add a meme generator that's like the Django docs tutorial with the internet web-poll
ctxc|1 month ago
Because it’s easy to pick on myself. :)"
Damn!
bummy_commenter|1 month ago
scottlamb|1 month ago
I think this one's true-ish. Back in the day when Google didn't have good cron services for the corp and production domains [1], Jeff Dean's workstation ran a job that made something called (iirc) the "protocol buffer debug database". Basically, a big file (probably an sstable) with compiled .proto introspection data for a huge number of checked-in protobufs. You could use it to produce human-readable debug output from what was otherwise a fairly indecipherable blob. I don't think it was ever intended for production use, but some things that shouldn't have ended up using it. I think after Jeff had been on vacation for a while, his `prodaccess` credentials expired, the job stopped working, maybe the output became unavailable, and some things broke.
Here's a related story I know is true: when I was running Google Reader, I got paged frequently for Bigtable replication delay, and I eventually traced it to trouble accessing files that shared GFS chunkservers with this database. I mentioned it on some mailing list, and almost immediately afterward Jeff Dean CCed me on a code review changing the file's replication from r=3 to r=12. The problem went away.
[1] this lasted longer than you would expect
chubot|1 month ago
Another Jeff Dean fact should be "Russ Cox was Jeff Dean's intern"
This was either 2006 or 2007, whenever Russ started. I remember when Jeff and Sanjay wrote "gsearch", a distributed grep over google3 that ran on 40-80 machines [1].
There was a series of talks called "Nooglers and the PDB" I think, and I remember Jeff explained gsearch to maybe 20-40 of us in a small conference room in building 43.
It was a tiny and elegant piece of code -- something like ~2000 total lines of C++, with "indexer" (I think it just catted all the files, which were later mapped into memory), replicated server, client, and Borg config.
The auth for the indexer lived in Jeff's home dir, perhaps similar to the protobuf DB.
That was some of the first "real Google C++ distributed system" code I read, and it was eye opening.
---
After that talk, I submitted a small CL to that directory (which I think Sanjay balked at slightly, but Jeff accepted). And then I put a Perforce watch on it to see what other changes were being submitted.
I think the code was dormant for awhile, but later I saw someone named Russ Cox started submitting a ton of changes to it. That became the public Google Code Search product [2]. My memory is that Russ wrote something like 30K lines of google3 C++ in a single summer, and then went on to write RE2 (which I later used in Bigtable, etc.)
Much of that work is described here: https://swtch.com/~rsc/regexp/
I remember someone telling him on a mailing list something like "you can't just write your own regex engine; there are too many corner cases in PCRE"
And many people know that Russ Cox went on to be one of the main contributors to the Go language. After the Code Search internship, he worked on Go, which was open sourced in 2009.
---
[1] Actually I wonder if today if this could perform well enough a single machine with 64 or 128 cores. Back then I think the prod machines were something like 2, 4, or 8 cores.
[2] This was the trigram regex search over open source code on the web. Later, there was also the structured search with compiler front ends, led by Steve Yegge.
kentonv|1 month ago
The "global protobuf db" had comments all over it saying it's not intended for production-critical tasks, and it had a lot of caveats and gotchas even aside from being built by Jeff's desktop, but it was so convenient that people naturally ended up using it anyway.
btilly|1 month ago
At least one production service went down because it relied on a job running on Jeff Dean's personal computer that no longer had access. Unfortunately I forget what job it was.
jeffbee|1 month ago
andy99|1 month ago
jakevoytko|1 month ago
mcmcmc|1 month ago
pss314|1 month ago
[0]: https://www.newyorker.com/magazine/2018/12/10/the-friendship...
dust-jacket|1 month ago
chihuahua|1 month ago
hvenev|1 month ago
This sounds really plausible. A change to the C toolchain/library (for example, specialized/inlined memcpy) may affect binary sizes significantly, and may change the behavior of something the C standard leaves undefined (for example, memcpy with overlapping arguments).
astrange|1 month ago
thevillagechief|1 month ago
That's actually funny and cool if true. I think what's even more impressive is that this stuff was all pre-AI boom.
dekhn|1 month ago
scottlamb|1 month ago
ChrisMarshallNY|1 month ago
> Jeff Dean compiles and runs his code before submitting, but only to check for compiler and CPU bugs.
Sadly, I have encountered this, in many "Non-Jeff-Dean" developers.
Xenoamorphous|1 month ago
devin|1 month ago
- Bruce Schneier facts - https://www.schneierfacts.com/
- Doug McIlroy facts - https://github.com/mischief/9problems/blob/master/lib/dougfa...
never_inline|1 month ago
postscapes1|1 month ago
m1ck|1 month ago
tanseydavid|1 month ago
dhruv3006|1 month ago
To me this will remain his best work.
hxtk|1 month ago
linsomniac|1 month ago
shagie|1 month ago
I also recommend Monktoberfest 2016: Bryan Cantrill - Oral Tradition in Software Engineering : https://youtu.be/4PaWFYm0kEw?si=nqfxSae52-89x5Ye&t=653
bhickey|1 month ago
seanmcdirmid|1 month ago
stogot|1 month ago
callumprentice|1 month ago
delichon|1 month ago
justinchen7|1 month ago
ripe|1 month ago
bubblicious|1 month ago
utopcell|1 month ago
leopoldj|1 month ago
Jeff Dean doesn't use a compiler; he just glares at his source code until it executes.
Jeff Dean once optimized a sleep(10) call to return in 5 seconds.
Jeff Dean’s keyboard doesn’t have a Backspace key; he simply doesn't make mistakes.
/end. There's no need to get up. I will see myself out.
VikingCoder|1 month ago
Bost|1 month ago
unknown|1 month ago
[deleted]
nickstaggs|1 month ago
freeCandy|1 month ago
billbrown|1 month ago
dysoco|1 month ago
shadowgovt|1 month ago
"Jeff Dean has access to the priority above P1. He's only used it once. It's why February only has 28 days."
yongjik|1 month ago
furyofantares|1 month ago
I can think of a lot of 1/n algorithms! Head, Tail...
nojvek|1 month ago
theodric|1 month ago
wernsey|1 month ago
[1]: https://meta.stackexchange.com/questions/9134/jon-skeet-fact...
anymouse123456|1 month ago
https://www.youtube.com/watch?v=3t6L-FlfeaI
bananapub|1 month ago
unknown|1 month ago
[deleted]
squigz|1 month ago
dekhn|1 month ago
sidcool|1 month ago
desi_ninja|1 month ago
Myrmornis|1 month ago
Keyframe|1 month ago
on a serious note, this recent-ish interview on AI is illuminating https://www.youtube.com/watch?v=dq8MhTFCs80
keybored|1 month ago
lysace|1 month ago
Demis Hassabis is the CEO of Google DeepMind and Jeff Dean is now the Chief Scientist of Google.
https://en.wikipedia.org/wiki/Google_DeepMind
https://research.google/people/jeff/
I joined Google in mid-1999, and I'm currently Google's Chief Scientist, focusing on AI advances for Google DeepMind and Google Research. My areas of focus include machine learning and AI and applications of AI to problems that help billions of people in societally beneficial ways. I have a broad variety of interests, including machine learning, large-scale distributed systems, computer systems performance, compression techniques, information retrieval, application of machine learning to search and other related problems, microprocessor architecture, compiler optimizations, and the development of new products that organize information in new and interesting ways.
saagarjha|1 month ago
mike_hearn|1 month ago
utopcell|1 month ago
bananapub|1 month ago
scrame|1 month ago
I mean, chuck norris even did it to endorse mike huckabee. https://www.youtube.com/watch?v=--EGyU57efY
eatbitseveryday|1 month ago
philipwhiuk|1 month ago
rednafi|1 month ago
esafak|1 month ago
dekhn|1 month ago
He rewrote the entire indexing pipeline at a critical time enabling Google's rapid growth... created mapreduce... helped create bigtable & gfs... wrote the search engine that ran for over a decade... numerous improvements to search and ads quality (back in the days when search and ads quality meant something)... and that was just the first few years.
advisedwang|1 month ago
yep
> and a meritocracy exists
not necessarily. It shows the system got one excellent engineer to an appropriate position. But it doesn't show that the system isn't promoting bozos too, and keeping other excellent engineers down.
macybosts|1 month ago
[deleted]
stefantalpalaru|1 month ago
[deleted]
unit149|1 month ago
[deleted]
m00dy|1 month ago
dekhn|1 month ago
bigstrat2003|1 month ago
benzguo|1 month ago
lookingdesk|1 month ago
chubot|1 month ago
And I actually think Google needs to pay more attention to AI ethics ... but it's a publically traded company and the incentives are all wrong -- i.e. it's going to do whatever it needs to do keep up with the competition, similar to what happened with Google+ (perceived competition from Facebook)
tziki|1 month ago
whynotminot|1 month ago
lemoncucumber|1 month ago
morcus|1 month ago
So Jeff wanted the team to modify an existing publication to fit the PR spin on AI, the ethics team refused, and Jeff dissolved the team?
tehjoker|1 month ago
https://www.technologyreview.com/2020/12/04/1013294/google-a...
shemnon42|1 month ago
jackblemming|1 month ago
And if we’re being brutally honest, I wonder how he would have faired at somewhere like Bell Labs ;)
utopcell|1 month ago