Editing 1739: Fixing Problems
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 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
− | Due to the complex relationships within a program or other system, making an alteration can cause problems with other parts of the program. This can lead to a seemingly small "fix" becoming a long chain of debugging and consecutive fixes, which Cueball is in the middle of | + | Due to the complex relationships within a program or other system, making an alteration can cause problems with other parts of the program. This can lead to a seemingly small "fix" becoming a long chain of debugging and consecutive fixes, which Cueball is in the middle of. As Cueball attempts to solve the initial computer issue, he creates more problems along the way. The title text suggests that the original problem was not stopping the function of the program and the benefits that Cueball may have hoped to achieve with the mentality of "If it ain't broke, break it and fix it" are being consumed by the expanding effort of the fix. Attempting to solve all of these problems results in more time wasted than he hoped would be gained by optimizing the inefficient tool described in the title text. |
− | |||
− | This comic is similar in thesis to [[1445: Efficiency]] and [[1319: Automation]]. | + | This comic is similar in thesis to [[1445: Efficiency]] and [[1319: Automation]]. |
+ | |||
+ | Relevant comics include [[1171: Perl Problems]], where using regular expressions causes more problems than it solves, [[349: Success]], where Munroe comments on the goals of a project decreasing in optimism as a project goes on due to more and more problems distracting from the original, and [[1579: Tech Loops]], which shows that attempting to fix one problem in a piece of software can force a developer to delve into seemingly irrelevant parts of the relevant tech loop that the software in question is trapped in. | ||
==Transcript== | ==Transcript== | ||
− | :[Cueball sitting in | + | :[Single square panel] |
− | :Off- | + | :[Cueball sitting in front of a laptop] |
+ | :Off-screen person: What are you working on? | ||
:Cueball: Trying to fix the problems I created when I tried to fix the problems I created when I tried to fix the problems I created when... | :Cueball: Trying to fix the problems I created when I tried to fix the problems I created when I tried to fix the problems I created when... | ||
− | |||
{{comic discussion}} | {{comic discussion}} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− |