Skip to main content

Timeline for What is the For-Case Antipattern?

Current License: CC BY-SA 4.0

13 events
when toggle format what by license comment
Jun 17 at 12:54 comment added Mark Amery @gnasher729 I tend to agree, but can imagine initially-reasonable code evolving to have this pattern through sloppy-but-not-insane changes. For instance, imagine a five-step data-wrangling tool where initially each step is to be run individually so it can be manually reviewed and tweaked before the next step. A CLI that takes a step number argument and passes it into a switch might be a fine implementation! Then the process matures; manual review is eliminated and all 5 steps just need to run in sequence automatically. Finally imagine a careless, rushed developer makes that change...
Jun 16 at 21:22 comment added gnasher729 Strange that it is an anti-pattern. I see it, I just shake my head, and think why would anyone do that? How did this ever become a pattern?
S Mar 5 at 19:59 history suggested Marcus Kwok CC BY-SA 4.0
Fixed link to Raymond Chen's blog post
Mar 5 at 16:39 review Suggested edits
S Mar 5 at 19:59
May 15, 2017 at 10:52 review Suggested edits
May 15, 2017 at 10:56
May 15, 2017 at 3:46 history tweeted twitter.com/StackSoftEng/status/863963688457383936
May 10, 2017 at 20:00 vote accept Mark Amery
May 10, 2017 at 13:51 answer added Satanicpuppy timeline score: -3
May 10, 2017 at 13:48 answer added Mason Wheeler timeline score: 27
May 10, 2017 at 13:17 review Close votes
May 15, 2017 at 3:01
May 10, 2017 at 13:02 comment added David Arno It's commonly known as (and easier to find via search engines) as the loop-switch anti-pattern
May 10, 2017 at 13:01 comment added Reinstate Monica thedailywtf.com/articles/The_FOR-CASE_paradigm
May 10, 2017 at 12:56 history asked Mark Amery CC BY-SA 3.0