5 ms·
In some sense, many "developers" are also cheaters, or thieves. Because a working product is not actually the expected product. It must be based on some speci
by revskill 3y ago
In some sense, many "developers" are also cheaters, or thieves.
Because a working product is not actually the expected product.
It must be based on some specialized benmarch and criterias.
It's a lesson for business people or shareholders to learn.
Example: To fix N+1 issue in RoR application is not simple. Cheaters won't spend their efforts to fix it to release.
- cratermoon 3y ago> Cheaters won't spend their efforts to fix it to release What reasons would developers have to 'cheat', as you call it? If they are experienced enough to recognize something like problematic N+1 queries, why wouldn't they rewrite them, regardless of the effort? Further, what reason would they have to write them in the first place, if they know better?
- revskill 3y agoBusiness people don't know N+1 query is the issue. Normally they only care if a feature is working or not. About performance, it's upon the developer to fix it or not.
- cratermoon 3y agoYes, those are broadly true generalizations, but they don't answer my question. > it's upon the developer to fix it or not. But why wouldn't the developer fix it? What incentives do they have for leaving a known problem unaddressed?