The recent conversations about #ToolsForThought tend to revolve around note taking. Indeed, a note can be a representation of thought...
2/
2/
But, a tweet can also be a representation of thought.
3/
https://twitter.com/girba/status/1465740842631675918?s=20
3/
And, a diagram can be a representation of thought, too.
Like a #WardleyMap, for example.
4/
Like a #WardleyMap, for example.
https://twitter.com/feenkcom/status/1405241536963547139?s=20
4/
A diagram relies on a different representation. Yet, to make it integral part of the overall graph, it should blend with the rest of the representations.
There never is a single representation of thought, and the environment should embrace this.
5/
There never is a single representation of thought, and the environment should embrace this.
https://twitter.com/feenkcom/status/1405241698830127108?s=20
5/
Now, code is also a representation of thought. And so is the result of executing that code.
For example, here we have a piece of code inside notes. Executing it shows the result through a contextual view in the inspector.
(Yeah, like a notebook. Only different. And better)
6/
For example, here we have a piece of code inside notes. Executing it shows the result through a contextual view in the inspector.
(Yeah, like a notebook. Only different. And better)
6/
Talking about objects: What about the structure of the note itself. Should that not be a relevant subject of inquiry?
Of course, it should be.
For example, this is how our page looks like behind the scene.
7/
Of course, it should be.
For example, this is how our page looks like behind the scene.
7/
And what about connections?
Well, if we can get to the objects of our notes, we can also visualize them.
8/
Well, if we can get to the objects of our notes, we can also visualize them.
8/
Let's stop a bit.
We just went a couple of meta-levels deep in the same environment: we are looking at an object (1) representing visually the connections between our notes (2).
And if we want to, we can highlight the current page within that whole graph, too.
9/
We just went a couple of meta-levels deep in the same environment: we are looking at an object (1) representing visually the connections between our notes (2).
And if we want to, we can highlight the current page within that whole graph, too.
9/
And because the visualization is showing us the objects that represent notes, inspecting one of these objects shows us the editor that we used to type that content with.
10/
10/
So what?
Humor me a little longer.
If we can visualize notes, can't we visualize code, too? Sure we can.
Here we see a visualization of dependencies between #GToolkit components. Selecting a component reveals the code specification behind it.
11/
Humor me a little longer.
If we can visualize notes, can't we visualize code, too? Sure we can.
Here we see a visualization of dependencies between #GToolkit components. Selecting a component reveals the code specification behind it.
11/
What do you know! Working with notes and code can be, essentially, the same.
Note taking does not have to be distinct from the programming experience. In fact, when they are not distinct, we get to express thoughts in new ways.
12/
Note taking does not have to be distinct from the programming experience. In fact, when they are not distinct, we get to express thoughts in new ways.
12/
How do you get there?
Adding programmability on top of note taking will only lead to a broken system.
Programmability has to be served first because that's what makes everything inside a computer.
That's why #MoldableDevelopment is important.
13/
Adding programmability on top of note taking will only lead to a broken system.
Programmability has to be served first because that's what makes everything inside a computer.
That's why #MoldableDevelopment is important.
https://twitter.com/girba/status/1381855442159165442?s=20
13/
#MoldableDevelopment started from a simple question: can we significantly affect the way we work with the smallest piece in a system? A single object.
It turns out that we can do that by inspecting through the lens of different contextual views.
14/
It turns out that we can do that by inspecting through the lens of different contextual views.
https://twitter.com/girba/status/1381855451285950464?s=20
14/
This little change of perspective led to several surprising findings. For example, we knew that it is immediately useful for reasoning about existing systems, but it was surprising to see how creating views changes how we design systems, too.
15/
https://twitter.com/girba/status/1147611789342969856?s=20
15/
This exploration was easy in Smalltalk, but it was still not obvious. A decade later, we are still discovering new angles.
We recently realized that we can replace the Playground (a REPL) with a rich multi-language environment in which note taking is just another language.
16/
We recently realized that we can replace the Playground (a REPL) with a rich multi-language environment in which note taking is just another language.
16/
The benefits are manyfold. For one, we can interweave narratives and code for many purposes. For example, #GToolkit ships with a live book describing it.
17/
https://twitter.com/feenkcom/status/1405241273313902599?s=20
17/
Another implication is how the environment can address non-technical people. When the inside of the system is explainable, it invites explorations. If given the chance, people want to learn about their system. This leads to a new feedback loop, too.
18/
https://twitter.com/girba/status/1381856008872587265?s=20
18/
Taken to the extreme, it leads to a fresh take on personal computing in which the individual can mold the experience dynamically. Actually, this is not necessarily new, as personal computing was always meant to be personal. We just forgot it.
19/
https://twitter.com/girba/status/1394214379655208962?s=20
19/
The tools we expose ourselves to, shape the way we are going to decompose the problem in front of us. They shape our thoughts.
But, we are not entirely powerless. We only have to choose our tools carefully.
We can start by asking: what thought?
20/
But, we are not entirely powerless. We only have to choose our tools carefully.
We can start by asking: what thought?
20/
I believe the exploration of what's possible is still in its infancy. We build #GToolkit to explore and summarize interesting questions we can ask as a collective. Because this journey requires a global conversation.
So, join us. Let's talk.
discord.gg/FTJr9gP
21/
So, join us. Let's talk.
discord.gg/FTJr9gP
21/
• • •
Missing some Tweet in this thread? You can try to
force a refresh
