Closed marianoguerra closed 2 years ago
🔙 Backward Execution 🔎 Visual Ideation Space of Interactive Explainers 🍃 Coding Sensorial Cues 🐢 Objects All The Way Down
🎥 Mainframe Demo - May 5 via André Terron
Hello everyone! Here's my first two-minute-week video about Mainframe: Helping app developer sync and import data from any API or database.
📝 Little UI for compass-and-straightedge constructions using love2d.org via Kartik Agaram
Shower thought after chatting with Jack Rusher: we delay teaching kids geometry until we can trust them not to poke someone's eye out with the pointy end of a compass.
Here's a little program to do compass-and-straightedge geometrical construction on a computer
Pictured below: constructing a second line (in black) parallel to a given line (red) passing through a given point.
👓 AR/VR Code Visualizing via Ivan Lugo
Hello friendly internet people!
I’m happy to share the current state of my tiny, incomplete, toy of an AR project for iOS / macOS designed to parse, analyze, trace, and render Swift application runtimes in 3D space. I’m posting the Github link here, and I thank anyone and everyone many times in advance for taking a curious moment to take a peek, and maybe even share your enthusiasm and interests!
I am absolutely open to critiques, comments, questions, thoughts, and of course offers to work alongside you and your like-wise visualization/AR/VR obsessed team <3
💡 The MAYA Principle via Mariano Guerra
Loewy’s secret was essential to design for the future – but delivering the future gradually. He designed his famous logos, some of the most recognizable cars of the 40s, 50s, and 60s, refrigerators, and locomotives for his users’ present needs and skills while pushing the boundaries of design and technology beyond his users’ expectations. He called this approach the MAYA principle. Maya is an abbreviation for “Most Advanced. Yet Acceptable.” which means that Loewy sought to give his users the most advanced design, but not more advanced than what they were able to accept and embrace. Loewy believed that:
"The adult public's taste is not necessarily ready to accept the logical solutions to their requirements if the solution implies too vast a departure from what they have been conditioned into accepting as the norm."
💬 Vaughan Rouesnel
Visualizing data structures (e.g. in PostgreSQL)
When we think about the data structures our programs use or the execution flow of our programs, I’m pretty sure we all think visually and if we had to explain it to someone we would be drawing diagrams on a whiteboard. Yet pretty much all our coding and debugging is text-based. We are forced to visualize things in our minds.
I’ve been debugging the PostgreSQL codebase to better understand how things work. I think a lot of people treat it like a scary magical black box, but it’s quite easy to debug a query’s execution path, and start to understand how it works.
When we learn about databases, say from Andy Pavlo’s CMU database course, there are a bunch of core diagrams used to explain things. Like the parse tree, logical plan tree, physical plan tree, disk storage layout, btree/bitmap/hashmap index, etc.
So what I was thinking was to instrument the PostgreSQL C codebase (via LLVM-IR), and then visualize some of the key data structures and stores. Imagine how easy it would be to teach database internals, if you could type in a query, and then visually step through the actual execution of the query with visual diagrams. I would imagine that any PowerPoint slides and diagrams could be replaced by this visual interface with a slider and some filtering options for what to show.
🎥 Alan Kay - SDM conference via Andreas S
Just found this gem while cleaning up my Zetelkasten a bit : 40:41 "using objects at the lowest level in the system and combining the language with this idea of co-routines so I realized that if you had co-routines and persistence you didn't need files because you basically just paused every structure that you wanted to stay around and just let it stay active there's a way of getting away from data structures so a lot of interesting ideas in this thing and on each iteration of these languages.."
🎥 2022 Blockly Developers Summit: Backwards Execution via Jason Morris
Blockly Developer conference is running tomorrow and wednesday. One of the staff talks is this video showing how by serializing the state of a JS Interpreter, and taking diffs as the state changes, you can build a javascript debugger that has "next" and "previous" options for navigating the code execution.
🎥 Malloy Composer via Mariano Guerra
Malloy is an experimental language for describing data relationships and transformations. It is both a semantic modeling language and a querying language that runs queries against a relational database.
Malloy Composer is a demo of a data exploration tool built using using the Malloy Language.
🧰 The XAI Primer via Jack Rusher
Really gorgeous zoomable UI work here that would be very interesting in a visual programming context:
Open access paper about the work: xai-primer.com — A Visual Ideation Space of Interactive Explainers
🤯 Cryptography in Scratch via Kartik Agaram
Looks like it's Scratch as a compile target. Not sure if that makes it more or less impressive.
📝 Magic Ink via Kartik Agaram
I find myself rereading the Magic Ink (2006) paper today. Vintage Bret Victor from before all the famous talks.
When I reread it now, the most valuable lesson for me is the meta-lesson about just the amount of effort it takes to make a memorable argument. The motivation for this paper was:
Before I release v1.0 of the BART widget, I’d like to write a little paper about its design…
—Bret Victor (2005)
People have been writing blog posts for 20 years about how they built something, or how they would redesign the American Airlines website or whatever. Here that's an interlude. This paper packs more effort into a single picture, more puns into a single example, than most whole papers. I'm no longer young, and yet the effort shock is immense.
🎥 Google Little Signals via Mariano Guerra
Would be nice to add them to Dynamicland
Little Signals explores new patterns for technology in our daily lives. The six objects in this design study make use of different sensorial cues to subtly signal for attention. They keep us in the loop, but softly, moving from the background to the foreground as needed. Each object has its own method of communicating, like through puffs of air or ambient sounds. Additionally, their small movements or simple controls bring the objects to life and make them responsive to changing surroundings and needs. Just as everyday objects might find simple ways to inform us - like the moving hands of a clock or the whistle of a kettle - Little Signals consider how to stay up-to-date with digital information while maintaining moments of calm.
Learn more on: littlesignals.withgoogle.com
[x] Change Month and Week Number
[x] focWeekExport "2022-01-19" "2022-01-26"
[x] Summary
[ ] Hashtags
[x] Check that comment links work (push weekly dump with channel summaries)
[x] Check to mention right person for moved messages
[x] Update Search Index
[x] Download New Attachments
[x] Update links
https://tinyletter.com/
https://tinyletter.com/marianoguerra/letters/
http://localhost:8000/history/
https://marianoguerra.github.io/future-of-coding-weekly/
https://stackedit.io/app#