2to3 was a bad idea

Posted Feb 26, 2018 21:46 UTC (Mon) by mathstuf (subscriber, #69389)
In reply to: 2to3 was a bad idea by rahvin
Parent article: Hovmöller: Moving a large and old codebase to Python3

No finger pointing was mentioned. The idea is to analyze how the decision-making process works (or doesn't) and how to improve it. Those who care about blame will find some and assign it anyways.

2to3 was a bad idea

Posted Feb 26, 2018 22:16 UTC (Mon) by raven667 (subscriber, #5198) [Link]

Yes, that is what I meant, playing some blame and shame game is not effective to generate learning, only the avoidance of pain, whereas accountability and analysis of the decision making process, after the outcomes are known, can generate better decisions in the future about the future.

2to3 was a bad idea

Posted Mar 6, 2018 11:02 UTC (Tue) by dgm (subscriber, #49227) [Link]

I mostly agree. The question is not about pointing fingers, but about avoiding such bad decissions in the future. For that, looking at the root cause is the most important thing. Were there any good arguments that were being ignored? If so, why? Of course, you have to balance that with analysis-paralisis. Decissions need to be made in reasonable time, otherwise they are not any good.

Who got it right is important, but only so much. You have to take into account the broken clock effect (you know, even a broken clock gives the right time twice a day), so better start listening to people with future-viewing super powers once they have proved themselves, at least, a couple of times.