Welcome to our newest channel, Two Minute Week. Once per week, post a video overview of the latest progress in your Future of Coding project. You can upload your videos to YouTube and link them here, or compress the video yourself and post it directly to the Slack (like I did, since YouTube's compression destroyed my dot grid). Further explanation and recording tips are here: https://futureofcoding.org/two-minute-week Let's take this first week to give context. Looking forward to seeing your projects! [Let's get a few of these videos posted to serve as examples, and then I'll bulk-add all our Slack members and make this one of the default channels]

A bit about progress on generic tree editor. In my last demo [1] I forgot to show how transition from editing blob to editing a tree works. This video fixes that. Currently I am designing tree storage API and covering it with tests. Source code is not public yet. I plan to open it when editor reaches usable state. [1]

It was a busy week so I went over by 20 seconds 😄

Since this was mostly intro, it was hard to fit into 2 minutes and 40 Meg, especially given the graphical nature! I had a nice script worked up and realised it was 4 minutes long 🙂 Apologies, I'm a complete beginner at video capturing, etc. I missed a few things, but I guess I can gradually work them in as I do more updates....

Here’s my 2 minutes intro of Lamdu!

So, it may be just me being old and slow, but .. 1. I've not been following #feedback videos reliably, and some of the above seem to assume I/we are up to speed with your work and know what you're doing already; maybe start from the beginning? 2. I know it's only 2 minutes, but you've got 52 weeks a year to play with, so how about slowing down a bit - or maybe over-running to 2:59 ;o] - so we can all have a chance to actually grasp what's going on in your show? On the plus side, you've got my attention, @Ivan Reese - great idea! 😄

Edward de Jong  [7:03 PM] Per Ivan's suggestion for making weekly progress videos, I have made a 2 minute video on Beads, showing off the beginnings of the IDE that will allow the programmer to use a graphical user interface to construct part of the code.  I had originally intended that Beads would be a purely textual language, but customer feedback is overwhelmingly requesting graphical aids and high interactivity. Certainly, for the graphical parts of coding, and that is a lot of the process, it will be much easier than typing. The key advantage of graphical interfaces is that you can constrain the visibility and presentation of options so that it is nearly impossible to have an invalid state. Textual coding has lots of tiny typographical errors, and that frustrates people. As i progress on this process of graphicalization i will find out how far you can actually take a language that is very Pythonic into this space. The output of the IDE is the canonical text form of the language, which will allow programs last a lot longer. Different IDE's will spring up over time, and the internal form of a document from an IDE is highly IDE specific. Just for "diff" reasons you need a text form that can be compared and updated. So a graphical system that stores into text format is a very sound idea. I know that the Luna people are doing a similar thing. Anyway please let me know if the video is tolerable. It seems a little fuzzy; i uploaded it at 720p but maybe not enough pixels. The IDE for Beads is written in itself, and shows very good compactness as it is only 15k words (approx 4000 lines) so far.

I think this 2mw thing is going to make it much easier to understand what everybody is doing and what's similar or not, and perhaps increase or ability to cross pollinate good ideas and approaches. I'm excited to see all these coming in! My project is moving like molasses and not very demo-able, but I've been considering drawing some (very rough) diagrams to show my vision, and how I plan to make it work.

Mu: the movie

luckily I checked this before sending the newsletter 🙂 I was thinking about the "archival properties" of posting the videos directly to slack, I guess they will eventually be removed? any reason why not post them on youtube? maybe it's possible to upload directly to the internet archive or some alternative like https://peertube.co.uk/ ?

This took a while, but I just finished my entry, pretty happy with how it turned out for my first time actually editing a video! This video is purely an introduction, next week there will probably be some more devlog-y content.

Undo & IO History, Storybook Async Examples, Multiple Output Types, Source/Output Type on Paths, Propagate Var Type Change and Eviction:

Lamdu’s second 2 minute video: this time focusing on localization, which I haven’t yet made any video or post about

Week 2 Video of my live coding project overview, focusing on the Synthesizer currently. I'm new to audio programming, so this has been an interesting journey.

I probably should have done this one first as it sets the stage, but heck it is only 2 minutes so hopefully not too boring!

