I?ve been in IT for a long time, ranging from mainframes and 300 baud modems (back in the day), to today?s current server/client architecture. I?ve planned, created, managed, and administrated networks. This is a job I loved to do before it becamethe ?in? career field. I?m not ?tooting? my own horn, but just adding ?insight? into my background.
After reading many posts over several years on this site, I hate to inform many of you that — THE NETWORK IS NOT YOURS!!!!! There are business rules, polices, practices, network performance issues, user productivity, time constraints, budgets, legacy applications, vendor inoperability, management, and get this one ? ETHICS, to consider on each LAN/Network.
1. This is not a career field for EGOS ? Nobody is above getting their hands dirty or doing the ?little? things. Remember ? IT is there to help achieve organization?s goals. That?s what you were hired for.
2. The LAN is not for games: You don?t own the bandwidth orthe computers, so WHY do you think you should be able to play games on something that’s not really yours? Answer ? Go home and use your own resources!!! If the business polices or rules doesn’t state that you CAN play games, then don?t assume thatyou can because you exist and the games exists that you are free to play it on something that is not yours.
3. Self-Importance: This one is funny. During the boom the IT people received a lot of attention and praise. Currently, in today?s climate that?s not happening as much. So, when many IT people ?fix? a problem or come up with a ?solution? their feeling are hurt when management or someone doesn?t ?bow down? because they did their JOB!!!!! (I?m talking smaller issues)I can go on for days on this one.
