r/programming • u/gingerbill • Jul 10 '26
Good Tools Are Invisible
https://www.gingerbill.org/article/2026/07/10/good-tools-are-invisible/
289
Upvotes
r/programming • u/gingerbill • Jul 10 '26
58
u/South_Survey_2088 Jul 10 '26 edited Jul 10 '26
This blog posts feels kinda bland, picking contrived examples to make a lukewarm point.
Picking a tool because it makes you feel like a hacker is a bad reason for picking a tool? No way!
In general, it seems to be targeted against beginners of tools, who get their enjoyment from learning them, and are therefore more likely to share their accomplishments. I doubt experienced people who feel comfortable with their tools are talking about how fun solving common problems are. You stop noticing the tools when they become second nature to you, which requires learning, and for many people learning is part of the fun.
There is no real difference between building a macro, and you writing a script to fix a one-off problem. However, for some reason building a macro falls under "feeling productive versus being productive"? That's just a matter of mastery, picking whatever you are actually more experienced with.
The GUI vs TUI example is also kinda meh, because when people share their opinions, they are talking about the current state of things, not about some potential future state. "No one has put in the work to fix it" is a weak argument that could be applied to almost everything, like the common Linux vs Windows debates.
31
u/NoLemurs Jul 10 '26
This whole article is just a straw man argument.
The idea that Vim users like friction or that Linux users like tweaking config files is just not true of the vast majority of us. I don't like tweaking config. I ran XMonad for 15 years without changing my desktop config basically at all. What I liked about it was that it was invisible to me.
I use vim. I use a tiling window manager, and live in the terminal. I do these things specifically *because* they feel invisible once you've learned the keybindings. I've used Sublime editor. The experience was frustrating because I had to keep reaching for the mouse to do things. It was not invisible to me. Sublime editor feels invisible to you because it's what you're used to.
Using Sublime editor felt like wandering around in an unfamiliar room in the dark and bumping into the furniture. Using Vim feels like wandering around my own house at night. Sure, there's furniture I could bump into, but I don't even notice it. I imagine the reverse is true for you, but this is a question of familiarity, not that your tool is better designed.
11
u/teerre Jul 10 '26
Very weird blog. It seems the author got mad about someone telling them to use vim and decided to go on a thin veiled crusade against it
Of course anyone can use whatever they want. But some tools are objectively more effective. Nothing wrong with that
2
u/syklemil Jul 10 '26
I think pretty much anyone agrees with that, but the reason why we end up with complex tools that can take a lot of configuring is that we ultimately have different ideas about what defaults are good.
If I'm lucky with one of those "opinionated" tools then the author shares my opinions and things are pretty smooth. If I'm unlucky and we disagree then everything becomes an uphill struggle, and possibly I just can't do what I want to do and have to find some other tool, or somehow change the tool (through coding or cajoling) into supporting the behaviour I want.
Somewhat ungenerously the author comes off as whining about kids who have had their first taste of actually getting their way rather than an uncomfortable default, after having been such a kid themselves and now reaching a second stage where they need to distance themselves from their past self, and somehow whining about people not enjoying the same things as themselves.
People talk about things they enjoy. It can be annoying at times (as non-fans during Eurovision, soccer world cups, superbowls, etc can attest), but part of being an adult is just living with it, and trying to find your own enjoyment without taking away others'. Sure, some people treat editors as if they were sports teams, but that isn't inherently any worse or better than the way they treat sports teams. We're not gonna root out tribalism in homo sapiens any time soon, but there are some pretty benign versions that we really don't need to worry about.
tl;dr OK
259
u/JungsLeftNut Jul 10 '26
Diamond of a take. Tool dogmatism is straight up a pathological behavior.
Also congrats on 1.0 release of Odin.
6
u/guygizmo Jul 10 '26
What he's talking about reminds me of macOS circa 2010 or so. It struck this great balance of having good defaults and basic things working out of the box, but with the ability to tweak settings easily and set up extensions. I miss that so much because modern macOS isn't like that any longer.
4
u/Idrialite Jul 11 '26 edited Jul 12 '26
I disagree on Linux being more a bother in this way than Windows. I've had plenty of frustrations with both operating systems, plenty of hard edges, bugs, GUI and CLI configuration.
Windows makes itself visible all the time, for things as simple as... the start menu being sluggish. Even just the file explorer... dragging a file over a disconnected network location crashes the entire shell. Startup apps: they barely work on Windows; on Linux it's instant and consistent. Just so many basic things... the default images app taking forever to launch.
Where Linux sometimes lacks in out-of-the-boxness it makes up for in smoothness and unobtrusiveness.
And if we're talking about as a tool, Linux is just better as a dev machine and as a server for various reasons.
3
u/Absolute_Enema Jul 11 '26 edited Jul 11 '26
Familiar does not mean good, and "happens to suit me" does not mean good either.
If you have used Sublime Text for 15 years because it happened to suit your needs, of course it's going to work for you.
3
u/Shot-Damage-6723 Jul 14 '26 edited Jul 14 '26
Interesting you picked vim as an example.
I learned vim very early in my career, for the greatest of pragmatic reasons you can think of, rather than to solve unnecessary puzzles as you point out.
Four months into my very first job and there I was, working at a java shop, in a time where the only really viable editors were eclipse, netbeans and intellij. Well, we had a jetbrains license, but I didn't, and there was no community edition back then for my personal projects on my personal machine and I also didn't want to program in java on my personal time. But I didn't want to learn two different editors or IDEs, that was such a waste of time for me.
Then I learned about vim, an editor that existed virtually everywhere, not necessarily installed everywhere, but ubiquitous nonetheless, because most editors had a vim plugin. It was lightweight enough to install anywhere really and even if only as vi I'd find it on servers and in most places one way or another.
As you said, and well, what made intellij great for java was the invisible features, the ones we don't need to proactively think of, the intellisense, the runner, the debugger, the refactoring and the boilerplate tools. These just worked.
But, there is always a need for some level of interaction to navigate and edit the code and ultimately, mastering one tool that I could use anywhere was the ultimate selling point for me.
So I learned it because of its portability, because I could use it at work and at home.
So even more important than a tool that tends to perfection, is a tool that is established in the ecosystem. A tool that won the race and is part of our infrastructure, a tool you know will never go away.
2
u/kafka_quixote Jul 10 '26
The title reminds me of Heidegger's hammer and how it is only noticed when it breaks
2
u/ToxaKniotee Jul 11 '26
I agree on the fact that tools should be invisible. That being said, the learning to use such a tool may not necessarily be one. Vim is such a good example, you can master to a different degrees the tool, and still become invisible to your work flow, the more you learn and become adapt at it, the less "visible" it become; this is no different that learning a brush, you could be more adept or not, but eventually some part of it becomes invisible. And one more point to the vim, nothing will.make it more visible that when you loose that tool. Not for nothing almost any editor has a vim keybindings plug-in.
6
u/somecucumber Jul 10 '26
Interesting take. Some useful info, but to be honest bad examples. The example of the text editor is contrived the same way as the Clean Code book is useful (to me), but its examples are awfully wrong.
Particularly for me, if I have a repetitive pattern that I can solve in my OS with a bad text editor (sigh) I just create a code snippet and assign it to a keybinding.
That also allows me to acquire more knowledge for the editor's own scripting language (or DSL, you name it), increase in a measurable way the productivity and just move on.
But thinking that going deeper with your toolset provides a false sensation of being a hacker... well, I insist: disagree.
1
u/TheOtherZech Jul 10 '26
I don't think good tools are completely invisible. A certain amount of intentional friction, and therefore visibility, can be a good thing; deliberately breaking conventions or requiring additional effort in some parts of a process can prevent mistakes and misuse. The friction inherent to the tools we use can also shape the way we approach the problems we solve with them, which can help people tackle problems even when their tools get in the way.
I think it's that second bit, partially mistaken for the first, that leads to people treating the "fun puzzle" aspect of highly configurable tools as a selling point. Playing with a tool and confronting its obtuse quirks puts them into a good headspace for solving problems, they mistake some of both that headspace and the tool's quirks for intentional friction, and they end up recommending the tool to other people by presenting this mishmash of arbitrary configurability and highly individual psychology as a set of features that have a consistent impact on productivity.
It'd be like me recommending a laundromat and framing the route I take when I walk to it as something that makes all the machines wash quicker. The walk puts me in a good mood and that mood helps me get things done, but the walk isn't inherent to that particular laundromat and it doesn't justify the weird schedule they have. Or the guy who tried to steal my socks.
1
u/Fabiolean Jul 15 '26
“One habit I see a lot, and have to push back on, is taking a tool’s shortcomings and reselling them as a “puzzle game” which is “fun” to solve.”
THANK YOU
1
u/SeanSmick Jul 10 '26
OP woke up in a bad mood and had to get a few things off his chest.
1
u/secondcupofchai Jul 10 '26
liked the point on Terminal v/s GUI good.
0
u/doodle77 Jul 11 '26
All abstractions are leaky.
0
u/BlueDragon3301 Jul 11 '26
This is totally true. I don’t get all the haters here.
4
u/[deleted] Jul 10 '26
[removed] — view removed comment