Instadeq Week in Two Minutes #3: Generalized IO UI & history, Selected output on charts, Keep UI state on IO update, Remove cycles in sankey chart, Providers and more

Third update for my Live Coding project - still focusing on the sythesizer creation.

Here is a follow up on the Beads layout system. Beads has a very unique layout system that is slightly more advanced than the Apple struts and springs system used in XCode. You design your layout by starting with the full screen rectangle, and subdividing it into pieces. Each chunk can be further subdivided. It has pre-programmed the commonly used types of decompositions: plain, vertical slice, horizontal slice, vertical scrolling, 2D grid, and a farily elaborate report writer for those who need to produce printed reports in the classic style. Since the layout system is in the language itself, you can use variables, IF statements, and subroutines in the layout portion, unlike CSS which hampers you great. Another huge advantage over CSS is that Beads uses explicit whitespace so placement of items is 100% predictable and repeatable, unlike CSS which on a small typo can scramble your page. Building a complex product by gradual refinement is the methodology you use in Beads; always proceeding from a working standpoint, and adding in detail.

Hi, here's a short introduction video about my flow-based-programming project: . In the near future I'll upload more videos to talk and show more deeply about the project, but I hope that this video already gives you an idea of what I am creating

alv week 2: (I'm clearly not able to keep up with a weekly rhythmn with my current workflow, but I'll keep experimenting with what I want out of this :)

I've had my hands full with other stuff for the past few weeks, so Hest progress has been slow (as seems to be my lot, sadly). I guess this is what you get when you start messing with the timeline. Don't mess with the timeline!

This is a programmable Gantt chart tool I've been working on. I just released it as a beta to my users today. I'm expecting them to find the formulas very intimidating (although most can use basic excel) but I'll let you know what their feedback is next week! Couldn't fit in the canvassy graphical interface but perhaps another time.

Instadeq Week in Two Minutes #4: Providers, a unified protocol to consume batch/streaming data from external systems

Sorry i posted only a partially uploaded file. This is a corrected version. Thanks to @wtaysom for catching that. Here is a short video showing how to build a temperature control. You proceed directly from a sketch to a final shippable product using Beads, with no prototyping necessary. A lot of wasted work happens in our industry by using wireframing tools that can't be executed. You are better off with a crude-looking working product than a fake but pretty demo. It saves time, when the final shapes are all worked out from the running product, then you apply the final polish. Beads is rare among languages in that it carries at runtime physical units of measurement (by creating a new datatype which carries the unit exponent array and magnitude of the value), and has pre-programmed all the common conversions, such as degrees Kelvin to degrees Centigrade, etc. In this example i also show how you can have two interlinked controls on the screen, and whichever one changes the model the other control tracks its value, all without any additional code.

It was a slow week this week. I found I didn't have my usual energy for after-hours projects, and I needed a rest this weekend. As is usually the case in such circumstances, I spent some time cleaning up code and refactoring - I often find such activities help keep the project momentum up, while requiring less time & effort. I have spent some time recently thinking about how to manage note events and synchronize beats & timing. It seems like a good idea to integrate Ableton Link at the outset, because on some level it helps drive towards a cleaner management of such things. It is also really nice to have a built in way for musicians to work together with a live coder; a USP perhaps. I don't say it in the video, but the tempo of the audio is being controlled using the iPad drumming app, which the sample app and the synth are aligning with. Another piece of ongoing work is the integration of Orca-c which I've shown previously. This is an embedded Orca inside my text editor and forms one way in which a coder can drive the synthesizer (and later, I hope, some geometry/graphics too). Orca isn't the only way I intend to generate music, but it represents a relatively easier integration than music languages, etc. As I say in the video, there is still work to do to complete this feature.

Hi, in this very short 2nd introduction video I'll show you how to create a body mass index calculator with my flow-editor step by step. It also shows (very briefly) the new debug functionality to help "follow" the flow.

Instadeq Week in Two Minutes #5: Form builder cell to create forms that emit output on change and submit, register and reload providers dynamically and allow services to specify configuration parameters that appear in the UI: