Hacker News new | past | comments | ask | show | jobs | submit login

You’ve created a concept and attached the word “perfect" to it. Your concept is different than the shared definition. This leads to disagreements, misunderstandings, and (as you said) twitching.

The purpose of words is to share information. If you have write a paragraph describing your definition when you use a word, use a different one.




Not really. When I look up the definition, it is 'completely free of faults or defect'. I don't think I've strayed past that meaning.


yes you have. you've moved it into the subjective by requiring pleasing aesthetics


Perfection is subjective because flaws are subjective. Aesthetics are part of the code. If a piece of code is functionally perfect but ugly or inelegant by some measure, then it is imperfect by that measure.


right, flaws are subjective. I'll try that one on my QA team next time they file a bug report ;)


There is more than one class of flaw. Some are objective, ie. fail to meet spec. Some are subjective, typically where the spec doesn't cover.

If software functions correctly but is unnecessarily hard to use due to (eg.) bad layout, would you still call it perfect?


>has tabs

>literally trash




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: