Originally posted by Kobayashi.K An interesting aspect in the Wikipedia article, at the bottom is:
"Feature creep combined with short deadlines will often lead to a "hacky solution". The desired change may be large enough to warrant a redesign of the existing project foundation, but deadline pressure instead requires developers to just "make it work" with a less elegant approach."
The K3-III is actually plagued with hacks. Without expanding on that too much I'll mention four of them:
1. In some places the menus are using the INFO button to advance into the structure instead of OK or the > button. It is a lazy hack, because the INFO button is supposed to give information.
2. The menu structure for setting the smart functions is a mess, and it looks implemented in great haste.
3. The DCU software is baked into the camera to replace the CD, but it cannot be updated, while software is supposed to be upgradeable during its lifetime. So after one upgrade (which already happened) the DCU is sitting in the camera for nothing.
4. The functionality for using M- and K-series lenses in automatic modes uses exposure measurement at full press of the shutter with all sorts of ugly consequences. Exposure measurement should always be done at half-press. They have done that to prevent users complaining about the sound of the aperture closing with the green button functionality every time you touch the shutter button with a half-press.
So, you disagree with design decisions made by the designers - but that has zero connection with how they are implemented, which is where the word "hack" is appropriate.
As a professional, I would
never describe these as "hacks". The word "hack" may be used to describe the implementation, but neither of us knows exactly what the code looks like.
You, in your great expertise, may disagree with the decisions made, but neither of us knows
why they were made, and - incidentally - I don't see why any of them would be classified as "feature creep".
"Feature creep" refers to adding feature after feature for lack of a good reason - for example, adding a flashlight onto a camera.
"Feature creep" plus short deadlines
may lead to "hacks" - but you
cannot run the logic backwards and say that "hacks" 'prove' "feature creep", and we have no evidence of short deadlines in this case.
For all either of us knows, this system is exactly as they planned it to be - perhaps not understandable to your logic, but proof of nothing but disagreement between you and them.