tag:blogger.com,1999:blog-3669809752172683097.post1887277597016950279..comments2024-02-08T04:04:28.385-08:00Comments on Cyclopedia Square: Averse to ChangeBryanhttp://www.blogger.com/profile/11394436715172971234noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-3669809752172683097.post-64168911654249607542024-01-09T23:34:49.263-08:002024-01-09T23:34:49.263-08:00Very thoughtful bloogVery thoughtful bloogCollin Ramirezhttps://collinramirez.wordpress.com/noreply@blogger.comtag:blogger.com,1999:blog-3669809752172683097.post-73601420673100938102012-01-29T11:12:02.254-08:002012-01-29T11:12:02.254-08:00Awesome article!!! I must say that I have a good p...Awesome article!!! I must say that I have a good portion of Bob and Fred inside me. ;-) However, I am constantly try to change for the better.<br /><br />Best regards,<br />MarkusAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3669809752172683097.post-21124081939150670102009-07-23T16:04:26.433-07:002009-07-23T16:04:26.433-07:00I was "Fred" (the tools guy) in a previo...I was "Fred" (the tools guy) in a previous life, with almost the exact situation you describe. (Server running RH8 for >5 years!)<br /><br />I desperately wanted to upgrade, my workstation was upgraded through fedora 2/4/etc. I wanted the server to keep up.<br /><br />The real problems were (1) lack of time -- it really does take a lot of extra time when your primary responsibility is shipping *revenue* software.<br /><br />(2) Supporting users who are more fragile ("averse to change") than you think -- having management ask me "why did you make a change that blocked Bob from getting his work done?" is not what I want to deal with. When you rebuild the toolchain to newer libc, *everybody* has to upgrade their workstation. Debian makes this relatively easy, RH makes it harder, we were on RH/FC.Brian St. Pierrehttp://bstpierre.org/noreply@blogger.comtag:blogger.com,1999:blog-3669809752172683097.post-53425142320555282892009-07-23T01:19:12.891-07:002009-07-23T01:19:12.891-07:00Pretty much my first reaction to these examples wa...Pretty much my first reaction to these examples was, "so, where is the automated testing then?". <br /><br />My second is that there is no sense of balance here. Blocking all change has benefits (cannot introduce new bugs) and costs (cannot meet new requirements and cannot fix existing bugs). Unconstrained change has benefits (agility, rapid cycle times, outpacing the competition on features, greater opportunities for refinement) and costs (increased bug rates, out of date documentation and support infrastructure). The key thing is to find the right balance, and to do that you need to maintain awareness of the benefits & costs of movement toward either end of the continuum.Jameshttps://www.blogger.com/profile/05368777100767513555noreply@blogger.com