A super bad designs to avoid

You could have at least kept the property as it's own variable, haha.

//This is really pretty
Polynomial banana = Main.getPolynomialHolder().get(polynomialIndex).getPolynomialVector().get(i);
banana.setExponent(banana.getExponent() - 1);

You could have at least kept the property as it's own variable, haha.

//This is really pretty
Polynomial banana = Main.getPolynomialHolder().get(polynomialIndex).getPolynomialVector().get(i);
banana.setExponent(banana.getExponent() - 1);

Yeah that could have been more readable. Someone on this forum once quoted saying at most you should do is " a.b() " which is a good quote.

You could have at least kept the property as it's own variable, haha.

//This is really pretty
Polynomial banana = Main.getPolynomialHolder().get(polynomialIndex).getPolynomialVector().get(i);
banana.setExponent(banana.getExponent() - 1);

This of course depends on whether or not the various "get"s have other side-effects and the code relies on them being called twice......

shudder

I have seen a lot of people do something like that in production code just to be extra smart. Sadly for being extra smart you generally get a bunch of crashes and bugs which someone else will have to fix.

Doing more than 3 or 4 "concatenated" method calls always makes me doubt if what I'm doing is right.

But then, making a single do-all method call makes you think if that method does more than it should :D