Got flashbacks to 1999 from some of those charts - I had a pair of design charts (partly for arguments, partly for onboarding) that were 17 nodes each and a lot of lines. (A coworker snuck in some extra nodes and an arrow labeled "troops move through Austria" and it was a while before anyone other than me noticed - yeah, that kind of chart.) This is not a lesson in design complexity - the design was pretty tight for what it did, even if you go back and read the patents - it's a lesson in the use of abstraction for explanation complexity and that you can break up the presentation more sanely than the code-on-disk actually is, you just have to stop and think about it (and have a bit more empathy for the people you're presenting to than, well, anyone in 1999 actually had :-)
The edit was perhaps personal... actuarily, three decades is what I'd be given =D
Now that I'm revisiting these comments, thanks for pointing out that 30 - 25 == five years into the future [honestly, I hadn't even given this any thought...]
I was surprised to learn (from this article) that there are local models that can do this (not sure if there are any that run on hardware I actually have though, unlike Tesseract which works fine on the scanning hardware I set up for it ~5 years ago.) For privacy reasons, cloud-based OCR is a non-starter...
Ooh, that's a worthy challenge. Of course, I can imagine getting enough data on all of those cities and deciding to launch everywhere else but not Boston "because your roads are garbage and you all drive like you're impaired 24/7" :-)
Heh, in the early days of C++ (1990ish) I had a notable application of 3+4 involving a doubly linked list with cache pointers (time-sequence data browser so references were likely "nearby" as the user zoomed in; spec was to handle streaming data eventually.) Had problems with it crashing in pointer-related ways (in 1990, nobody had a lot of C++ experience) so I cooked up a really dumb "just realloc an array" version so I could figure out if the problem was above or below data structure... and not only didn't the "dumb" version crash, it was also much faster (and of faster order!) due to amortized realloc - doing a more expensive operation much less often turns out to be a really good trick :-)
Listing alumni degree year is generally an "insider" thing (noone who isn't also a Cornell alum really cares which year, especially for a bachelor's degree; likewise Cornell doesn't mention the Harvard '95 PhD in Applied Physics, even if it's probably more relevant to the work...)
"insider" thing, you can be certain that an exempliary mind such as his did not get fired up in a vacume, and that 90, was a year and place that likely produced an iteresting mixed bag of characters, or in other times would be refered to as "schools of thought", and then some went off to bell labs which still functions as an intelectual singuarity that leaks concepts through it's event horison ocasionaly, or in this case displays time dialation effects.
On my Polestar 2, I was surprised how in actual use, friction braking was basically zero - to the point where when you start a trip the brakes are used for a few seconds to make sure they're still working (and scrub them a bit.) In actual driving - without trying particularly on my part - it's just always regen.
Somebody recently used a variation of this to get good video of welding - basically a camera synced with a very bright (strobe-ish) light, brighter than the weld itself, so you adjust the camera to the ludicrous-but-consistent brightness level and get details of the weld and the surroundings. https://www.youtube.com/watch?v=wSUxK8q4D0Q (Chronos "Helios", from early 2025)
Same - but mine are also primarily so I can hand out links to specific articles - they're not hidden but they're not advertised either (and they're static sites with almost zero logging, so I wouldn't really notice either except that this site has a published list :-)
reply