Stories by the creators of Glamorous Toolkit and Moldable Development.
An exercise of creating multiple sprites out of a given picture. The exercise shows how we can mold the environment in different ways along the way.
In Pharo, some whileTrue: messages sends are inlined, and some are not. How do we find those that are not and how can we distinguish between them? And what can we learn by doing that?
A little while ago Mariano Guerra asked whether our work at feenk belongs in the space between academia and industry. Soon thereafter we found ourselves in a two-hour long conversation that touched on our motivation, how we work and the thinking behind Moldable Development and Glamorous Toolkit.
Until now, Glamorous Toolkit worked in a single image running on one processor. This was fine until we worked on figuring out what Moldable Development is, but now want to benefit from the multiple processors from our machines. That is why we are introducing support for parallel computations in Glamorous Toolkit.
How do you keep documentation in sync with the code? How do you steer agile architecture? And how do you do that without reading code?
You'll often hear us say that developers today typically spend 50% or more on code reading. Why do we say that?
We made the Glamorous Toolkit repositories rely on main instead of the master branch.
More than a decade ago, we set out to make the inside of software systems explainable. We started from the observation that software engineering is primarily a decision making activity about lots of ever changing data points represented in code and other artifacts. We conjectured that tools are essential in this endeavor but for them to be effective they have to be adaptable to the context of each single development problem. They have to be moldable.
Want to run Glamorous Toolkit on virtual Linux systems? Our community figured it out.
Carlos Lopez is a developer. He started to work with Glamorous Toolkit recently. He used it for reasoning about a database he did not know. Here is the description of his experience in his own words.
What does it mean when we say that developers spend most of their time figuring the system out? Why is it important? And how else could we look at this problem?
We untangle your software legacy crises. How? Take a tour guided by Wardley maps.
In this session Tudor Girba answers questions from Jacob Goodman and provides a guided tour.
How can we solve real problems without reading code? Through custom analyses.
We started a new video series entitled The Hitchhiker's Guide to the Glamorous World in which we have conversations with newcomers to Glamorous Toolkit.
Glamorous Toolkit Live #2 is now available. It's about how we use the inspector to reason about a REST API.
Glamorous Toolkit Live #3 is here. We covered example-driven development.
At IDE Summit 2020, I talked about moldable development and how we should not read code. It appeared to be at least intriguing, if not outright contrarian.
Creating a standalone app based on Glamorous Toolkit is as simple as opening an application specific window and closing the GT window. This can be achieved in just a few steps.
I had the pleasure of giving a lecture on Moldable Development as part of the Software Modeling and Analysis course from the University of Bern. This was exciting because this is the very first university course that relies on Glamorous Toolkit.
Everything can be customized in Glamorous Toolkit, including the home tab. Learn how.
I had the pleasure of giving an interactive session for the strumenta.community about how Glamorous Toolkit is built as a language made out of interactive and visual operators.
A screenshot rich tutorial on how to use Git from Glamorous Toolkit.
Episode 193 of the Greater than Code podcast (1h13m) features a conversation with Tudor Girba covering a wide spectrum of subjects ranging from optimizing for happiness to the power of storytelling and our privilege and responsibility as developers.
One of the first question people ask when starting with Glamorous Toolkit concerns the list of editor shortcuts. Indeed, these shortcuts are not yet visible in the user interface. Still, we should be able to learn these shortcuts from the system itself.
Over the past several weeks we spent a significant amount of effort on improving performance. The work affected the whole stack, and now we have results to show for our effort.
A short overview of how to edit and manipulate documents with Documenter.
In this article we explore how code comments can become a live wiki if we rely on interactive notebooks to document our systems directly inside the IDE.
Glamorous Toolkit is built in Pharo, and it enables people to work with Pharo systems. Nevertheless, its goal is distinct from that of Pharo and so is its realization.