✉️ Not subscribed yet? Subscribe to the Newsletter
Future of Coding Weekly 2025/05 Week 4
2025-05-26 10:33
🧰 Scrappy: make little apps for you and your friends 🎙️ Lu Wilson on Art of Creative Coding 🎥 ESP32 Composite Video
Our Work
🧰 Scrappy: make little apps for you and your friends via Pontus Granström
Hi! Me and John Chang have been exploring home-made software together, and we’ve created Scrappy, a tool for making little apps for just you and your friends. It’s a pretty rough prototype, but it’s real and you can try it for yourself — we wanted to contribute more than a vision statement. Very curious what you think of it!
💬 Tom Larkworthy
The advantageous that reactive programming on a reflective substrate has over mainstream testing methodologies.
Reactive Reflective Testing in Lopebook
Devlog Together
💬 Kartik Agaram
Literate Programming with a little bit of spatiality.
💬 Kartik Agaram
First draft of a complete running program. I automatically "tangle" the code from the markup to check that I didn't forget to include something.
The picture is blurry, but in practice I can zoom in and out using mouse wheel or pinch gesture.
The editing experience is terrible. All the lines are absolutely positioned and not integrated with the markup. But code is read more than it's written 😛
Thinking Together
🎥 Net Inclusion 2025: Day 2 via Isaac Carrasco-Ortiz
National Digital Inclusion Alliance's Net Inclusion 2025 conference is currently live discussing the intersection between skills using AI and general digital literacy training
💬 Marek Rogalski
Procedural Programming + 👀 + 🤏 = Block Based Programming
Functional Programming + 👀 + 🤏 = Nodes And Wires
Object-Oriented Programming + 👀 + 🤏 = ❓
I'm looking for a term that describes a class of visual environments, where behavior is organized into stateful objects, subject to direct manipulation by the user. Examples of those environments might be The Alternate Reality Kit, Automat or Scrappy. I don't think I've ever stumbled upon a term for such a class. Or maybe I'm just not well versed in visual programming nomenclature. Do you know how they're called? Or how would you call them yourself?
Content
📝 Idea: Make a Recipe from the code comments. Code recipes is a view mode… via Medet Ahmetson
I got an idea about a code view as a comment lines. Just sharing, might hope someone to grab and build his next AI startup:
Code recipes is a view mode in your editor to read it.
In code recipe mode, instead seeing a programming language grammar words, we see the comment line for each programming language command. For example, can you understand what does following piece of code do?
But, in code editor mode, I would read the code piece as the bullet points: - Convert source code into ontological json data. Ontological json data is called 'contents'. // ...this.identifyContent(... - content is created, lets create its restful api // ...PageLevel.rest... - Re-identify page-rest if extensions ask for. // ...extension.afterPageRestCreation(.. - to make CSS Selector 'module > .page-content', so lets find module in reflect object tree // ...rest.get(..moduleURL...)... - make the branch as a sub-branch of the reflect. // pageRest.setRootNode(moduleNode) - keep alive the page rest object, so that reflect rest could refer to it. // _pageRests[moduleURL] = pageRest
In above list, instead the code, we see the comment lines. And instead comments we see highlighted pieces in the code line. The comment with the highlighted code pieces should be in grey, although I didn't know how to change font colour in LinkedIn. And that code is interactive, clicking on the highlighted codes will expand it or redirect the user to the whole line.
This mode is now possible with the LLMs. I as a developer write the comments on the complex parts, or in necessary parts. Often intentionally not putting comments on the code lines that I think are self explanatory, there comments are actually distracting and irritating. But now, LLMs could do really well about describing the command lines. You could highlight for the AI the parts, that are the main focus of the code piece. And for the readers as well. :)
I also think, maybe add some emojis or smileys next to the recipe code views, so its easier and enjoyable to do the most hated thing: to read someone else's code.
The code recipe isn't good when debugging code errors, when you need to optimize or write the code piece itself. But if you want to understand the code at the architectural, business flow level through the code, for refactoring or for modification, then code recipe is another nice-to-use way. :) I would be glad to see it.
🎙️ Lu Wilson on Art of Creative Coding by The Orthogonal Bet via Konrad Hinsen
Nice podcast episode with Lu Wilson:
In this episode of The Orthogonal Bet, host Samuel Arbesman speaks with Lu Wilson, a programmer and creative coder who also works as a software engineer at tldraw, a Lux Capital portfolio company. Lu’s creative work is broad, strange, and delightful in all the best ways—perhaps best exemplified by the Todepond videos, a mindbending series that reimagines computing through playful, experimental lenses.Together, Samuel and Lu explore the world of Todepond, the ethos of creative coding, and Lu’s unconventional path through education. Their conversation spans topics like cellular automata, the programming language Logo, the history of computing, and the evolving role of artificial intelligence. They also dive into Lu’s work at tldraw, collaborative software, and the importance of cultivating community in tech.
🎥 ESP32 Composite Video via Paul Tarvydas
This might be of interest to anyone with a hardware bent. One of the comments below it is: "... The animated explanation of the tv lines and timing are the best i have ever seen. ..."
👨🏽💻 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