Top
Best
New

Posted by jxmorris12 10/28/2025

Tinkering is a way to acquire good taste(seated.ro)
470 points | 381 commentspage 3
itissid 10/29/2025|
I've spent an inordinate time tuning my home nas to what I want to do. e.g. NPM reverse proxy with all kinds of docker apps and configuring it securely made me appreciate how tough cyber security is. My latest venture was to create several docker images for whatever environment I want: VsCode Remote SSH server, a docker image with a custom LLM, sync thing for obsidian notes across all devices

My goal is to de Google with home nas hosting a bunch of services. I want to take all my Dropbox photos and recreate what Google memories does using off the shelf AI tools on my nas. Then email and finally maps with great PoI data.

Probably not all of what I did is a differentiator that put my learning beyond mediocrity. But a good yard stick is if what I built is useful to someone and even better if one would pay me for something.

BoorishBears 10/29/2025||
You don't have interesting taste if you write articles like this.

People are just figuring out taste matters for product, so at this pace in 10 years they'll figure out that having novel tastes that aren't just a distillation of the echo chamber you live in matters just as much.

doodaddy 10/29/2025||
I think there is too much associating taste with quality. We can see it in many of these comments and in the post as well:

> And what I mean by taste here is simply the honed ability to distinguish mediocrity from excellence.

And I say, maybe. But more than quality I think taste is a way to discern what’s unique and novel. In my mind it doesn’t necessarily mean that it has to be “excellent” because, as the post mentions, everyone’s “excellent” may be different.

Why do I think this distinction is important? Because if taste is about seeing the nuances that make something interesting instead of what makes it “good” then getting to good taste promotes open minded exploration (healthy exploration) over status seeking.

jongjong 10/28/2025||
I love tinkering but I'm very minimalist as far as tooling is concerned. I don't like to use too many tools. I only use tools to automate activities that I do frequently. I don't try to micromanage and automate every aspect of my existence. Some stuff is better left uncounted and unplanned.

A lot of other people who like tinkering seem to have a kind of obsession with using all the latest gadgets to solve the tiniest problems. IMO, there's a point when you're so into automation that you end up looking for problems to use your tools on. You end up introducing new problems into your life, just so you can solve them using your tool of choice. Your life becomes like a Rube Goldberg machine.

lolive 10/29/2025||
Tinkering is a very demanding activity, especially when you are total newbie at a new domain. The first steps are very intellectual-draining. [and that is probably why so few people learn new things, when adults].

Having good mentors [on Youtube, among your friends, or a vendor at a localshop] can really help you figure out things much faster, that will have taken forever to discover by yourself.

So don’t fear to ask !

submeta 10/29/2025||
Tinkering is the ultimate satisfaction of a hacker. When you love perfecting your tools, shaping your terminal, your Emacs, your Neovim, or whatever tool you use, exactly the way you want it. You spend hours doing it and feel enormous satisfaction from every small improvement.

That is exactly what a Japanese swordsmith, a chef, or a craftsman does. Perfecting their work, finding joy in refinement, and taking pride in the process itself.

I used to see tinkering as a form of procrastination. But not anymore. What does that even mean? That we should be doing something else, and devalue this activity? What if this very activity, and the results it produces, bring me deep satisfaction? In that case, it is not procrastination. It is the perfection of the art.

Johanx64 10/29/2025|
This is not what a Japanese swordsmith or any craftman does, they obsess over the end result, polishing it until it reaches perfection.

Riced out Neovim/emacs setup doesn't and hasn't ever led to quality software in any shape or form, neither it ever will.

If it did, world would be full of polished, high quality software, what instead we have is endless sea of garbage produced by these cough, cough "craftsmen" - that obsess about everything else, but the actual end product.

submeta 10/29/2025|||
Well, very valid points you made. I must admit.

Edit: But why do you believe that my super polished and streamlined WezTerm is less worth than a japanese sword? :) Which value has a perfectly made sword in a world today? Which value has a perfecly made machs tea? And other things only the maker or a few select people value?

