Timeline for Does this anti-pattern have a name?
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 9, 2018 at 16:08 | comment | added | Flater | @amon: You'll want to remember bad things too, so you can stay away from them. I wouldn't fly a plane into the Bermuda triangle. If I had never heard of it before, I wouldn't be too fussed about flying into it (and presumably regret it later). As long as the name is attributed to the entire range of possibilities for the same mistake, and not just a particular subset of it; naming it seems fine (e.g. the northern half of the Bermuda triangle doesn't need a unique name to warn pilots flying into it). "Bad code" is an overly terse summary, and not enough to identify the problem ahead of time. | |
| Feb 9, 2018 at 16:05 | comment | added | Flater | Trying to coin a name for it, I'll pick "embroidering". | |
| Jan 15, 2018 at 22:53 | comment | added | Mark Benningfield | This is a Coding Horror if I ever saw one. | |
| Jan 15, 2018 at 22:51 | comment | added | Steve | Good grief! This example should go into a museum of horrors, alongside pickled body parts. | |
| Jan 15, 2018 at 17:58 | comment | added | David Arno |
getSingletonInstance. There’s your first anti-pattern right there. It’s called the singleton anti-pattern.
|
|
| Jan 15, 2018 at 14:44 | comment | added | Dan Pichelman | Have the author of the code read How would you know if you've written readable and easily maintainable code? | |
| Jan 15, 2018 at 14:36 | vote | accept | h22 | ||
| Jan 15, 2018 at 13:33 | comment | added | Doc Brown | ... or simply Overengineering, if you prefer that. | |
| Jan 15, 2018 at 13:33 | review | Close votes | |||
| Jan 22, 2018 at 3:04 | |||||
| Jan 15, 2018 at 13:27 | comment | added | Doc Brown | Call it The Daily WTF, if you like. | |
| Jan 15, 2018 at 13:15 | answer | added | Neil | timeline score: 7 | |
| Jan 15, 2018 at 13:14 | history | edited | Kilian Foth | CC BY-SA 3.0 |
fix grammar
|
| Jan 15, 2018 at 13:13 | history | edited | h22 | CC BY-SA 3.0 |
added 9 characters in body
|
| Jan 15, 2018 at 13:12 | comment | added | amon | Recommended reading: Naming considered harmful: STOP IT. Avoid naming things that don’t need to have names. This was bad code. We gave it a name and joked about it. But now, I’ve got a name for it. It is not a good thing. This code already had a name before we christened it – it is Bad Code. Use names for things that you want to remember. | |
| Jan 15, 2018 at 13:09 | history | asked | h22 | CC BY-SA 3.0 |