Jon Skeet: The 'Chuck Norris' of Programming (2016)
bbc.com
bbc.com
It’s currently sealed up.
In three years, Anders Hejlsberg is going to open the book to see if the language design team got it right.” still cracks me up.
[0] At the time I'm replying...
Watch me get downvoted into oblivion for merely offering a theory :)
It's not him, it's the circus that has developed from admirable community support and respect for a formidable person to something that must be a little frustrating for some of the other rockstars of the site who live in his shadow (and maybe for him as well!) - though I expect this multiplier effect also positively benefits them as well in comparison to the people further down the ladder.
Or am I imagining it?
In the grand scheme of things it's a non-issue, but it was quite frustrating at the time. And it is clearly an example driven by him as a famous personality rather than technical chops.
Carmack, Thompson, et al weren't simply great programmers; they were researchers and inventors.
Perhaps a longer timeframe will change that, but at the moment it seems ok to me.
It helps that he seems like a good egg.
Add to that that he is really good at writing detailed and to the point answers and you know where his reputation comes from. I only met him once briefly at CodeKen in London but judging from that he is a nice guy too.
* Jon Skeet can divide by zero.
* Jon Skeet's SO reputation is only as modest as it is because of integer overflow (SQL Server does not have a datatype large enough)
* Jon Skeet is the only top 100 SO user who is human. The others are bots that he coded to pass the time between questions.
* Jon Skeet coded his last project entirely in Microsoft Paint, just for the challenge.
* Jon Skeet can solve the travelling salesman in O(1).
* Jon Skeet does not use exceptions when programming. He has not been able to identify any of his code that is not exceptional.
* When you search for "guru" on Google it says "Did you mean Jon Skeet?"
* Jon Skeet can recite π. Backwards.
* Jon Skeet is the traveling salesman. Only he knows the shortest route.
* Jon Skeet can make the Kessel run in under twelve parsecs.
* If Jon Skeet posts a duplicate question on StackOverflow, the original question will be closed as a duplicate.
* When Jon gives a method an argument, the method loses
* When Jon pushes a value onto a stack, it stays pushed
* When invoking one of Jon's callbacks, the runtime adds "please"
* Google is Jon Skeet behind a proxy.
* The Jon Skeet badge is awarded for posting a better answer than Jon Skeet. Only Jon Skeet can earn this badge.
* God said: 'Let there be light,' only so he could see what Jon Skeet was up to.
* Jon Skeet doesn't use #include. He thinks of it as cheating.
* When Jon Skeet throws an exception, nothing can catch it.
* .NET uses Just-In-Time compilation because every instruction must first be approved by Jon Skeet.
* nVidia plans to triple the processing power of their newest videocards by bypassing their GPU pipelines entirely and offloading the vector operations to Jon Skeet over instant messenger. And those graphics benchmarks will improve further still during those intervals when Jon is actually awake.
* Any function written by Jon Skeet can only return 42. Co-workers have yet to report any errors caused by this.
* Jon Skeet programs in Binary, then compiles it into human-readable code.
* Jon Skeet has 2 keyboards so that he can type at full speed on one while the other is cooling down.
* Jon Skeet's desktop background is a picture of his desktop background. You wouldn't understand it even if you saw it.
* Jon Skeet's keyboard has only two buttons: 1 and 0
--Only one key surely, pressed (1) and released (0), and input is done at a fixed frequency (a la serial comms)
----last heard.. he got rid of that key too.. It's amazing what Jon Skeet can do with reflection and blinking.
* Jon Skeet's development workstation does not have a monitor. He never saw the point. In fact, the only reason he installed a video card is because the BIOS beep warning irritated his cat.
* Jon Skeet can appreciate music by opening an MP3 in a hex editor and reading it. He doesn't need a monitor for that either.
* When dragons write code they comment it with "Here be Jon Skeet".
* Alan Turing is Skeet-Complete.
* There are 10 types of people in this world. Those who think they understand binary, and Jon Skeet.
* I opened up a can of awesome the other day - it had Jon Skeet in it.
* The only reason we didn't all die of the Y2K bug was because Jon Skeet was bored on New Year's Eve and decided to fix it.
* Chuck Norris and Jon Skeet walked into a bar. The bar was instantly destroyed, as that level of awesome cannot be contained in one building.
-- ...Jon Skeet walked out unharmed.
* Jon Skeet can speak French in Russian.
* Jon Skeet can make IE obey his CSS rules.
With five cats, he will need six computers at least. I wonder if bengals are so warm lovers as the common african domestic cat.
What notable code has he written?
Noda Time - https://github.com/nodatime/nodatime/graphs/contributors The C# Protobuf port - https://github.com/jskeet/protobuf-csharp-port/graphs/contri...
Noda time is one of the top 100 downloaded packages on nuget.
That's quite a significant contribution to the .NET open source ecosystem - especially for someone whose day job is programming Java at Google, so these are pure side projects (.
He also wrote C# In Depth which is one of the standards by which programming language books should be judged (up with books like K&R, JavaScript: The Good Parts, and Essential Java).
NodaTime is a port. He didn't come up with those ideas. He translated Java code to C#. protobuf isn't much different, either.
https://www.mercurynews.com/2013/01/24/how-googles-jeff-dean...
I don't think there is such a thing. Certainly there are well-known coders who are terrific. But there are also great coders quietly working away in mundane jobs, doing great work, without any fanfare. And we have a huge variety of work in the industry. A great programmer in one area won't be a great in another. And that isn't even getting into the philosophical discussion of academic coders vs. pragmatic.
At the end of the day, any list of the best coders is going to be built upon opinionated criteria. Maybe instead of discussing an artificial list, just go out and say "Thanks", to any great coders who you work with.