Johanx64 10/29/2025||
> why do you believe that my super polished and streamlined WezTerm is less worth than a japanese sword?

Because people are willing to pay roughly 0$ for your riced terminal and dot files.

A polished japanese sword made by a master craftsmen on the other hand - people are willing to pay good money for.

submeta 10/29/2025||
So you think money is the indicator? I have to disappoint you: There's a ton of things that have zero monteray value, yet an enourmous value for the person who creates it. One example: Open source software. Another: Art you create for the fun of it.
Johanx64 10/29/2025||
I'm sorry to disappoint you. Money is proxy for value. Or atleast the closest thing to it.

In fact, it has so much value, that people will bend over, creep and crawl just to get it. And sell their waking hours for it.

Yes, you can have a lucky-pet-rock that you've always had with you, that holds value for anyone but you. For everyone else though - it's just a rock.

iLemming 10/29/2025|||
> Riced out Neovim/emacs setup doesn't and hasn't ever led to quality software in any shape or form, neither it ever will.

Hmm... excuse me?

Linux kernel - most contributors use vim/emacs extensively, with some deep customizations.

Git - Linus developed it in his own heavily customized Emacs fork

Rust - Core team members use various customized setups

Postres - core devs use vim/emacs

Kubernetes - vim/emacs

What the fuck are you even talking about? Majority of high quality shit we use today - probably 90% of all C - from networking stacks - nginx, HAPoxy, OpenSSL, drivers; to compilers and languages; databases; web infra; cryptography; build systems, basically everything written before ~2010 that's still critical infrastructure was likely built by developers in vim/emacs.

All that stuff was developed by those craftsmen you're so dismissively mocking. Do you think they never customized their environments? Spending weeks perfecting configs instead of shipping is a discipline problem, not a tool problem.

Johanx64 10/29/2025||
"Most is software is written using a some text editor."

What an astute fucking observation you've made, mate!

And so it happens, that webdevs and web infra people (which is the extent of your understanding of "high quality shit") tend to use unixes and consequently vim/emacs as their text editor. No fucking way!

Perhaps, you can even tell just by looking at a piece of code - oh, this is beautiful, clean and clear, bugfree, this surely must have been written vim OR emacs?

Or maybe, just maybe, you're just making shit up on the spot and thinking backwards and attributing software quality metrics and outcomes to choice of a fucking text editor and how riced it is.

iLemming 10/30/2025||
I'm not making shit up on the spot nor am I attributing any metrics to vim or emacs specifically or how riced should they be, I'm simply telling you the facts to counter-argue your point of: "hasn't ever led to quality software in any shape or form, neither it ever will".

Most software is not written using "some" text editor, I would love to see maniacs writing kernel patches in notepad.exe or nano. Tools are tools - disputing that vim or emacs are not great tools is plainly dumb, obviously there must be something about them for why they've remained a popular choice among highly skilled pros for decades.

Of course, simply picking up a tool isn't enough - I can perfectly write shitty code equally well in Emacs, InteliJ or VSCode, yet saying good stuff never ever got done there is just disingenuous - it was, it is, and it will be. Of course, ricing the editor and terminal doesn't guarantee amazing shit, but the opposite is also equally true - you can't magically build some awesome sauce by paying for proprietary, sophisticated IDE that "just works" either.

Johanx64 10/30/2025||
> facts to counter-argue your point of: "hasn't ever led to quality software in any shape or form, neither it ever will".

Your line of reasoning is something akin to - there are some skilled programmers that have shipped high quality software and wrote the code using lubed mechanical switches.

Therefore there MUST be something about lubing your switches and obsessing over clacks and thocks that contributes to quality of software somehow.

It's some weird bizzaro cargo cult reasoning.

Unix/webdevs often tend to use vim/emacs -> therefore this absolutely must contribute to the quality of software somehow (it has to!)

Except there are absolutely no basis for this claim, as there are high quality software that is written using neither vim nor emacs nor lubed mechanical switches.

