Join the discussion
Write your take first — we'll ask for email only when you're ready to publish.
- Hacker News
- I’d like to tinker with that font, it burns my eyes to try and read the words styled like that, maybe that’s the intent?by andy99
- I think the author has a point, but his examples are bad. He talks about mouse sensitivity, windows manager, keyboard switches, and vscode. All those things were made to be tweaked. He's not so much exploring as he is playing with a toy the way it was intended. The stickiest learning comes from getting things wrong, and that happens when you're using things the way you're not supposed to. For example disassembling a microwave. Not the keyboard switches.
The world has become so comfy that even tweaking has been packaged and monetized by some company. That's right, I'm gatekeeping tweaking, sue me.
by bfkwlfkjf - > ...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. The ideal, of course, is to be a mix of both.
This is related to what Robert Pirsig in Zen and the Art of Motorcycle Maintenance calls the romantic (subjective, "artistic") and the classical (objective, "scientific") understanding. He, too, points that the ideal is to enjoy both. Not because there are both useful and have their place and time, but because this is a false dichotomy to begin with and, ideally, one should refrain from defining the splitting and abandon both concepts (after all, the Zen in the title is there for a reason).
by newsuser - This is the second article I've seen on taste here. It seems to me the author's definition of "tinkering" is primarily describing hyperfocused, repetitive behaviors found in neurodivergent individuals, potentially even a complex form of stimming. I think this is unrelated to taste.
I think good taste in engineering comes down to a mix of skill and knowledge. It isn't just about how you can reach a goal, but rather about having a solid internal map of the world and an understanding of which parts of the map you are unfamiliar with. To those lacking knowledge, the map can deceptively appear much smaller. Skill allows you to effectively find your way to the places you know you can go. With knowledge and skill, taste comes naturally. Those with bad taste, I've found, are those with limited knowledge of the vast universe of tools available and/or the lack of skill needed to utilize those tools effectively.
- Some of the worse engineers I've ever interacted with had too strong of a "taste" for what they felt were right and were completely unable or unwilling to work outside of that. Developing a superiority complex because you think you have "taste" is a great way to torpedo your team.
Coding for others is not art, it does not have much meaning in of itself. Your users won't marvel at your choice of language or your usage of design patterns - they care about how the end product looks and works.
In a world like that where you have to work in a team, why you ever wear your inflexibility as a badge of pride? The ones who are the most useful are the ones who can code any way, any how, and can plugin anywhere - "taste" be damned. If you want to be a net positive on the teams you work on, stop thinking it's about you, because it's not.
by billllll - I used to resonate with the word "taste" as a distinguishing factor between good and bad quality, but a comment on HN some months ago about one of the many blog posts that talks about taste really nailed it:
"Taste" is just the degree to which two people value the same things.
When someone is rated as having "good taste" it just means that the person rating them values a lot of the same qualities.
The more I thought about it, the more that applies everywhere: Food, wine, clothes, architecture, software design, etc.
by saxelsen
I think in this age of vibe coding where anyone can code anything, the discriminating factor between two developers, at a technical level, just comes down to "good taste" (lots of other more important factors, too, like a good human to work with).> 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.And like the author, I agree that taste is acquired through tinkering and trying to be able to discern the qualities of one approach or one design over another. You can't have good taste in anything without having tried lots of variants in that domain -- wine, sushi, furniture, color, style, etc. Having this quality now is more important than ever for senior devs and mid-level devs that want to reach the next level.
When anyone can vibe code, it is the ones with "good taste" in the design of systems that will thrive. Anyone can use an agent and code fast; few will be able to do it fast and well and build systems that do not eventually collapse under the weight of their own tangled mess.
How to acquire it? Have a folder called `sandbox` and just build small projects in there and try new ideas, new techniques, new libraries you come across. Used a particularly interesting package? Go check out the GitHub repo and see how they did it; learn something new. Good taste can be acquired; it just surprises me how few devs actually care to seek it.
- Decades ago, an old friend told me "I became a coffee expert, I learned everything there is to learn about beans, the ways to prepare them, the chemistry that goes into it, and now I can only enjoy a cup of coffee prepared by the most expensive machines from the most expensive beans. The shit part is that I enjoy it just as much as I enjoyed my shitty supermarket coffee back when I didn't know anything about coffee."
That advice has stuck with me, and I try to have the least taste I can. I use $20 headphones and a $200 TV because I can't tell what "good" is, and I enjoy music and movies as much as my friends with $600 headphones and $3k TVs do.
by stavros