| > is never a code smell /* This changes the sorting of the original list based on the result, when you use a pipeline <- you have an architectural problem - this happens for example in Splunk */ map() /* You need to call these in this exact order, one after another <- your architecture is terrible */ processFirst() processSecond() processThird() /* We did this unusual thing because we hate encapsulation <- obvious paraphrase, and lie, you were just lazy, or you didn't have time */ class A { public static String x } In unrelated code: A.x = "something"; /* We merged these two classes because they looked similar, in the code we have a lot of switches and ifs to differentiate between them, we explained them one-by-one <- do I need to explain this? */ class TwoCompletelyUnrelatedThingsInOne > that's part of my point > The gigantic prompt It was clearly not.* |