>Reusing someone else's code with credit is not cheating or taking a short >cut. > >A sysadmin cheating and taking a short cut is one who shoves in a "quick >fix" or hack, usually claiming it's temporary, and always without proper >testing or consideration for the consequences of their actions. Ninety >nine times out of one hundred those "temporary" fixes are still there a >month later. > >Real sysadmins do not cheat and use short cuts, they work out the right way >to fix it and do it, or do their best to do it, the first time. Completely agree.
I would describe what you are saying as "band aid fixes" or "quick and dirty fixes". I highly discourage this as well. I have seen many temporary fixes in place 12 months later. By "shortcut" I was meaning things like instead of you taking a week to write code to solve a problem, look for someone else's effort. There are lots of smart people who have probably solved something similar before you tried. IT Professionals should *always* be willing to sign their name to their work. I would never be comfortable with a comment like "This fix was made by Craig Cook on date" if I knew it was going to be a mess for someone else to clean up. Craig
_______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
