3 ms·

I think with this one it is, because everyone has tasted before, but comparatively few have coded before. So everyone can say something about their subjective t

I think with this one it is, because everyone has tasted before, but comparatively few have coded before. So everyone can say something about their subjective taste experiences, but not so many can about some code. The actual difference might be subjective or one of practiced ability to distinguish in detail. There is also the aspect of science and engineering leading to objective an hopefully reproducible results. There is less subjective matter to it and there are objective criteria to measure quality. It is possible to leave personal taste out of the equation. Imagine a michelin star tester eating and having to throw up, because of taste, even though the kitchen is clean and all ingredients were of superb quality and the cook is really good. Would they still approve objectively?

Ansil849 5y ago
> I think with this one it is, because everyone has tasted before, but comparatively few have coded before. I don't think this is an apt comparison. Tasting is consuming something, coding is creating something. An apt comparison would be tasting to using apps, or coding to cooking. And now sure, you could say that most people have cooked before, much like most people have performed rudimentary medical procedures before; but most people have not performed complex medical procedures, or successfully made complex Michelin-starred dishes, or coded high-quality apps.
deleted 5y ago
[deleted]
bobthepanda 5y ago
> So everyone can say something about their subjective taste experiences, but not so many can about some code. This is not too true for frontend. Everyone and their mother has an opinion on what needs to be pixel pushed, or something that "should be easy."