whytevuhuni 10/30/2025||
> > facts to counter-argue your point of: "hasn't ever led to quality software in any shape or form, neither it ever will".

> Your line of reasoning is something akin to - there are some skilled programmers that have shipped high quality software and wrote the code using lubed mechanical switches.

No, I can second that the claim of "hasn't ever led to quality software in any shape or form" has been pretty solidly invalidated by GP. You may be able to claim many other things, and some of them might be true, but that point above won't be.

Johanx64 10/30/2025||
> has been pretty solidly invalidated by GP

How exactly has it been invalidated?

By pointing out that SOME widely used software (mostly web/web infra with unix heritage) has been written using vim/emacs as the text editor?

Now, you can find endless sea of garbage software on github that is written using riced vim/emacs setups - would you therefore conclude that using vim/emacs leads to garbage software?

The only thing you can conclude here is that to write software (either good or bad) you generally speaking need a keyboard and a text editor.

Claiming vim/emacs leads to or directly contributes to "quality software" is the same and about as meaningful as saying that keyboards and text editors lead to "quality software".

Cargo cult insanity.

whytevuhuni 10/30/2025||
> would you therefore conclude that using vim/emacs leads to garbage software?

I cannot conclude that "it leads to garbage software", but I can definitely conclude that "it has ever led to garbage software" at least once, and in some "shape or form".

> Claiming vim/emacs leads to or directly contributes to "quality software" is the same

This (or the alluded opposite) was not the original claim. The original claim was the total impossibility of vim/emacs to have ever led to quality software, in any shape or form. That is the only claim being contested here.

Johanx64 10/30/2025||
Don't tell me what the original claim was.

You contorted it to mean that it's literally impossible to write "quality software" in vim/emacs.

I did NOT claim this. Nobody would claim this either.

I wouldn't make such claim even about nano or notepad or any text editor (of which there and hundreds and thousands) for that matter.

What an insane thing to contest even.

Would I attribute quality of software to - in any shape or form - to the text editor it was written in - whether written in nano, notepad or vim or emacs or god knows what else? No, I would not. That WAS the original claim.

whytevuhuni 10/30/2025||
> I did NOT claim this. Nobody would claim this either.

Regardless of what you wanted to convey, I hope the responses make a bit more sense now.

> What an insane thing to contest even.

We just simply thought so too.

gilbetron 10/29/2025||
> I have come to understand that there are two kinds of people, those who do things only if it helps them achieve a goal, and those who do things just because.

There are two kinds of people, those that think it is clever to split people into just two groups, and everyone else.

Kinrany 10/29/2025||
> This will be highly subjective, and not everyone’s taste will be the same, but that is the point, you should NOT have the same taste as someone else.

Lost me here. If tastes don't converge in the limit, then there's no point and you're just justifying a hobby.

hooskerdu 10/29/2025|
Wrong. ;P
sowbug 10/29/2025||
In my day, we'd say that as kids we'd take apart all our toys to see how they worked. We didn't necessarily call the end goal "taste"; it was to understand how things work, and to learn which results require which trade-offs.
adastrapa 10/29/2025|
agreed, tinkering in my experience is either understanding how something works, or fixing something that is broken, or, building something new entirely (and in my mind all of these are hardware based) and usually involves disassembling things into their constituent components, whether or not you're supposed to. I also don't think tinkering is required for taste, I think being exposed to things, exploring things you're interested in, and questioning things is how you develop taste, which is also highly subjective.
citruscomputing 10/29/2025|
This applies to fashion as well. Hackers should tinker with their clothes and jewelry more.
SchemaLoad 10/29/2025|
My coworkers are shocked and confused that I own/use a sewing machine and see at as some legacy old timey thing. It's true that you certainly don't need to own one anymore and you won't save any money making your own clothes. But you can modify and make loads of custom cool stuff that are impossible to buy new.

I've got a few things I made that just bring a lot of joy knowing it's the exact thing I wanted which you can't buy, and couldn't justify paying someone else to make either.

More comments...