George Hotz | Programming | Livecoding SLAM | twitchslam | Part1

I love occassionaly putting on George Hotz's streams while programming. Here's an 11 hour stream of him implementing SLAM from a closet: ▶ this video The guy's a certified legend. Sadly he 'quit' streaming but the hundreds of hours in the archive should suffice.

It's a different kind of watching, but you can find saved streams from geohotz / comma.ai. Those contain things like learning about blockchain contracts and finding a security bug in one of them in a very informal 8h live stream. Or building a toy computer vision project from scratch for a recorded dashboard footage. ▶ this video It's an experience... Try watching at higher speed when it gets boring.

I am working at a company that is tracking vehicles using GNSS antennas. When designing the vehicle dynamics model for the Kalman Filters, I found it useful to have a graphical representation (including error ellipses, velocity vectors etc). Turns out that pygame was a great fit for that type of visualization. Fast forward to two days ago, when I was idly watching George Hotz design a monocular visual SLAM prototype in 11h. Much to my surprise, one of the first things he fires up is pygame for visualization [1]! [1] ▶ this video

Sorry to be holy-wary, but that was outrageous: just watched random pieces of that video until found one where he actually codes, basically vim Python editing. So I opened somewhere around this moment: ▶ this video And, first, he copy-pastes some code, and then spends about a minute figuring if he got tabs converted to spaces, including googling a vim command. Then he proceeds to make a loop over some collection next to the loop over an adjacent collection. And he makes that stupid mistake of renaming a variable of the loop, but no renaming in the body. Man, if that's how professional vim users work, this piece of video will be the only proof I will ever need to prevent zealots from even wasting IDE users time to try vim.

Hi everyone, so I'm the guy who wrote this article. I'm sharing a video recording of George Hotz writing some Python code. Note his reaction at 5:55 ▶ this video His outburst is an emotional manifestation of the different sources of frustration I've had working with Python that I've tried to document. A common theme I've seen in responses is that many claim that I've mistaken Python as a weakly-typed language countering that it is indeed a strongly-typed language -- obviously an argument of semantics. I'll define a "strongly-typed" language as one where it is trivial to identify the type signature and definition of any function or variable in a program. In Python, this is non-trivial. FYI, this article is also cross-posted on: link link link