tag:blogger.com,1999:blog-5181352157149802369.post3588310150172967356..comments2023-11-28T03:48:54.412-07:00Comments on Coding When High: "If it ain't broke, don't fix it" vs. "Continuous improvement"Jonhttp://www.blogger.com/profile/03567052319139861613noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5181352157149802369.post-74057120982190119872011-04-18T16:08:33.343-06:002011-04-18T16:08:33.343-06:00This topic makes me think back to chemistry class....This topic makes me think back to chemistry class. Reactions are constant with the collisions of molecules, but some will rarely if ever happen without a catalyst. Broken/not-broken situations are high activation energy reactions.<br /><br />Constant collision, continuous improvement, must be pursued, it isn't forced. Even though some efforts will always perhaps require a catalyst, continuous improvement must be intentionally pursued. It's products are important even if they aren't catalyzed by "broken".Unknownhttps://www.blogger.com/profile/17843817559225123526noreply@blogger.comtag:blogger.com,1999:blog-5181352157149802369.post-34464151581973471402011-03-27T20:47:44.889-06:002011-03-27T20:47:44.889-06:00I think the challenge is that there are various de...I think the challenge is that there are various degree of being broken. The perfectionist in me would want to keep on improving the software , but the rationalist me stops me form getting carried away. <br /><br />I think... when its my "own creation" e.g. a module or a framework that I created, its generally the perfectionist that wins and when its something that I "inherited" , the rationalist wins.<br />Pretty lame- eh ?<br />In other words I think it matters (among other factors) how emotionally involved are you with the subject.RNhttps://www.blogger.com/profile/07430438348232305102noreply@blogger.comtag:blogger.com,1999:blog-5181352157149802369.post-70509054907538012542011-03-21T08:54:24.743-06:002011-03-21T08:54:24.743-06:00Jon,
This reminds me of another quote, 'Goo...Jon, <br /><br />This reminds me of another quote, 'Good is the enemy of great'. Scrum is about continuous improvement and achieving greatness. IIABDFI is about being good or average.<br /><br />The biggest problem with just being good enough is you never get better you just keep going along being average. In some ways average is worse than below average. If a team is below average there are obvious issues and change is easier. IIABDFI will get the individual, team and organization in a rut.Unknownhttps://www.blogger.com/profile/17833438295349410696noreply@blogger.com