tag:blogger.com,1999:blog-36118108.post4668909908814422489..comments2023-12-06T00:17:28.519-08:00Comments on Creative Chaos: Choices ...Matthewhttp://www.blogger.com/profile/05956714498778698672noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-36118108.post-41629116354802923572007-02-03T10:31:00.000-08:002007-02-03T10:31:00.000-08:00and said "It's getting tot he point where all you ...<i>and said "It's getting tot he point where all you get to do is decide to use a FOR loop or a WHILE loop."<br /><br />He replied that "Yeah, we really should document the pros and cons of a FOR loop verses a WHILE loop, so we can created a repeatable way to decide which to use."<br /><br />I'm not kidding. He wanted the process to determine which kind of loop to use.</i><br /><br /><b>LOL.</b><br /><br />This is what I hate about most "best practices" and detailed processes. High-level process is good. Process (and automation) is good for things that require consistent repeatability. Process can be good with large and/or inexperienced teams. <br /><br />However, processes that micro-manage can be laughable when proposed and ridiculous -- even dangerous -- when implemented.<br /><br />Process should help us be more productive and improve quality. We need to be flexible enough to bend the process when it doesn't apply. ... but first we'll have to go through the process bending process. :)<br /><br />I have encountered a number of people that require a defined process to be productive. It is a challenge to get some people to think without a process to guide them.Ben Simohttps://www.blogger.com/profile/11448600123169359955noreply@blogger.com