Editing 1926: Bad 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 8: | Line 8: | ||
==Explanation== | ==Explanation== | ||
− | + | {{incomplete|Created by a bad coder, very incomplete, added (possibly excessive) explanation for load-bearing wall. Please change this comment when editing this page. Do NOT delete this tag too soon.}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | [[Ponytail]] has caught [[Cueball]] in the act of writing some messy code | + | [[Ponytail]] has caught [[Cueball]] in the act of writing some messy code - code in the form of a spreadsheet formula, which in turn produces another program in a language called {{w|Haskell (programming language)|Haskell}}. |
− | + | Haskell is a {{w|purely functional programming}} language, a concept that has a debatable steep learning curve, which causes Haskell to be a somewhat obscure programming language, as referenced in [[1312: Haskell]]. | |
− | Immediately after, Ponytail appears to have | + | It is explained that ''this'' code will, in turn, interpret ''more'' source code, specifically markup in {{w|HTML}}. |
+ | After Cueball excuses his bad code by stating that "nothing depends on this" (meaning that no other projects rely on this code being good to operate properly), Ponytail uses the analogy of breaking a non-load-bearing wall to ridicule Cueball's excuse. | ||
+ | |||
+ | A {{w|load-bearing wall}} is a wall that plays a role in supporting the building. Damaging such a wall would threaten the structure of the entire building, and could potentially cause a collapse. By contrast, walls that aren't load-bearing are designed only to separate spaces within the building, and do not contribute to keeping the building up. Damaging or destroying such walls wouldn't endanger the overall structure of the building. However, supporting the building is just ''one'' of the functions which could depend on having an intact wall; walls serve many other important purposes, from creating opaque and sound blocking barriers (desirable for privacy purposes, particularly for bedrooms and bathrooms{{Citation needed}}), to containing and protecting water pipes and electrical wiring. Ponytail's analogy suggests that, even though poorly written-code wouldn't cause the entire program to fail, it's still not a good idea. | ||
+ | |||
+ | Immediately after, Ponytail appears to have realized that she's only ''inspired'' Cueball to go ahead and break the wall, instead of swaying him away from writing ugly code. If left unchecked, this will only end in tragedy. [[905: Homeownership|Hilarious, knee-slapping tragedy.]] | ||
This is most likely a continuation of the [[:Category:Code Quality|Code Quality]] series, but it differs slightly. For one thing, all of the previous strips were named "Code Quality <number>", with the exception of the first, which was just named "Code Quality". Also note that, unlike the previous Code Quality strips, Ponytail does not start using similes like "This is like being in a house built by a child using nothing but a hatchet and a picture of a house". It's also the longest explanation of Cueball's code by Cueball himself. | This is most likely a continuation of the [[:Category:Code Quality|Code Quality]] series, but it differs slightly. For one thing, all of the previous strips were named "Code Quality <number>", with the exception of the first, which was just named "Code Quality". Also note that, unlike the previous Code Quality strips, Ponytail does not start using similes like "This is like being in a house built by a child using nothing but a hatchet and a picture of a house". It's also the longest explanation of Cueball's code by Cueball himself. | ||
− | The title text suggests that Cueball's approach to breaking the wall - scotch-taping a bunch of hammers together - is as good as his code | + | The title text suggests that Cueball's approach to breaking the wall - scotch-taping a bunch of hammers together - is as good as his code. And his excuse is similar. |
==Transcript== | ==Transcript== | ||
− | :[Cueball is at his desk | + | :[Cueball is at his desk in a swivel chair, using his computer. Ponytail walks towards him.] |
− | :Ponytail: That's the ugliest mess of code I've ever seen | + | :Ponytail: That's the ugliest mess of code I've ever seen! What on earth are you working on? |
:[Cueball swivels his chair to face Ponytail in a frameless panel.] | :[Cueball swivels his chair to face Ponytail in a frameless panel.] | ||
Line 33: | Line 33: | ||
:Cueball: It just looks bad because it's a spreadsheet formula. | :Cueball: It just looks bad because it's a spreadsheet formula. | ||
− | :[Cueball is | + | :[Cueball is facing his computer again.] |
:Cueball: ...which assembles a Haskell function. | :Cueball: ...which assembles a Haskell function. | ||
:Ponytail: Uhhh. | :Ponytail: Uhhh. | ||
Line 39: | Line 39: | ||
:Ponytail: ...oh my God. | :Ponytail: ...oh my God. | ||
− | :[Ponytail | + | :[Ponytail is pointing away from the scene.] |
:Cueball: It's ok! Nothing depends on this. | :Cueball: It's ok! Nothing depends on this. | ||
:Ponytail: That wall isn't load-bearing. Does that mean we can just throw hammers at it? | :Ponytail: That wall isn't load-bearing. Does that mean we can just throw hammers at it? | ||
Line 53: | Line 53: | ||
[[Category:Code Quality]] | [[Category:Code Quality]] | ||
[[Category:Cueball Computer Problems]] | [[Category:Cueball Computer Problems]] | ||
− |