✊ Live Programming in Hostile Territory 📡 Propagators 📄 What Does ‘Human-Centred AI’ Mean?

Share Your Work

🗨️ Pandi Lin:

🧵 conversation @ 2025-09-08

Hi everyone 👋
I’ve been working on a JavaScript implementation of Sussman & Radul’s propagator model and wanted to share some progress + questions. here's the link to the repo: https://github.com/Semi-0/Propagator
I currently have two branches:

1. A custom push-based version (works, but amb can get weird). (In the AMB branch)
2. A more faithful scheduler-based version, closer to the original design. (but amb still acts weirdly when execution gets large)

It supports almost all of the original Scheme machinery, and I’ve been experimenting with a reactive extension so propagator networks can drive UI updates.
Lately I’ve been exploring some theory: I noticed interesting parallels between wired diagrams in category theory and propagator networks, and I’m researching how to separate representation from execution (syntax vs. scheduler). And how I can perhaps making the propagator more self-reliant as independent programming languages.
Since I’m pretty new to open-source, I’d really appreciate advice on two fronts:

1. Research direction → does this “wired graph <-> propagator <-> representation/execution” connection resonate with anyone? Are there papers or projects I should look at?
2. Sharing the code → what’s the best way to make an infrastructure repo like this easier for others to understand? (Docs? examples? small demos?)

Thanks in advance for any pointers

🧵 conversation @ 2025-09-08

For anyone not already familiar with propagators, here’s a quick refresher:

A propagator network is a collection of small, independent agents connected by cells that hold partial information. Each agent watches its inputs and, whenever it can deduce something new, it updates other cells. Unlike ordinary functions, information can flow in many directions at once — for example, if you know two sides of a right triangle, the Pythagorean propagator can solve for the third no matter which two you provide. This makes propagators a general model for constraints, dataflow, multi-directional reactivity and incremental reasoning.

🗨️ guitarvydas: 🎥 PBP Part Basics

🧵 conversation @ 2025-09-09

🗨️ Guyren Howe:

🧵 conversation @ 2025-09-09

I can’t find a working link here or in the YouTube video. For those interested in further info about Propagators, see: https://wiki.futureofcoding.org/Propagators/

TIL that we have a wiki…

🗨️ Christopher Shank: ✊ Live Programming in Hostile Territory

🧵 conversation @ 2025-09-09

Orion Reed and I submitted a positional paper for LIVE 2025 called "Live Programming in Hostile Territory". Now that it's been accepted, I'm excited to hear peoples thoughts and feedback! It touches on a topic wider than just live programming and, at least to me, is very relevant to the FOC community. Here is the abstract:

Live programming research gravitates towards the creation of isolated environments whose success is measured by domination: achieving adoption by displacing rather than integrating with existing tools and practices. To counter this tendency, we advocate that live programming research broaden its purview from the creation of new environments to the augmenting of existing ones and, through a selection of prototypes, explore three adversarial strategies for introducing programmatic capabilities into existing environments which are unfriendly or antagonistic to modification. We discuss how these strategies might promote more pluralistic futures and avoid aggregation into siloed platforms.

https://folkjs.org/live-2025/

Thinking Together

🗨️ guitarvydas:

🧵 conversation @ 2025-09-12

A sketch that might inspire brainstorming. I perceive that we're "doing what we've always done" instead of stepping back and inventing new stuff, like they did in 1960. The "we've always done it this way" mentality results in epicycles piled on top of epicycles.

Linking Together

🗨️ Ivan Reese:

🧵 conversation @ 2025-09-08

(Graphics) Clever use of screen-space vertex positions + edge depth to represent impossible objects in a robust way.

Meschers: Geometry Processing of Impossible Objects

🗨️ Ivan Reese:

🧵 conversation @ 2025-09-08

Double header — lead author on the above also has a good paper/talk about gender and bias in graphics research.

🗨️ Jasmine Otto:

🧵 conversation @ 2025-09-09

Dreyfus 1965, 98p. longread, early example of critical AI. feels kinda ripped from the headlines.
emphasizes gestalt processing & gestures toward embodiment. looks like frame problems and wicked problems (critique of reductionist / associationist assumptions) developed in parallel

📝 Lori Emerson (@loriemerson@post.lurk.org)

I am SO enjoying this very early...the earliest? critique of AI from 1965 whereby Hubert Dreyfus calls the hot air about AI "the production of intellectual smog" #ai https://www.rand.org/pubs/papers/P3244.html

🗨️ Mattia Fregola: 📝 Physically based rendering from first principles

🧵 conversation @ 2025-09-11

Feels like it might have been shared before, if not this is pretty awesome:

📝 Physically based rendering from first principles

🗨️ Jasmine Otto:

🧵 conversation @ 2025-09-12

good manifesto for slow tech 📄 What Does ‘Human-Centred AI’ Mean? (15p.)

🦋 olivia.science

Something I hinged on to get to this what I describe: the Marxian fetishisation of artefacts is so complete in the case of AI that not only do we somehow conclude machines think, but we accept for them to think, speak, draw instead of us, while also thinking these are (expressions of) our thoughts.

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🎼 Unleashing Creative Expression in Music Score Writing 📝 Type Checking is a Symptom, Not a Solution 🤔 What Declarative Languages Are

Two Minute Week

🗨️ Jasmine Otto: ♾️ Infinite Love Triangles (and other Graph Coloring Experiments)

🧵 conversation @ 2025-09-05

Someone asked me to define a "splot", which is like a flood-fill texture for narrative design. In addition to doing that, I've started teaching robots to spill tea. Hmm

Infinite Love Triangles (and other Graph Coloring Experiments)

Wave Function Collapse (WFC) is an algorithm for constraint propagation on adjacency graphs. Game designers use it to procedurally generate interesting levels for players to traverse. Let's use it to generate toxic relationships instead. Now we have a bunch of interesting relationship roles that might get thrown around when heartbreak happens. Red is for traitors, orange is for their enablers, and yellow is for people who got hurt. (Green doesn't care, and teal tries to help.) Use these buttons to assign ne

Share Your Work

