Editing 2138: Wanna See the Code?
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 19: | Line 19: | ||
Cueball offers to show her his code, but Ponytail remarks that it sounds like he's creepily inviting her to see a dead body. (This is likely a reference to the movie "Stand By Me," which begins with one of the main characters making this exact offer.) Magnanimously, Cueball accepts the comparison, noting that his code ''does'' have at least one similarity to a deceased corpse: although unpleasant, if Ponytail allows it to go unchecked, it causes problems which will get increasingly worse over time. In the "dead body" analogy, a recently-deceased corpse is easier to deal with than one that has been left for a few weeks, which will be decayed, unpleasantly smelly, and will likely have attracted disease-spreading vermin. | Cueball offers to show her his code, but Ponytail remarks that it sounds like he's creepily inviting her to see a dead body. (This is likely a reference to the movie "Stand By Me," which begins with one of the main characters making this exact offer.) Magnanimously, Cueball accepts the comparison, noting that his code ''does'' have at least one similarity to a deceased corpse: although unpleasant, if Ponytail allows it to go unchecked, it causes problems which will get increasingly worse over time. In the "dead body" analogy, a recently-deceased corpse is easier to deal with than one that has been left for a few weeks, which will be decayed, unpleasantly smelly, and will likely have attracted disease-spreading vermin. | ||
| β | |||
| β | |||
This may be a reference to the concept of {{w|technical debt}} in software development: the idea that an initially poor implementation accrues a sort of "compound interest" over time, becoming increasingly difficult to repair the longer it is left unfixed. This happens because any future development might have to take unorthodox or unrecommended measures to work around the problems that are already there, making the system increasingly complex and fragile the more that is added to it. | This may be a reference to the concept of {{w|technical debt}} in software development: the idea that an initially poor implementation accrues a sort of "compound interest" over time, becoming increasingly difficult to repair the longer it is left unfixed. This happens because any future development might have to take unorthodox or unrecommended measures to work around the problems that are already there, making the system increasingly complex and fragile the more that is added to it. | ||
