#moldabledevelopment search results
Explaining #COBOL can be playful. Here, we expand a reference to a screen in a to reveal the screen preview right in the editor of the COBOL source code. #MoldableDevelopment
But the most interesting bit is how the custom debugger is defined: through an inspector extension of the exception. Here, we see the same view both in the debugger and in the inspector of the exception. #MoldableDevelopment 3/
Embracing #MoldableDevelopment with our ATS Contestia 🛠️ Started by making explainable a software feature (application recovery), and ended up crafting a visual tool. Now, complex JSON mapping is just a matter of connecting dots. No tech expertise needed – just draw and define.
Just compare that with the generic debugger view. Seeing it through a custom view, the error becomes delicious. #MoldableDevelopment 2/
#MoldableDevelopment is a way of programming through custom tools. We approach every development problem through a custom tool built specifically for that problem. This often leads to thousands of little tools per system... "Thousands of tools? But is this not expensive?" Well,…
How do you explore Ruby on Rails routes? How about: - Left pane: all API entry points in a searchable list. - Right pane: for a given entry point, we see the routes definitions linked with the corresponding controller implementations. #MoldableDevelopment with #GToolkit
The key to making #MoldableDevelopment practical: composable micro tools. Here is how a typical inspection scene is composed in #GToolkit. The scene shows a flow with two panes. The first pane holds an inspector in which we execute a script that spawns another inspector. 1/
I often tend to talk about #MoldableDevelopment in too abstract terms. I did it in a call just now. It's not the most useful inclination. That's when I wish I had @swardley next to me to bring me down to earth and show concrete examples. Like he did in this chat when he had me…
When looking at a system developed following #MoldableDevelopment, people's attention is attracted by the existing tools. But those are secondary. The most important part is the act of creating a new tool. Take a look at the attached picture. It's a profiler tool that is…
And here we rename a message. In both cases the refactorings affect the snippet from the documentation. And all interactions are seamlessly integrated. #MoldableDevelopment 2/
As we are in a #MoldableDevelopment environment, the exception can also customize the preview. For example, here we see an equality assertion failure showing a diff. Of course, you can open the full debugger, but often a preview is enough feedback. 3/
Going from a #COBOL screen to the flow of programs and screens it can lead to. #MoldableDevelopment with #GToolkit
@swardley summarizing his #MoldableDevelopment journey: "This is impressive ... very, very impressive" Watch the full conversation between @swardley and @girba here: youtube.com/watch?v=abArhH…
When running an example (or a test) in #GToolkit we can see the result to the right. If the execution leads to a failure, we get to see the failure. Without a debugger. For example, here we see an off-by-one error in the assertion. #MoldableDevelopment
We can now extend the debugger that is embedded in a Pharo snippet. For example, here we get a quick feedback through a diff view of a failure exception right in the snippet. #MoldableDevelopment with #GToolkit
@girba: We are so used to the idea that tools will be provided to us ... what if we get to create our own tools? That's the essence of #MoldableDevelopment. @swardley: How long does it take to build such a tool? Find the answer in the full conversation: youtube.com/watch?v=abArhH…
Oscar Nierstrasz 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?si…
youtube.com
YouTube
Moldable Development in Practice — Patterns for Legacy Modernization...
GToolkit es nuestro ambiente de desarrollo preferido. Nos permite practicar #MoldableDevelopment para crear con relativamente poco esfuerzo herramientas específicas del dominio o, como en este caso, entornos dedicados completamente nuevos.
DynaClassroom was built on #GToolkit, the moldable development environment based on #PharoSmalltalk. 🚀 Its flexibility allows the creation of tailored environments like DynaClassroom, a collaborative educational space powered by tangible interfaces and augmented reality.
I often tend to talk about #MoldableDevelopment in too abstract terms. I did it in a call just now. It's not the most useful inclination. That's when I wish I had @swardley next to me to bring me down to earth and show concrete examples. Like he did in this chat when he had me…
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 compact narratives. If you are interested to learn how it can apply your specific context (technology, domain,…
#MoldableDevelopment is about programming through custom tools. Little tools, often in the shape of object views. The key to making this practical is to decrease the cost of creating those custom views. While we already could create them in minutes, we've always been interested…
In our quest to make creating views more and more inexpensive, we now got to the point in which we can create custom views based on the object obtained from executing a snippet in the contextual playground from an inspector. Sounds complicated? It's really not. Just take a look.
#MoldableDevelopment denotes a way of programming through custom tools. To make it practical, we need to make creating these tools be highly inexpensive. It's not enough for tools to be extensible, the ability to extend should be seamless. This is a research problem. We first…
Moldable exceptions are all about extending the debugger by extending the exceptions' inspector. How does that work? Watch @onierstrasz's talk at Onward 2024: youtube.com/live/-Br66SUjs…
youtube.com
YouTube
[SPLASH'24] Pacific - Onward! (Oct 23th)
We're excited to welcome Oscar Nierstrasz to the #YOW24 stage to share a series of case studies and illustrate a number of key patterns behind #MoldableDevelopment. Get tickets here: 📍 MEL yowcon.com/melbourne-2024 📍 BNE yowcon.com/brisbane-2024 📍 SYD yowcon.com/sydney-2024
If you are a technical person and want to convince your business manager to invest in better skills and tools for legacy modernization, start from the business perspective. Say you looked into #MoldableDevelopment and are now convinced that you need to invest in it because it's…
#MoldableDevelopment is a way of programming through custom tools. We approach every development problem through a custom tool built specifically for that problem. This often leads to thousands of little tools per system... "Thousands of tools? But is this not expensive?" Well,…
#GToolkit shows that #MoldableDevelopment can be practical. It comes both with abilities to create custom tools and, perhaps more importantly, it comes many examples of such concrete custom tools. Most prominent, of course, are extensions for and with Pharo code. But what about…
#GToolkit can be integrated in many different ways with other systems or runtimes. Watch @Chis_Andrei showing examples of such integrations. youtu.be/kn9NmvBjgS8?si…
youtube.com
YouTube
Glamorous Toolkit
Recently, we focused our attention on Moldable Debugging. Here is @Chis_Andrei giving a tour of what we mean by it. youtu.be/jAO0lZ6tNKU?si… #MoldableDevelopment with #GToolkit
youtube.com
YouTube
Moldable Debugging
moldable dev with clerk and clojure. a triple @usenextjournal threat feat @elliotokay @mkvlr and @unkai
Explaining #COBOL can be playful. Here, we expand a reference to a screen in a to reveal the screen preview right in the editor of the COBOL source code. #MoldableDevelopment
We use #MoldableDevelopment. We replace the activity of reading code through custom tools built specifically for each development. For a system considered legacy this can lead to thousands of little tools. These tools generate views that allow us to build mental models much…
Going from a #COBOL screen to the flow of programs and screens it can lead to. #MoldableDevelopment with #GToolkit
When looking at a system developed following #MoldableDevelopment, people's attention is attracted by the existing tools. But those are secondary. The most important part is the act of creating a new tool. Take a look at the attached picture. It's a profiler tool that is…
We help organizations solve their hardest problems: We modernize legacy systems. We use a mix of technology and business assessment, technology optimization, reverse engineering and migration. Our not so secret ingredients? #MoldableDevelopment combined with #WardleyMapping.
However, if your focus is on digital transformation then I'd suggest talking to @esynergy_ - esynergy.co.uk - they can drag me in when needed. If your focus is on super hard problems like legacy then I'd suggest talking to @feenkcom - feenk.com
Something went wrong.
Something went wrong.
United States Trends
- 1. Giants 63.5K posts
- 2. Bills 134K posts
- 3. Bears 56.2K posts
- 4. Caleb 45.7K posts
- 5. Dolphins 30.5K posts
- 6. Dart 24.3K posts
- 7. Daboll 9,687 posts
- 8. Josh Allen 14.2K posts
- 9. Russell Wilson 3,666 posts
- 10. Jags 6,027 posts
- 11. Texans 35.9K posts
- 12. Browns 35.3K posts
- 13. Ravens 35.3K posts
- 14. Patriots 99.5K posts
- 15. Henderson 15.6K posts
- 16. Trevor Lawrence 2,169 posts
- 17. Drake Maye 14.1K posts
- 18. Bryce 14.9K posts
- 19. Vikings 28.9K posts
- 20. JJ McCarthy 4,481 posts