Future of Coding Weekly 2023/01 Week 5

[marianoguerra]

• [x] Change Month and Week Number

• [x] focWeekExport "2023-01-19" "2023-01-26"

• [x] Update Search Index

• [x] Download New Attachments

• [x] Update links

• [x] Check that comment links work (push weekly dump with channel summaries)

• [x] Check to mention right person for moved messages

• [x] Summary

• [x] Hashtags

• [x] Set title in newsletter

• https://tinyletter.com/

• https://tinyletter.com/marianoguerra/letters/

• http://localhost:8000/history/

• https://marianoguerra.github.io/future-of-coding-weekly/

• https://stackedit.io/app#

[marianoguerra]

🪜 Gradual Languages 🧫 Coding Generative Interactive Systems 🧠 History of Tools for Thought 🦥 Lazy User Interfaces

Our Work

📝 Hedy: A Gradual Language for Programming Education via Joe Nash

🧵 conversation

We have quite a FoC relevant edition of Papers We Love Education this month: we’ll be discussing “Hedy: A Gradual Language for Programming Education” with Professor Felienne Hermans! Thursday 26th at 6pm CET, all the info here: github.com/papers-we-love/edu/discussions/11

For those not familiar with Hedy: hedycode.com

[marianoguerra]

🐦 Tweet from @jimmeyer via Jim Meyer

🧵 conversation

The code engine in Henosia can now interact with Chrome's own debugger, including any local variables used at the breakpoint.

It's an internal tool for now to debug the code engine. Might be useful for hybrid designers though 😁

Details in this twitter post.

🎥 Henosia Breakpoint Locals

[marianoguerra]

Thinking Together

💬 Nick Arner

🧵 conversation

Does anyone have any resources they’d recommend for learning about Rust/WASM?

[marianoguerra]

Content

📝 AI-powered low-code platform by example — how to use chatGPT to abstract from domain languages :rocket: via Jarno Montonen

🧵 conversation

ChatGPT as a natural language abstraction for DSLs?

[marianoguerra]

📝 the Noosphere Discord via Kartik Agaram

🧵 conversation

A couple of links from the Noosphere Discord, just because sharing links is how I add them to my brain:

• Jerry's Brain
• The map room is a physical room-size wiki for collaboration from the 1950s

[marianoguerra]

📝 2023 Rough Questions via Mariano Guerra

🧵 conversation

Two overarching questions:

• How can we reason about notations/interfaces/editors? So that:

• We can construct correct interfaces

• We can distill what we are trying to say into more direct representations

• We can explore the consequences of what we are trying to say more directly

• How can we construct more direct analogies for computation?

[marianoguerra]

🎥 "Ceptre: A Language for Modeling Generative Interactive Systems" by Chris Martens via Nilesh Trivedi

🧵 conversation

[marianoguerra]

🐦 Tweet from @haxor via Mariano Guerra

🧵 conversation

Are you interested in trying the new functional programming language that I've been developing? Sign up for an early preview

Here's a small glimpse of the language

🐦 Brett Slatkin: Are you interested in trying the new functional programming language that I've been developing? Sign up here for an early preview: https://quil.la/2X2LS I'd love some patient feedback before I release it more widely. Thank you in advance!

🐦 Brett Slatkin: Today's functional programming amusement: Mandelbrot set

[marianoguerra]

💻 QueryStorm | C# in Excel - QueryStorm via Riley Stewart

🧵 conversation

A fairly complete IDE that can work directly with Excel data via LINQ, with extension capabilities of its own to boot.

Show HN

[marianoguerra]

📝 Natural language is the lazy user interface via Mariano Guerra

🧵 conversation

" Just slap a textbox on it!"

The tyranny of the blank textbox is real.

"people are bad at words"

[marianoguerra]

🎥 Meeting: Tools for Thought Rocks - Mark Bernstein via Jack Rusher

🧵 conversation

Mark Bernstein (who has been doing Tools for Thought stuff for decades, and has had a product in that space since 2001) gives a very rich history of TfT in the hypertext/notetaking vein

[marianoguerra]

Devlog Together

📝 Manual Tests via Kartik Agaram

🧵 conversation

Today I gave each app a default map for its code, so that people get a better initial experience when connecting the driver to it, rather than the blank canvas they've been faced with so far.

Initialization is one of the categories of semantics that's hard to write tests for. What should happen when a config file is present. The driver maintains separate configs for each app it knows about, so it needs to handle the very first app vs first view of a new app. What if the app has no default map. Etc., etc.

Anyways, I ended up touching git.sr.ht/~akkartik/driver.love/tree/main/item/Manual_tests.md after a while.

[marianoguerra]

💬 Lu Wilson

🧵 conversation

a snippet from my weekly blog this week

(pretty niche tode/bret lore content)

[marianoguerra]

Present of Coding

📢 Future of Coding Newsletter Archive and RSS Feed via Mariano Guerra

🧵 conversation

The future of coding newsletter now owns its small plot of land on the internet: history.futureofcoding.org/newsletter

And because of that it now has an RSS feed: history.futureofcoding.org/newsletter/rss.xml