Blogs Classifieds Downloads FlashChat Gallery Googlemap Invite Friends Links Projects Reviews Wiki
 


Welcome to the pSeries Tech Forums, our free peer-based support site for administrators, engineers and architects working with IBM pSeries servers and software.

You are currently viewing our site as a guest which gives you limited access to view most discussions, articles, tutorials and access our other free features. By joining our community you will be able to collaborate with administrators, engineers and architects charged with designing, delivering or maintaining IBM pSeries server environments.

Founded by a recognized IBM pSeries consultant and IBM Redbook author, pSeries Tech Forums was developed with the single mission of bringing IBM pSeries professionals together into a single self-help community.

Registration is fast, simple and absolutely free to all IT professionals with responsibility for or interest in IBM pSeries servers. We invite you to join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

Our Sponsors
Want to advertise?  


Reply
 
LinkBack Thread Tools
  #1  
Old August 9th, 2006
alexisl's Avatar
alexisl Offline
Senior Member
 
Join Date: June 2006
Posts: 147
Schools of Thought

This has come up in a recent conversation and has gotten me to think about it. There are basically three schools of thought for most people. The first is "If it ain't broke don't fix it". I tend to fall under this category most of the time. The second is "Preventive maintenance will prevent a breakdown". Which most people fall into some of the time. The third is "Get the product out and we will fix it later". This is a corporate type of mentality. Maybe a little examination will tell us why we chose each of these trains of thought, sometimes even trains for different occassions.

"If it ain't broke don't fix it" I tend to go with this one a lot, mostly because I have been burned before trying to "fix" something that was working fine before. It applies to just about everything from car repairs to installing the latest patch for the OS. Some times the patches create more problems than they fix so I tend to wait until a new Maintenance Level comes out because they are supposed to be the most stable.

"Preventive maintenance will prevent a breakdown" I used to go with this train of thought most of the time until I got burned by it but it does have its merit if used cautiously. You will always have the latest patch installed and be as secure as possible at the time. The best advice for this is to be sure you know what you are installing and if it is considered stable. I don't know how many times I havee installed things just to find out it was not what I wanted or needed. Still I do go with it on some things such as oil changes in my car because this maintenance has proven to work.

"Get the product out we will fix it later". This seems to be creeping into all corporations and not just the obvious software companies. How many recalls of vehicles have there been in the last year. There was some discussion years ago about the stabitiy of a certain OS. The discussion went along the lines of: if a car had that many problems it would be recalled, the CEO of the company replied with something to the effect; if the computer crashes it doesn't leave you stranded on the side of the road. While that might be true what is more costly; a tow truck or lost revenue while trying to repair the software, not to mention the cost of the restoration itself. It all boils down to money and greed.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!Spurl this Post!Reddit! Wong this Post!
Reply With Quote
Reply

Bookmarks

These are the 100 most searched terms
Search Cloud
0042-001 0042-001 nim 0513-001 the system resource controller daemon is not active 0513-001 the system resource controller daemon is not active. 0514-061 0514-061 cannot find a child device 0514-061 cannot find a child device. 0516-787 0516-787 extendlv 0516-787 extendlv: maximum allocation for logical volume 110000ac aa00e1f3 aio aix aix aio aix freeware aixif_arp_dup_addr b150f22a b181fb53 ba010004 c1001020 d133c002 dacnone dcb47997 dlpar fcp_array_err6 fget_config gnu tar aix gsclvmd gtar aix hi yall hmc root password hmc vmware hscl05db ibm p6 ibm p6 520 libpopt aix libpopt.a libpopt.a(libpopt.so.0) is needed by rsync-2.6.2-1 migratelv mksysb navisphere agent nim server pseries pseriestech rsync aix sc_disk_err4 scan_error_chrp vio server websm xhost file ... powered by Simple Search Cloud


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0
Powered by vbWiki Pro 1.3 RC5. Copyright ©2006-2007, NuHit, LLC

vBulletin Skin developed by: vBStyles.com


1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50