Speaker @onierstrasz.bsky.social shared a series of case studies and illustrate a number of key patterns behind #MoldableDevelopment on the #YOW24 stage.
👀 Watch it here: youtu.be/F_-z0aC7Pnk?...
Custom tools for each development problem.
#MoldableDevelopment
You might be looking for #MoldableDevelopment.
Take a look at gtoolkit.com.
Of course, the goal is reasoning, but developers read as a way to get informed. This is manual and occupies the largest part of the budget.
We can optimize it significantly through custom tools that summarize the system for each problem (not AI). It’s called #MoldableDevelopment.
Developers read code to understand enough to know how to change the system. From this perspective, reading is a way of extracting information from the system. But it's also the most manual way in which we can do that.
We can do better. Through custom tools. We call this #MoldableDevelopment
Dear new and old followers,
I am talking quite a bit about making systems explainable through #MoldableDevelopment. This is a new way of programming and I am still searching for the effective narratives.
To make the exercise more interesting for everyone, please ask questions. I will address them.
A live example of relying on #MoldableDevelopment to speed up debugging 👇
#MoldableDevelopment is a way of programming through thousands of custom tools ... per system.
"How is this going to help me?"
Watch the rest of the conversation with @swardley.bsky.social here:
youtu.be/abArhHOwdEc?...
Why is #GToolkit built in Smalltalk?
Why should one try to use it?
And is #MoldableDevelopment a convincing story?
I tried to address these questions in the conversation below 👇.
Feel free to ask more questions. I am ready to answer 🧑💻.
I am glad you find it interesting (because it really is :)).
That talk does not touch on implications of #MoldableDevelopment to teaching and onboarding, but there are such implications.
Please ask questions. I am here to provide more details.
This thread summarizes the gist of #MoldableDevelopment so crisply!
I love it.
What other way?
Well, as code is data too, we can build tools that extract the information we care about from it. And because systems are highly contextual, we need custom tools, too.
Ok, now take a few more steps and you get to #MoldableDevelopment.
4/
The recent changes in #BlueSky impacted the client code a little.
Eg, here is a debugger due to rendering a post with a video. As "app.bsky.embed.video" is a new type, we need to implement the visual element creation.
But first, we extend the inspector of the with a preview..
#MoldableDevelopment
"What is #MoldableDevelopment?"
I thought you'd never ask. But that'd be Ok too, as I'd tell you anyway :).
Moldable Development is a way of programming through custom tools. For every development problem we build tools through which we can understand that problem.
I know it sounds funny.
2/
Quite a few new followers over the past couple of days. Welcome!
I talk a lot about making systems explainable and the implications of doing so. This is my interest and central to my work at feenk, where we modernize legacy systems through #MoldableDevelopment.
1/
After working with it for a while, we found that hiding parts of the code that are less relevant for the main flow works really nicely.
But we were not entirely satisfied. We still wanted to know exactly what will get hidden before hiding. So, now we can see it.
#MoldableDevelopment with #GToolkit
One company that is transitioning some hundred programmers to adopt #MoldableDevelopment already has a few thousand custom tools specific to their system. Within a year or two, counting custom tools will need 5 digits. Getting to observe this up close is such a treat.
I do :).
My colleagues and I invented #MoldableDevelopment, a way of programming through custom tools. It essentially replaces most code reading (it’s not AI).
We are building gtoolkit.com (free and open source), a moldable development environment, to show how it works in practice.
Moldable exceptions allow you to associate multiple domain-specific views and actions to exceptions in the debugger. You can always switch back to the generic, stack-oriented view if you like.
doi.org/10.1145/3689...
#MoldableDevelopment