Web Frameworks Excessive Complexity

Andriy Kornatskyy andriy.kornatskyy at live.com
Wed Nov 21 12:02:26 CET 2012


You would never get a better product by accident.

The meaning of better product might differ from team to team but you can not ignore excessive complexity. Earlier or later you get back to that code and refactor it, thus existence of such fact was driven by your intention to make it a bit better (easier to understand, to support, to cover with unit tests, etc), with a team of 20 heads you can get even further: the whole team adherence. So those drops make the overall picture better. This is what you, as a software developer, donate to what the final better product become.



> To: python-list at python.org
> From: robert.kern at gmail.com
> Subject: Re: Web Frameworks Excessive Complexity
> Date: Tue, 20 Nov 2012 20:33:46 +0000
> On 20/11/2012 20:22, Andriy Kornatskyy wrote:
> >
> > Robert,
> >
> > I respect your point of view and it definitely make sense to me. I personally do not have a problem to understand CC but agree, method LoC is easier to understand. Regardless the path your choose in your next refactoring (based on method CC, LoC) it gives your better product.
> No, refactoring based on CC does not give you a better product, except by accident.
> --
> Robert Kern
> "I have come to believe that the whole world is an enigma, a harmless enigma
> that is made terrible by our own mad attempt to interpret it as though it had
> an underlying truth."
> -- Umberto Eco
> --
> http://mail.python.org/mailman/listinfo/python-list

More information about the Python-list mailing list