reponse to: Tools Shape Our Products by Boris Müller

Published on –

tl;dr – A quick response to Boris Müller and his post Tools Shape Our Products and why I think he is exaggerating the state of our tools to make his point.


Hi Boris, in your article Tools Shape Our Products you argue that the code editor is this arcane empty text field we are staring at when coding. In my opinion you are exaggerating (maybe to make your point?).

When I open a Terminal. It does not look like this anymore:

An image of MacOS Terminal with bash prompt loaded
An image of MacOS Terminal with bash prompt loaded

It looks more like this:

An image of MacOS Terminal with iTerm2 and fish shell loaded
An image of MacOS Terminal with iTerm2 and fish shell loaded

And also the editor. We are not using the plainest of plain text.

An image of an empty text editor with the hello world in JavaScript
An image of an empty text editor with the hello world in JavaScript

It is actually more like this.

An image of VSCode with debugger and chat open
An image of VSCode with debugger and chat open

There is so much information and tooling to make my life easier. Debuggers, Breakpoints, Linters, Code Formatters, Static Typing, Code Generators. The list goes on. Even the color of the words I type contain information about what I am doing. when I type the application suggest what I could type next based on context.

But I get your point.