🗨️ guitarvydas: 📝 Type Checking is a Symptom, Not a Solution

🧵 conversation @ 2025-09-05

DevLog Together

🗨️ Tom Larkworthy:

🧵 conversation @ 2025-09-07

Trying to properly learn codemirror 6. I upgraded my AI with code search and optimised its prompt with GEPA so it could help me program codemirror better. Given Observable is going plain Javascript, that simplifies things a bit language-wise and its just a matter of getting the off-the-shelf JS language syntax highlight working + injecting runtime state for code completion based on the current state of the runtime. My new prototype runtime editor lets you change the runtime graph using the plain JS SDK instead of the higher level cell model. Anyway, nice to start understanding about 3% of codemirror's programming model. I think getting rid of cells will make things more straight forward.

Thinking Together

🗨️ guitarvydas:

🧵 conversation @ 2025-09-04

Pond'ring aloud:
We know that "loop" is recursion, but recursion is often expressed in too-academic a manner.
We know that recursion consists of 2 parts:

1. termination case
2. recursion case.

I'm thinking about what might be a less-inhumane syntax for expressing a recursive solution. Suitable for non-programmers and LLMs?

[aside: the goal is not "efficiency" at the machine level, but expressiveness and human (non-programmer) understandability]

humane syntax???:  
----------------  

