This is more of an anti-pattern, but I saw what I call the "Keep it all in one place" pattern. This is a great application, where all variables that were not local for each class, EVERY class, were stored in one class P (for parameters). Aside, all static variables were contained in a class called ... wait for it ... S.
In any case, some of them, this project became quite large, and suddenly nothing happened. (I was hired at this time). Surprisingly, the program did not crash, it just had a lot of side effects that made the application confused. As you can imagine, multiple threads, all accessing P and changing variables, without locks or synchronization in place.
I tell you, it was a real sight.
The company opened a new office and hired 3 people to serve it, and I was one of them. We got the program and said to fix it. We spent days sitting just clapping our eyebrows. Now, a print on my palm appeared on my face.
Other funnies ... a variable named "fudgeFactor". Still don't know what it did.
A way to get the next ascii character ...
char getNextChar(char previous) { switch (previous) case 'a': return b; case 'b': return c; ... case 'z': return a; }
Anyway, my funny picture ... with some extra funny fun.
scubabbl
source share