A DEVELOPER WALKED ON STAGE DRESSED AS A 1973 ENGINEER AND "PREDICTED" THE FUTURE OF PROGRAMMING.
@slash1sol15K followers
689,121 views
32 Comments
Comments from the original post on X (Twitter)

@YourDuden3ss
He should’ve worn a short sleeve button up shirt to really sell it.
8 likes

@HenkPoley
On YouTube:
6 likes

@hannaanna88
The bit where we act shocked by 50 year old ideas packaged as inonvation never gets old. Almost like the industry runs on amnesia by design
4 likes

@PrometheusRoot
Genius. We think we are always so smart, but we know that people in the past were not. So this a genius way to show that we are still not that smart. Excelent take!
4 likes

@MAhmetson
He is not a programmer, he is a UX designer whom I respect as that. His idea revolutionized in the 90s to visual programming and wysiwyg. But matters mental model not what users see. So it’s failed dead end or not solved properly.
2 likes

@gtbck2earth
So fake. This is not history. Very sloppy use of some random facts with wishful thinking then shaming ‘future’ developers.
2 likes

@lagerskoy
The real lesson is that programming did not have to become walls of text, we just normalized the interface that won
2 likes

@sj_bennett
This was also expressed in the days of "data driven" programming and "object oriented" programming. It was incorporated in a language named Prolog and several others in the past.
2 likes

@philliplanos
lol when he started talking about API’s
2 likes

@szpak
"Tell the machine your goal instead of every tiny step." This is also the current paradigm shift in biology (agency all the way down—cf @drmichaellevin) and what it implies for medicine: human-whispering—tell the body your goal instead of molecular micro-managing.
1 like

@BTownJoe
For those of you that remember the Shlaer-Mellor method...
1 like

@hammertime_one
crazy how some of the "future of coding" was already figured out before the internet even existed
1 like

@AchiestDragon
yea the trap of early vonnuman arcitecture still in use today , lead to the single sequential thread of each core on multi core cpus , and the bit he missed , the bottelneck of memory bandwith over cpu access , the ditching of pipline proccessors used on some higher end mainframes in favor of simpler cpus a pipleine cpu for example one with say 8 stages , could do a log(cos(squre(a*b)/c))*sin(b*c)) as a single instruction , just data in and data out of the pipline , passing the intermediate values though the pipe without having to store or recall them individualy , ther just passed on to the next stage , saving quite a few memory read writes ( even at L1 chache ) , so rather than having say a 48core cpu , a single core with a programable 48 core recofigurable pipeline would have a significant performance advantage , but like he did say how to program it would be somthing that would not realy allow the use of legacy code or coding methods on half hybrid not fully fpga but partial confugurable pipline sub proccessors , passing data to the next after it did its little bit , on silicone where its timing is local to its core , as the distance accross the silicone adds a delay time , one that still affects the l1 cache read times , let alone actual system memory ,, theres a lot of room for improvment using primeraly ideas that where used in the 60's/70's that seemed to have been long forgoten in the name of refusal to learn and adopt new methods of programming , quite a valid talk
1 like

@gippp69
he actually predicted the future
1 like

@nxpatterns
👀 Too many mistakes, most likely intentional for comic effect, but I must admit, it is amusing. 🤭
1 like

@HarryTandy
Bret Victor is a legend, this talk hurts
1 like

@ns4235
There’s a lot of room for improvement for imperative programming already
1 like

@keenansmith82
@andreasxirtus
1 like

@caglararazx
It is a continuous observation. AI idea has been there since 50's. So these observations are not shocking at all.
1 like

@yhousegone
>quietly >lands AI slop
1 like











