Yes, it does work but usually it means that the programmer wrote some ambiguous piece of code that is not complying with the design of the software and that will confuse every programmer who has to read that code. There is a better description on Wikipedia on this.
In the context of electrical engineering, this is good. A hack is a word to describe the process of tweaking things to do something they were not meant to do. If you want to really get a bit of history, you can Wikipedia it. That's can be an example of ignorance or a false assumption.
Is it using a side effect of code as a part of your solution? The hack is based on ignorance, bugs or assumptions. "Budget" is a common justification, but this is essentially one of the above three (ignorance, arrogance or error) with a non-technical root cause. Management override to good design and correction assumptions. mistaken assumptions) about an API or language construct.Īctual bugs that aren't solved but are worked around. The second example, however, might be hack that gets used because of ignorance of a better practice or an assumption that made /1 seemed simpler at the time or a bug in a library that made the /1 work correctly.
0 kommentar(er)
