In common parlance, the word fetish is used to refer to any sexually arousing stimuli, not all of which meet the medical criteria for fetishism.[5] This broader usage of fetish covers parts or features of the body (including obesity and body modifications), objects, situations and activities (such as smoking or BDSM).[5] Paraphilias such as urophilia, necrophilia and coprophilia have been described as fetishes.[6]
Source Wikipedia
Anyway, just a few words on the 3 points
Unfortunately most business/product owners do not put the performance in top 3 priorities, at least not until is verrry slow or paying customers complain, so we cannot dedicate time to improve it.
Is hard to draw the line but I saw some devs where they took it too seriously and trying to fix a small repetition they added new layers of complexity.
When I was a Lead I cared more about the actual real history, and dates of the commit and authors, and less about the actual message. We didn't squash/rebase them and I had an advantage by doing so, I could see who did what exactly when. I can deduct from the code what does the actual commit does, especially in the lack of tests.
To be super clear (if we're all off quoting Wikipedia YAWN)
Essentially, fetishism is the emic attribution of inherent value or powers to an object.
Where 'emic' means within the social group.
What Chris is saying (I think) is that the social group of developers attribute to the three objects (DRY, time to first byte, and 'clean' commit histories) inherent supernatural powers which they have in and of themselves.
If you are sexually aroused in any way by having a clean commit history, seek help.
Unfortunately most business/product owners do not put the performance in top 3 priorities, at least not until is verrry slow or paying customers complain, so we cannot dedicate time to improve it.
This is not really the point I'm trying to make.
If you are fetishising time to first byte then you are prioritising performance. The point is that you should not be prioritising that above everything else in respect to performance.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Anyway, just a few words on the 3 points
I wouldn't get too caught up about the definition of "fetish".
Wikipedia
To be super clear (if we're all off quoting Wikipedia YAWN)
Where 'emic' means within the social group.
What Chris is saying (I think) is that the social group of developers attribute to the three objects (DRY, time to first byte, and 'clean' commit histories) inherent supernatural powers which they have in and of themselves.
If you are sexually aroused in any way by having a clean commit history, seek help.
Also
This is not really the point I'm trying to make.
If you are fetishising time to first byte then you are prioritising performance. The point is that you should not be prioritising that above everything else in respect to performance.