break down member (x, list) -> ([#found | #not-found], value) {  
    finish when list is empty { ^ #not-found, ɸ }  
    finish when x in list     { ^ #found, list }  
    decompose list' <- rest (list) {  
        ^ again (x, list')  
    }  
}  

break down append (x, list) -> value {  
    finish when list is empty { ^ x }  
    decompose «item» <- first (list), «list'» <- rest (list) {  
        ^ prepend «item» onto again (x, «list'»))  
    }  
}

inhumane syntax:  
----------------  

(defun my_member (x lis)  
  (cond ((null lis) (values nil nil))  
        ((eq x (car lis)) (values t lis))  
    (t (my_member x (cdr lis)))))  


(defun my_append (lis x)  
  (cond ((null lis) x)  
        (t (cons (car lis) (my_append (cdr lis) x)))))

[aside: "send ..." sends something forward asynchronously instead of returning it synchronously to the caller and unblocking the caller]

less-inhumane syntax involving async ports:  
-------------------------------------------  

break down member (x, list) output ports: { success: [#found | #not-found], value: object } {  
    finish when list is empty { send success: #not-found, send value: ɸ }  
    finish when x in list     { send success: #found, send value: list }  
    decompose list' <- rest (list) {  
        ^again (x, list')  
    }  
}  

break down append (x, list) output port: { value: object } {  
    finish when list is empty { send value: x }  
    decompose «item» <- first (list), «list'» <- rest (list) {  
        send value: prepend «item» onto ^again (x, «list'»))  
    }  
}

suggestions / comments?

Linking Together

🗨️ Konrad Hinsen: 👨‍💼 Issue 084: Spreadsheets

🧵 conversation @ 2025-09-01

A few articles on spreadsheets that are well worth reading:

Issue 084: Spreadsheets

Welcome to the 84th issue of De Programmatica Ipsum, about Spreadsheets. In this edition, we declare spreadsheets the most popular software programming environment of all time; in the Library section, we learn how to use Lotus 1-2-3 for science reading "Spreadsheet Physics" by Charles Misner and Patrick Cooney; and in our Vidéothèque section, we discover that Excel is a Turing-complete, functional programming language through the eyes of Dr. Felienne Hermans.

🗨️ Nilesh Trivedi: 🤖 Coding Agent Builders Mixer · Luma

🧵 conversation @ 2025-09-05

I am hosting an online mixer this Sunday for those who are building coding agents:

Coding Agent Builders Mixer · Luma

If you're building Coding Agents using LLMs, this online meetup should help you connect with similar folks and discover ideas and opportunities.

🗨️ Ivan Reese:

🧵 conversation @ 2025-09-05

there's actually a surprisingly simple and useful definition of declarative language: a declarative language is any language with a semantics [that] has some nontrivial existential quantifiers in it.

What Declarative Languages Are

Music

🗨️ avon:

🧵 conversation @ 2025-09-02

Hi all, I remember running into a wonderful blog post a while back where the author described recreating a DAW from a sort of hazel(https://github.com/hazelgrove/hazel)-like moldable programming environment. I unfortunately cannot find the post in my bookmarks, and my searching the last few weeks has turned up empty. Does this ring a bell for anyone?

🗨️ avon: 🎼 EuterPen: Unleashing Creative Expression in Music Score Writing

🧵 conversation @ 2025-09-05

Searching for that livecoding blog post I mentioned above, I found this really amazing programmable ink software for composing:
🎼 EuterPen: Unleashing Creative Expression in Music Score Writing By Vincent Cavez, Caroline Appert, Catherine Letondal, Emmanuel Pietriga

Video demo

The pattern manipulation & search operations are especially interesting imo.

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🧑‍💻 Write your own tiny programming systems 🎥 Python: The Documentary 🗓️ FoC Meetup

Two Minute Week

🗨️ Ivan Reese: 🎥 automerge cards

🧵 conversation @ 2025-08-31

Share Your Work

🗨️ Dany:

🧵 conversation @ 2025-08-29

I recently finished (and released) my first app built in my miqula programming system: https://danybittel.ch/marbling
Overall it worked quite well. Still some dearly missing features (like constants)... and bugs are super demotivating when I need to switch back to C++.
I really need to look for some paid work right now.. that's why I've been a bit quite in here.

Reading Together

🗨️ When Leggett:

🧵 conversation @ 2025-08-27

I just got finished reading "The Dream Machine" about Licklider - great book, I recommend it to anyone who ever enjoyed an Alan Kay talk

Thinking Together

🗨️ Eli: 📝 Oatmeal - To the surprise of literally no one, I'm working on implementing a programming language all my own

🧵 conversation @ 2025-08-27

Inspired by conversation last night at the virtual meetup, I wrote a blog post to introduce the toy language I’ve been working on.

Inspired by conversation at a recent Future of Coding event, I decided I’d write up a little something about the programming language I’ve been

Linking Together

🗨️ Stefan: 🧑‍💻 Write your own tiny programming systems

🧵 conversation @ 2025-08-25

Came across tomasp's teaching materials and would like to especially highlight these two courses here:

1. Write your own tiny programming systems — build your own tiny versions of ML, Basic, HM type system, Prolog, Self, Excel
2. Programming Language Design — fantastic resources that embed technical language features into a broader perspective of design and culture

This is the kind of resource that is absolutely amazing to be publicly available under such permissive license.
Seriously, look at the tiny programming systems and bootstrap your way into your favorite programming environment in an afternoon or weekend. Don't miss the source code for the demos in the same repo. The only things missing are a TinyLisp and a TinyForth, but you can find those easily somewhere else on the Internet.

🗨️ Craig Abell:

🧵 conversation @ 2025-08-30

Saw Will's Rust for Everyone! talk earlier oh his research into tooling to help people understand programs. The program slicer (highlights all lines impacted by the current line) seems particularity useful for understanding large functions.

🗨️ Konrad Hinsen: 🎥 Python: The Documentary | An origin story

🧵 conversation @ 2025-08-31

Python: The Documentary | An origin story is a somewhat surprising movie, in the sense that I haven't seen anything similar yet in the Open Source universe. I'd summarize it as an autobiography of the Python community. In general, I am not particularly interested in autobiographies. But as an ex-member of the Python community, it was nice to see the aged faces of people I interacted with in the past, or even just faces to put on the names of people I never met but exchanged lots of e-mails with at some time.
Still, I'd be much more interested in a history of Python and its community, written by a trained historian and adding historical context and outsider views to the memories of the main protagonists.

Present Company

🗨️ When Leggett:

🧵 conversation @ 2025-08-27

I guess this isn't exactly a presentation, but I'll be at the IIW unconference this fall if anyone else is gonna be there or wants to sign up: https://internetidentityworkshop.com/

also happy to chat about it with anyone interested but not sure or whatever

🗨️ Maikel: 🗓️ FoC Meetup · Luma

🧵 conversation @ 2025-08-28

Our next "european" FoC meetup is on the 24th of september, this is the luma link : https://lu.ma/eog1qc5x and we already have 2 guests (I'll contact you), so we're looking for one more demo/presenter! This meetup will last an hour

Information about our meetup can be found here : https://futureofcoding.org/meetups

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🗃️ Grist: Organize your data, your way 💡 Icepath: a 2D Programming Language 🧑‍💻 Alpaca 2025: Algorithmic Patterns in the Creative Arts

Share Your Work

🗨️ Alex McLean: 🧑‍💻 Alpaca 2025: Algorithmic Patterns in the Creative Arts

🧵 conversation @ 2025-08-23

Alpaca festival and conference on algorithmic patterns in the creative arts In-person talks+workshops+concerts+algorave in Sheffield, much of which will be streamed online, from 12-14th September 2025

Then continuing as on-line conference into the following weekend, with in-person watch parties/hubs in Barcelona, Berlin, Linz and Sheffield

Features a fair amount of live coding, including a paper from the mysterious 'pastagang' Full info and line-up/schedule:

2025.algorithmicpattern.org

🗨️ Scott: 📝 Safe Is What We Call Things Later

🧵 conversation @ 2025-08-24

Wrote a little followup to the post from last week based on the conversation with Jonathan Frederickson and D. Schmudde: 📝 Safe Is What We Call Things Later

Some Software Engineering Folklore

DevLog Together

🗨️ Ezhik:

🧵 conversation @ 2025-08-18

Making a little Obsidian plugin that lets you cook small apps right inside of your vault.

I find boilerplate annoying for little experiments, so I got rid of all of it. Each file is a standalone little app that automatically gets built and executed. Data persistence is also usually a pain, so it's nice to be able to just do it HyperCard style and have changes auto-save right to the file.

🎥 Screen Recording

🗨️ Kartik Agaram:

🧵 conversation @ 2025-08-18

I add a feature and add a toggle of state for it. Then I add another feature and add another toggle. Do I really need to handle 4 possible states now, or just 3, i.e. I have an enum in disguise 🥸? I keep making this mistake. Designing things up front is easy, but I find it impossible to reliably avoid mistakes when adding to an existing design.

Thinking Together

🗨️ Christopher Shank: 🎥 My Favourite Games from GMTK Game Jam 2025

🧵 conversation @ 2025-08-18

The theme of the GMTK Gam Jam was "loops" and there are lots of fun and novel explorations of affordances, interactions, and mechanics that feel applicable to the types of stuff explored here

🎥 My Favourite Games from GMTK Game Jam 2025

🗨️ Ivan Reese:

🧵 conversation @ 2025-08-24

Anyone have experience with XSLT? The recent kerfuffle about removing it from the html spec and the episode of Igalia Chats about it were both quite interesting to me. A declarative tree-transformation language!? Sounds like the sort of thing you could build a web app engine around ;)

Linking Together

🗨️ Pablo Donato: 🗃️ Grist: Organize your data, your way

🧵 conversation @ 2025-08-18

Not sure if it was already shared here before, but Grist looks like a good contender in the No Code/Relational Spreadsheet game. It seems to be to Airtable what Zulip is to Slack: an open-source, self-hostable, and more customizable alternative.

Learn about all of Grist's powerful spreadsheet-database product and its many features.

🗨️ Eli:

🧵 conversation @ 2025-08-20

Ends in what is likely a fun question for these parts:

In the 1970s, you could launch a new language with a paper and a maybe a compiler and/or interpreter. In 2025, you need an integrated product, a narrative, and enough momentum to bootstrap an ecosystem and on top of that a huge corpus of code that can only be created through sustained use. Modern langdev is daunting to say the least.

Where do languages go from here?

• Languages could be shaped by physical and purpose-specific constraints once again. Tomorrow’s interesting languages may target IoT, SBCs, edge devices, Blockchain, GPUs, and let’s not forget that the world still runs on microcontrollers.
• Python is the lingua franca of AI, which means it’s the lingua franca of LLM-generated code. Eventually Python will force LLMs to eat their own tail, but more immediate an over-reliance on AI-generated code will expose inherent weaknesses in the technology. We’re seeing real problems with an increased lack of rigor and there are novel problems that LLMs simply cannot solve. These short-comings are opportunities.
• Future innovations may look more like a new operating environment with integrated semantics across distributed systems, or programmable infrastructure that blurs the line between language and runtime.

🗨️ Jon Tran: Open-source geometric constraint solver

🧵 conversation @ 2025-08-21

A while back, when I saw the Inkling presentation I said that my company was working on designing a constraint solving system for CAD. It's just getting started and still very much a work in progress, but it's happening. https://github.com/KittyCAD/ezpz

🗨️ Konrad Hinsen: 📝 Google is killing the open web

🧵 conversation @ 2025-08-22

A statement I frequently hear is that no platform is as stable as the Web platform, because everyone makes an effort to keep old Web sites functional. The current XSLT debate suggests that this stability may soon end, as part of another enshittification campaign.

📝 Google is killing the open web

The juggernaut is taking advantage of its dominant position to enclose and destroy the commons.

🗨️ Jimmy Miller: 💡 Icepath: a 2D Programming Language

🧵 conversation @ 2025-08-23

https://healeycodes.com/icepath-a-2d-programming-language

A little 2D programming language called Icepath. Named after the ice puzzles in Pokémon Gold and Silver. The vibe I was going for was sliding around a cave and hitting opcodes.

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🛸 A moldable Common Lisp object inspector 🧑‍🔬 Trying out "Reflective Prompt Evolution Can Outperform Reinforcement Learning" 📄 Hierarchical File Systems are Dead

Share Your Work

🗨️ guitarvydas: 📝 De-Spaghettifying Control Flow & 📝 Towards Asynchronous Programming Workflows and Languages

🧵 conversation @ 2025-08-11

In my mind, CPUs implement subroutines, and, "functions" are but artificial constructs built on top of subroutines. Here are some more attempts to explain this hardware-centric view (see, also, the playlist of short videos in the first article).

📝 De-Spaghettifying Control Flow

📝 Towards Asynchronous Programming Workflows and Languages

🗨️ Robin Heggelund Hansen:

🧵 conversation @ 2025-08-12

I'm working on a language called Gløgg, which is a fully declarative, relational language where the source code is stored in a sqlite3 database as AST.

I now just got vite support and (proof of concept) dom integration working.

I'll be doing a whole presentation on Gløgg at the upcoming JavaZone conference (september 3-4).

🎥 glogg

🗨️ Scott: 📝 The System Inside the System

🧵 conversation @ 2025-08-17

I've been thinking about the Viable System Model as a framework for AI agents since I came across it, mentioned it here actually: https://futureofcoding.slack.com/archives/C5T9GPWFL/p1748381760844169

Finally put together some rubygems to explore it - vsm the framework and airb a CLI-based agent built with it and wrote up some more detailed thoughts about them on my newsletter:

📝 The System Inside the System

Announcing two new Ruby gems: vsm and airb

DevLog Together

🗨️ Konrad Hinsen: 🛸 A moldable Common Lisp object inspector based on CLOG

🧵 conversation @ 2025-08-11

I finally implemented dataflow-based reactive views for my moldable inspector for Common Lisp. It's much shorter than the limited input handling I had before, and also more versatile. I am working on a demonstration/example, stay tuned...

There seem to be two widely used dataflow implementations for Common Lisp, out of which I picked the simple one (https://github.com/kchanqvq/lwcells) over the complex one (https://github.com/kennytilton/cells).

In the process, I ran into my first experience with ambiguities in the Common Lisp specification, with one of my new indirect dependencies.

Thinking Together

🗨️ Joel Neely:

🧵 conversation @ 2025-08-17

• The clean way that the if/fi and do/od constructs embraced non-determinism still looks cleaner to me than the contemporary toolkits of various mainstream languages and frameworks.

Linking Together

🗨️ Ivan Reese:

🧵 conversation @ 2025-08-11

Let's have a discussion that'll hopefully generate lots of links.

Microsoft have just placed GitHub under AI in their org chart.

If I don't want to stick around and find out what fresh hell comes next, where should I go instead? Gitlab? Codeberg? Sourceforge? Send me links to your favourite social network for git repos!

🗨️ Bill Mill:

🧵 conversation @ 2025-08-12

a semi-related opinion that I don’t want to clutter that thread with:

self-hosting is awful* and there’s a big opportunity to develop structures for community-hosting things like git forges, chat servers, &c. Spread the load and develop social experience for sharing resources

*: too much work for too little use, too expensive, nobody wants to be on the hook all the time for maintenance so it rots

🗨️ Chris Knott:

🧵 conversation @ 2025-08-13

I thought I would hate this paper (Hierarchical File Systems Are Dead) because I actually zealously love the hierarchical directory metaphor and hate the modern broth of files approach. In fact it is basically neutral on the user facing metaphor, recognises the necessity of replicating posix if anything will ever get traction, and is overall very good.

More like - how do we reify semantic search and tagging to the lowest level of the OS

📄 Hierarchical File Systems are Dead

AI

🗨️ Tom Larkworthy: 📝 Trying out "GEPA: Reflective Prompt Evolution Can Outperform Reinforcement Learning"

🧵 conversation @ 2025-08-12

I completed a toy setup of GEPA with some fricken good results! I am very happy to have a methodology that removes some of the guess work with prompt design. Its a really simple algorithm that orchestrates a genetic evolution where the mutation operator is asking a LLM to improve the prompt based on the diagnostic trace your evals. So simple! I also enabled websearch during reflection so it can actually do its research when improving the prompt. This means it would adapt the web documentation to suit the prompt format automatically. Very good, been looking for something like this and it did not disappoint.

🧑‍🔬 Trying out "GEPA: Reflective Prompt Evolution Can Outperform Reinforcement Learning"

Present Company

🗨️ Ivan Reese:

🧵 conversation @ 2025-08-12

We still have nobody offering to demo this month at the weirdly timed meetup (North American Tuesday Evening, or NATE). If nobody volunteers I'll have to get weird with the format. We need your help to make sure that doesn't happen: 👉 Call Now 👈

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🔌 Spirit Plant Software and Network Architecture 🎥 Virtual Meetup 13 • July 2025 🧑‍🔬 Notes from the Lab

Share Your Work

🗨️ guitarvydas:

🧵 conversation @ 2025-08-06

reading When Leggett post caused me to write this article

🗨️ Marcin Ignac: 🔌 Spirit Plant Software and Network Architecture: a technical case study

🧵 conversation @ 2025-08-07

We have just published an in depth case study about our last generative (non genAI) art installation. All JS + WebGL baby! Check it out Spirit Plant Software and Network Architecture: a technical case study. · Variable - new ways of experiencing data | https://variable.io

We used web technologies to power the Spirit Plant installation visuals in real-time.

DevLog Together

🗨️ Christopher Shank: 🧑‍🔬 Notes from the Lab - June & July 2025

🧵 conversation @ 2025-08-09

Latest notes about what we've been working on with the folkjs project. Explorations include DOM sync, Desktop Interlay via Accessibility Trees, DOM interactions and instruments, HTML pipes, HTML attributes for syntax highlighting, LSPs, and reordering lists, and much more!

Notes from the Lab - June & July 2025

Thinking Together

🗨️ Joel Neely:

🧵 conversation @ 2025-08-09

I hadn’t thought about your before-and-after interpretation in quite that way. I’ll have to ponder a bit.
Regarding your reference to determinism, only some constructions in EWD’s wp-based notation are deterministic! While some cases (e.g. x := x-y) are, EWD’s reasoning makes some kinds of determinism a not-very-interesting special case. The “Aha!” moment for me was his solution for max in c := a max b.

if  
   a >= b -> c := a  
[]  
   b >= a -> c :- b  
fi

In the (again, uninteresting) special case that a = b, both guards are true it is perfectly valid to “perform” either of the two guarded commands.

Linking Together

🗨️ Jasmine Otto: 🕹️ too many gamedevs and only one game

🧵 conversation @ 2025-08-04

ahaha, multiplayer bitsy in the wild at A MAZE (using MouseMux)

🗨️ Nilesh Trivedi:

🧵 conversation @ 2025-08-06

Prof Eric Hehner's April 2025 article on interpreting the Halting Problem:
https://www.cs.utoronto.ca/~hehner/Boxes.pdf

AI

🗨️ Jason Morris:

🧵 conversation @ 2025-08-07

Happy GPT-5 day to those who celebrate. I got to play with it at work a bit, and it is impressive. I think having the AI generate symbolic representations of facts in text is going to be a lot more feasible going forward, which is going to be a game changer for people who can figure out how to use it.

Present Company

🗨️ Ivan Reese: 🎥 Virtual Meetup 13 • July 2025

🧵 conversation @ 2025-08-07

Here's the video from last week's virtual meetup.

🗨️ Ivan Reese:

🧵 conversation @ 2025-08-07

I'd like to try planting (yes, like a plant that'll grow) the next virtual meetup at a different time, so that we can shake things up and bring out some folks who normally can't attend.

If we were to schedule it at 01:00 UTC Aug 27th (conversions: everytimezone, time.is) — so think evening of wednesday the 26th for north america, morning of the 26th for eastern asia — would you be stoked to attend? to present? give a 👍 on the post if you'd come, and if you might present, post a threaded reply!

🗨️ Maikel: 🗓️ FoC Meetup · Luma

🧵 conversation @ 2025-08-08

This month's FoC meetup is on a different time to enable other timezone's to more easily attend, here's the luma link: https://lu.ma/3olgtwn1 😎

📝 FoC Meetup · Luma

Information about our meetup can be found here : https://futureofcoding.org/meetups

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🎥 Bubble Menu 💡 Enough AI copilots! We need AI HUDs 🎥 Vibe coding a choropleth map in Observable Notebooks 2.0

Two Minute Week

🗨️ maf: 🎥 Bubble Menu 🎮💻 AUTOMAT DEVLOG 13

🧵 conversation @ 2025-07-30

Some context for the context menu:

🎥 Bubble Menu 🎮💻 AUTOMAT DEVLOG 13

DevLog Together

🗨️ Ivan Reese:

🧵 conversation @ 2025-07-28

Spent the weekend playing with claude code for my first nontrivial thing.

It's pretty wild. It feels so much like working with a super green junor dev. A lot of the same coaching strategies seem to apply well. Also, I'd forgotten how it's kinda fun to teach good debugging practices!

One major difference — I tend to hit the context window limit after about an hour, and have to start up a new session (because compaction sucks), which means I (seemingly) need to do a bunch of coaching to make sure claude is always externalizing its "thought" process to files so that the next agent can pick up where it left off. This sucks, or I just haven't figured out a good foolproof way to do it.

The nontrivial thing — I'm making a new version of my depth camera, but using gaussian splatting. So I'm using this as an opportunity to: * learn claude code * learn gaussian splatting * learn more swift

🗨️ Eli:

🧵 conversation @ 2025-08-01

My 3rd act reveal is that the future of coding is actually awk

• a kinda working scheme implemented in awk

, skwak

• let’s bring some functional programming niceties to awk, using awk, rawk

Thinking Together

🗨️ Kartik Agaram:

🧵 conversation @ 2025-08-02

This might be premature, but I think I finally understand Dijkstra's approach to deriving programs from post-conditions in "A Discipline of Programming". I've had this book on my bookshelf for almost 20 years, never understood it but also never quite worked up the will to toss it out. (For context, I only own like a dozen books over the long term.)

Concretely, I've made it to the end of Chapter 7. I feel like I understand every bit up until this point.

Parts of Chapter 6 and 7 feel very sloppily written! And this is Dijkstra! So either my leaps of interpretation are only leaps because I'm missing something, or my sense of understanding is an illusion 😅

Has anyone here made it this far and feel like they understood it? I'd love to talk to you.

Incidentally: I wouldn't have made it in even this my probably 4th attempt, if it wasn't for LLMs. They're better than a rubber duck for talking things over with! It's amazing that they can all converse intelligently about the Dijkstra method, and all I need to do is mention wp or wdec. Or I know nothing and am incapable of judging anything about this book.

🗨️ Mihai:

🧵 conversation @ 2025-08-02

Seems like the message from the Better Software Conference is that the future of programming should be: simple, low level ( aka fast ), imperative, data-oriented ( not oop ) coding. I kind of like it… Started working in C again for some personal projects, and I enjoy it.

Linking Together

🗨️ Mariano Guerra: 🎥 Vibe coding a choropleth map in Observable Notebooks 2.0

🧵 conversation @ 2025-07-29

Observable Notebooks 2.0 Technology Preview

🎥 Vibe coding a choropleth map in Observable Notebooks 2.0

🗨️ Jasmine Otto:

🧵 conversation @ 2025-07-31

pipeline synthesis via domain-specific visual programming. obviously they're over-claiming ('generate any stable, isolable molecule') as chemists, but as a PL person this sounds great! if you're a constructivist getting into assembly theory, I think this was written for us

Linking this framework to assembly theory strengthens the definition of a molecule by demanding practical synthesizability and error correction becomes a prerequisite for universality.

🦋 leecronin.bsky.social:

Making digital chemistry truly universal for chemputation (digital control of chemsitry) required a new approach to hardware, wetware, & software with the development of XDL. https://www.science.org/doi/10.1126/science.aav2211 Now the theory showing universality is done. https://arxiv.org/abs/2408.09171

🗨️ Ivan Reese:

🧵 conversation @ 2025-08-02

sapphirepunk – an alternative to cypherpunk, via Christopher Shank

🗨️ misha:

🧵 conversation @ 2025-08-02

https://www.reddit.com/r/nosyntax links and demos of structural/visual code editors https://github.com/yairchu/awesome-structure-editors/blob/main/README.md

🗨️ Denny Vrandečić: 📑 Gallery of programming UIs

🧵 conversation @ 2025-08-02

That links to the Gallery of programming UIs, but the link there seems dead (and the Internet Archive is no help): https://alarmingdevelopment.org/?p=1068 --- does anyone have a copy?

📝 Gallery of programming UIs

I’ve assembled a gallery of notable/interesting user interfaces for programming, as inspiration for the next Subtext. [Google Slides]

🗨️ Jack Rusher:

🧵 conversation @ 2025-08-03

https://blog.brownplt.org/2025/08/03/paralegal.html Something for our community of computational law enthusiasts. 🙂

AI

🗨️ Nilesh Trivedi: 💡 Enough AI copilots! We need AI HUDs

🧵 conversation @ 2025-07-28

🗨️ Tom Larkworthy: 📝 DSPy

🧵 conversation @ 2025-08-03

Just came across https://dspy.ai/ while researching GEPA. Seems to be a very flexible and programmable "LLMs as code" runtime. Sort of a functional abstraction over LLMs. Its got some very good credentials using it, it allowed things like optimising the prompt.

📝 DSPy

The framework for programming—rather than prompting—language models.

📔 GEPA: Reflective Prompt Evolution Can Outperform Reinforcement Learning

Large language models (LLMs) are increasingly adapted to downstream tasks via reinforcement learning (RL) methods like Group Relative Policy Optimization (GRPO), which often require thousands of rollouts to learn new tasks. We argue that the interpretable nature of language can often provide a much richer learning medium for LLMs, compared with policy gradients derived from sparse, scalar rewards. To test this, we introduce GEPA (Genetic-Pareto), a prompt optimizer that thoroughly incorporates natural language reflection to learn high-level rules from trial and error. Given any AI system containing one or more LLM prompts, GEPA samples system-level trajectories (e.g., reasoning, tool calls, and tool outputs) and reflects on them in natural language to diagnose problems, propose and test prompt updates, and combine complementary lessons from the Pareto frontier of its own attempts. As a result of GEPA's design, it can often turn even just a few rollouts into a large quality gain. Across four tasks, GEPA outperforms GRPO by 10% on average and by up to 20%, while using up to 35x fewer rollouts. GEPA also outperforms the leading prompt optimizer, MIPROv2, by over 10% across two LLMs, and demonstrates promising results as an inference-time search strategy for code optimization.

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🎙️ FoC 77 • As We May Think by Vannevar Bush 📄 Boxer: A Teacher's Experience 🎛️ Frame of preference

Share Your Work

🗨️ Ivan Reese: 🎙️ F----- o- C----- • Episode 77 • As We May Think by Vannevar Bush

🧵 conversation @ 2025-07-22

[I've had this episode finished and ready to publish for like 2 months now, ugh! Sorry it's so late. Yeah, this was recorded back in, like, April(?) when we were deep in the "rename the community" discussion. Sigh.]

We're trying to switch it up a bit between "classics" like this month's paper, more recent work (like the prior, and the next episode — already recorded and releasing soon dammit — a preprint, so fresh), and maybe some weirder things. If there's stuff you think we should read that's relatively short (ideally less than 20 pages), well-written, and arguably relevant (the more "arguably" the better I say!) then I'd love to know about it.

No, I'm not going to talk about the content of the episode. Everyone knows it, surely. Surely! Sur… fine.

As We May Think was written in the 1940s and, worried about the surge of information complexity in the modern world, imagines how advancements to present technology would allow for the creation of a special machine, dubbed the "memex", that bears a striking resemblance to the Personal Computer of the 80s and later. This paper is often referenced as a good starting point for folks beginning their journey into deeply understanding and reimagining the computer. It's historically significant, it suggests a bit of alt-history, and (rule of 3s) it does other stuff too!

🗨️ TodePond: 🎥 You can do collab strudel with flok.cc it's a lot of fun

🧵 conversation @ 2025-07-25

hello i gave a talk about a new live programming language called strudel

🎥 You can do collab strudel with flok.cc it's a lot of fun

🗨️ Laura Brekelmans:

🧵 conversation @ 2025-07-26

I started a Discord for people who're interested in communal computing/dynamicland specifically for people in the Netherlands (and Belgium, I suppose!)

If you happen to be from the lower lands, let me know

Thinking Together

🗨️ guitarvydas:

🧵 conversation @ 2025-07-23

Inspiration from today's demo meetup: Nilesh Trivedi casually tossed out the idea that there are 2 kinds of edges between software units: edge (visible line) and containment (invisible(?), but, easy to calculate using bounding boxes). I think that containment is important, but, I've been avoiding it because I could only think of complicated ways to represent it. If it's "just" an edge, then the problem is solved 🤦. I've used Prolog (exhaustive search using backtracking) in the past to infer edge information from JSON (SWIPL even knows how to inhale and exhale JSON). Now that backtracking is no longer a verbotten technique (OhmJS, Prolog, miniKanren, Nils Holm's Scheme code & transpilations of that code to other PLs, cl-holm, etc.) it should be straight-forward to create DPLs that use "containment" visual syntax. Hmmm...

Linking Together

🗨️ maf: 🎥 The Most ADVANCED VR Game in the WORLD! [Resonite]

🧵 conversation @ 2025-07-23

Resonite (a.k.a. Future of VR, whitepaper, video) has an interesting built-in scripting engine. Probably the most immersive programming environment I've seen. I'll have to dust off my VR headset to try this one out!

🎥 The Most ADVANCED VR Game in the WORLD! [Resonite]

🗨️ curious_reader: 📝 Rick Rubin | The Way of Code: The Timeless Art of Vibe Coding

🧵 conversation @ 2025-07-25

My quick search hasn't revealed anything so I just wanted to share this here again which a friend mentioned to me today:

https://www.thewayofcode.com/

📝 Rick Rubin | The Way of Code: The Timeless Art of Vibe Coding

Rick Rubin brings ancient wisdom to the modern age in The Way of Code, a meditation on the art and science of vibe coding. With Claude by Anthropic, the Grammy-award winning producer and author of The Creative Act turns philosophy into practice with artifacts that can be creatively modified with AI.

🗨️ Jeffrey Tao:

🧵 conversation @ 2025-07-25

A while ago I remember I came across a blog post or spreadsheet contrasting a large number of known non-textual programming languages. One attribute of each project was the modality: node-wire, scratch-like puzzle piece, etc. Does anyone know what I'm talking about or have a link? It is not The Whole Code Catalog or any of the linked surveys, nor is it the "Future of Coding or Programming: Project Comparison" spreadsheet.

🗨️ Kartik Agaram: 📄 Boxer: A Teacher's Experience [pdf]

🧵 conversation @ 2025-07-27

Lovely and heartfelt.

🗨️ misha: Tacit Talk Episode 1: Uiua with Kai Schmidt

🧵 conversation @ 2025-07-27

tacit (no local names), stack-oriented (forth), prefix-notated (lisp), APL https://www.uiua.org/
with a very good intro and "IDE" demo: Tacit Talk Episode 1: Uiua with Kai Schmidt

🗨️ Florian Schulz: 🎛️ Frame of preference

🧵 conversation @ 2025-07-27

Omg you can use all those old Mac OS versions here:
https://aresluna.org/frame-of-preference/

📝 Frame of preference

A story of early Mac settings told by 10 emulators.

AI

🗨️ Jason Morris:

🧵 conversation @ 2025-07-23

That's an interesting way of framing AI usage. I'm not sure I like "authentic." I think there is a sort of expertise or craftsmanship or fluency that grows over time, but I don't know that it's ever inauthentic. I also think authenticity doesn't really explore whether you are upgrading existing systems, designing new systems for current tasks, or making new kinds of work possible. I think AI has unrecognized potential in that last category.

Present Company

🗨️ Ivan Reese: work on Automerge

🧵 conversation @ 2025-07-23

Job posting — Ink & Switch is looking for someone to work on Automerge. It's something like a TypeScript + DevRel role, so if that sounds like you and you want to come work with a small group of playful researchers & engineers (and me), we'd love to have you!

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

🎥 Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake 📝Composable higher-order reactors 📝 Introducing XMLUI

Two Minute Week

🗨️ Jasmine Otto:

🧵 conversation @ 2025-07-17

Feeling excited to demo multiplayer Bitsy on Wednesday!

Share Your Work

🗨️ guitarvydas: 📝 On Options For Programming

🧵 conversation @ 2025-07-17

I've stated that CPUs don't implement "functions". In this article, I say this again, hopefully in a better way.

Thinking Together

🗨️ guitarvydas: 📝 Programming and Macros in 2025

🧵 conversation @ 2025-07-16

🗨️ guitarvydas: 🎥 Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025

🧵 conversation @ 2025-07-19

Watching this (again). I find myself wondering if this can be related to Morrison's FBP (flow based programming), especially his "conveyor belt" model. It, also, underlines my feeling that there should be a strong separation between the expression of programs in human-oriented terms, vs. some kind of automatic mapping from that human-readable domain to something production engineered to run on hardware CPUs. Currently, popular programming languages try to do both at once, usually leaning on humans to express code in ways that can be optimized for hardware (based on old-fashioned 1960s biases). I think that there should be two distinct languages and some automagic tooling that transforms from one to the other. A simple example is Prolog. Someone wrote a Prolog "engine" in machine code (or assembler, or an ancestor of assembler, like Lisp/Python/Haskell/C/etc). Prolog code allows humans to express "relational logic", then maps that logic onto operations for the engine (e.g. WAM).

🗨️ Dave Bauer:

🧵 conversation @ 2025-07-20

I've been reflecting on this video and now I need to go learn about Flow Based Programming. I have been trying to imagine what changes could be made to some of the code I've developed if a model hierarchy was not the only possible solution.

Linking Together

🗨️ Nilesh Trivedi: 📝Composable higher-order reactors as the basis for a live reactive programming environment

🧵 conversation @ 2025-07-17

Came across this during my search for ideas on distributed reactivity:

Composable higher-order reactors as the basis for a live reactive programming environment

📝 [July 7th, 2025 11:00 PM] nilesh.tr: Folks, can you please point me to recent efforts in Distributed Reactive Programming?...

Folks, can you please point me to recent efforts in Distributed Reactive Programming? How can we build whole systems (spanning multiple simultaneous users as well as the database) in React/Vue/Svelte- like way, instead of just UI components? What are the typical challenges and the unsolved problems?

🗨️ misha: 🎥 Casey Muratori – The Big OOPs: Anatomy of a Thirty-five-year Mistake – BSC 2025

🧵 conversation @ 2025-07-17

🗨️ misha: 🎥 Over the Shoulder 1 - Text Preprocessing in Forth

🧵 conversation @ 2025-07-18

forth "repl"

🗨️ Konrad Hinsen: 📝 Introducing XMLUI

🧵 conversation @ 2025-07-19

Very mixed feelings about XMLUI . I like the motivation and the overall approach to an accessible glue language, but just about everything about the implementation feels wrong. XML syntax is perhaps the worst - does anyone really want to stare at that kind of code?

In the mid-1990s you could create useful software without being an ace coder. You had Visual Basic, you had a rich ecosystem of components, you could wire them together to create apps, standing on …

🗨️ Natalie Freed:

🧵 conversation @ 2025-07-19

Does anyone know where this quote comes from? "How is the abstraction, for understanding? Is it well designed to help you see what is happening underneath?" I was so certain it was from Learnable Programming or another Victor piece but I cannot for the life of me track it down. Maybe it's my paraphrase or misquote of someone and that's why I can't seem to Google it? Let me know if this rings a bell for anyone!

Present Company

🗨️ Maikel:

🧵 conversation @ 2025-07-14

Next week we have a FoC meetup planned (23th of july, see announcement in the message above)... but we're still looking for one person who wants to present / demo something about their FoC project.. if you have interest please let us know 😊

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast

📝 Unleashing the Power of End-User Programmable AI 🎥 Jonathan Blow - Jai Demo and Design Explanation 🎥 The future and promise of a post-AI world

Share Your Work

🗨️ Dennis Hansen:

🧵 conversation @ 2025-07-08

Yo yoo! This is less technical but- thought it would be interesting to put LLM's into a generative 'outline' interface- I always loved workflowy, etc- maybe it sparks some ideas for y'all. Github - Play with it

🎥 branchy demo

🗨️ Karl Toby Rosenberg:

🧵 conversation @ 2025-07-10

Teaching computer science concepts (conditional branch handling and / or recursion) using Mondrian for inspiration?

🎥 solution video

Thinking Together

🗨️ Nilesh Trivedi:

🧵 conversation @ 2025-07-08

Folks, can you please point me to recent efforts in Distributed Reactive Programming? How can we build whole systems (spanning multiple simultaneous users as well as the database) in React/Vue/Svelte- like way, instead of just UI components? What are the typical challenges and the unsolved problems?

🗨️ curious_reader: 🎥 The InterBrain - How Collective DreamWeaving Can Heal the World

🧵 conversation @ 2025-07-10

Hey Foc!
This piece got swamped, but I do think it is worth while.
🎥 The InterBrain - How Collective DreamWeaving Can Heal the World
In the Video the Author proposes a tool to enable new communication patterns. He asks for fundraising: 📝 ProjectLiminality - Open Collective

And apparently he got funded.

He got like 160 issues yesterday , now its some epics.
https://github.com/ProjectLiminality/InterBrainMVP/issues

Why is it interesting? If you spend some time going through the README.md you can see that some aspects of it cover things like transclusion or spatial design. I can not help but it reminds me a lot of xanadu. Pretty interesting I will follow up.

An open source communication and co-creation layer bridging ancient wisdom & modern systems to reshape how we collectively share and organise around ideas

Linking Together

🗨️ Nilesh Trivedi: 📝 Unleashing the Power of End-User Programmable AI

🧵 conversation @ 2025-07-08

Erik Meijer on end-user programmable AI : 📝 Unleashing the Power of End-User Programmable AI

🗨️ Nilesh Trivedi:

🧵 conversation @ 2025-07-08

Chad Fowler lamenting the loss of programming as a craft people cared about:

🗨️ Mihai: 🎥 Jonathan Blow - Jai Demo and Design Explanation

🧵 conversation @ 2025-07-09

New Jonathan Blow talk at LambdaConf about Jai

🗨️ Nilesh Trivedi:

🧵 conversation @ 2025-07-10

Algebraic Replicated Data Types (ARDT): Programming Secure Local-First Software - by Rescala Lang folks
Found this as I am reading and learning about distributed reactive systems, specifically around web applications, where the same reactive DAG could manage state across clients, backends and databases.

🗨️ KP Kaiser:

🧵 conversation @ 2025-07-10

anyone interested in collaborating on a project for multiplayer LLMs and the future of social media?

think people working together to make a social media feed, a bit like twitch plays pokemon.

I'm looking for a frontend dev to partner with on a prototype project, making some chat UI components and some multiplayer chat to video. I've got a decent budget for infrastructure and have built a whole api that already exists and could work with this. it would just be a thing we build and release, with a couple thousand bucks worth of infrastructure credits I can throw at it.

feel free to shoot me a dm if you're interested in chatting!

🗨️ misha:

🧵 conversation @ 2025-07-13

https://bettersoftwareconference.com/ is happening now (online)

AI

🗨️ guitarvydas: 🎥 The future and promise of a post-AI world

🧵 conversation @ 2025-07-07

This keynote about the future of AI is from a non-programmer perspective. I found the discussion of "authentic AI" to be interesting. (meta: a trick that I have begun using is to watch a video, then, if I want to refer to a certain point without re-watching, grab the transcript and ask an LLM to summarize it)

🎥 The future and promise of a post-AI world

👨🏽‍💻 By 🐘 @marianoguerra@hachyderm.io 🐦 @warianoguerra

💬 Not a member yet? Check the Future of Coding Community

✉️ Not subscribed yet? Subscribe to the Newsletter / Archive / RSS

🎙️ Prefer podcasts? check the Future of Coding Podcast