Getting IT Wrong, Every Day


  • Service Provider

    After a decade of seeing the same "how do people keep making the same mistakes even though we've documented what not to do ad nauseum stuff, I'm going to make a list of the most ridiculous things that truly have no excuse any longer as they've been so thoroughly documented, discussed and the information is so readily available and/or is so insanely basic either for common sense or baseline technical knowledge.

    • Installing Hyper-V as a role instead of directly
    • Using VLANs with VoIP thinking that it is a tool for QoS
    • Using reservations instead of prioritization for QoS
    • Building an IPOD in the SMB
    • Using split arrays
    • Still using RAID 5 on spinners (this is finally starting to fade away)
    • Using a SAN where there is no scale for it
    • Not virtualizing
    • Not patching systems
    • Not keeping systems updated


  • This probably fails into another topic, but I feel it belongs.

    • Failing to document systems (not accounting for the bus)


  • @scottalanmiller said in Getting IT Wrong, Every Day:

    After a decade of seeing the same "how do people keep making the same mistakes even though we've documented what not to do ad nauseum stuff, I'm going to make a list of the most ridiculous things that truly have no excuse any longer as they've been so thoroughly documented, discussed and the information is so readily available and/or is so insanely basic either for common sense or baseline technical knowledge.

    • Installing Hyper-V as a role instead of directly
    • Using VLANs with VoIP thinking that it is a tool for QoS
    • Using reservations instead of prioritization for QoS
    • Building an IPOD in the SMB
    • Using split arrays
    • Still using RAID 5 on spinners (this is finally starting to fade away)
    • Using a SAN where there is no scale for it
    • Not virtualizing

    As far as I know, I'm down to 2 on that list.

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    • Using VLANs with VoIP thinking that it is a tool for QoS

    Tried to talk them out of the other one last week and was laughed at.



  • @DustinB3403 said in Getting IT Wrong, Every Day:

    This probably fails into another topic, but I feel it belongs.

    • Failing to document systems (not accounting for the bus)

    That should be added to the list. Documentation should always be apart of the process and is only setting up oneself for failure if not done properly and maintained.



  • @NerdyDad said in Getting IT Wrong, Every Day:

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    • Using VLANs with VoIP thinking that it is a tool for QoS

    Tried to talk them out of the other one last week and was laughed at.

    Who is making the decisions here? People playing IT?



  • @DustinB3403 said in Getting IT Wrong, Every Day:

    @NerdyDad said in Getting IT Wrong, Every Day:

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    • Using VLANs with VoIP thinking that it is a tool for QoS

    Tried to talk them out of the other one last week and was laughed at.

    Who is making the decisions here? People playing IT?

    Boss has a degree in robotics and landed the job from the previous guy who was just totally out there like 10 years ago. Did it all from vendors with basic IT knowledge. Then I show up and am trying to show him the light. He's not buying it. I'm glad I'm not a salesman. I'd starve.


  • Service Provider

    @NerdyDad said in Getting IT Wrong, Every Day:

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    That's when you go to the owners and talk about some significant organizational concerns.


  • Service Provider

    @NerdyDad said in Getting IT Wrong, Every Day:

    @DustinB3403 said in Getting IT Wrong, Every Day:

    @NerdyDad said in Getting IT Wrong, Every Day:

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    • Using VLANs with VoIP thinking that it is a tool for QoS

    Tried to talk them out of the other one last week and was laughed at.

    Who is making the decisions here? People playing IT?

    Boss has a degree in robotics and landed the job from the previous guy who was just totally out there like 10 years ago. Did it all from vendors with basic IT knowledge. Then I show up and am trying to show him the light. He's not buying it. I'm glad I'm not a salesman. I'd starve.

    Why is he in the position of being your boss? What's the goal in having someone whose sole job is to sabotage IT?



  • @scottalanmiller said in Getting IT Wrong, Every Day:

    @NerdyDad said in Getting IT Wrong, Every Day:

    @DustinB3403 said in Getting IT Wrong, Every Day:

    @NerdyDad said in Getting IT Wrong, Every Day:

    • Building an IPOD in the SMB

    Tried to talk them out of one of them a couple of months ago, but that was shot down quickly.

    • Using VLANs with VoIP thinking that it is a tool for QoS

    Tried to talk them out of the other one last week and was laughed at.

    Who is making the decisions here? People playing IT?

    Boss has a degree in robotics and landed the job from the previous guy who was just totally out there like 10 years ago. Did it all from vendors with basic IT knowledge. Then I show up and am trying to show him the light. He's not buying it. I'm glad I'm not a salesman. I'd starve.

    Why is he in the position of being your boss? What's the goal in having someone whose sole job is to sabotage IT?

    Sometimes - we don't get a choice.



  • @scottalanmiller said in Getting IT Wrong, Every Day:

    Why is he in the position of being your boss?

    He was here before I was.



  • Okay. I'm going to stop jacking this thread. I'd just suggest adding documentation to this list.



  • Best thread title on ML.



  • I asked today if I could do something proper with our documentation since we have stuff scattered around everywhere. I wanted to do a wiki since I do that at home. I found out that it can be switched on in our new ticketing system but just has not yet. The person in charge of the ticketing system is very knowledgeable but just has too much to do. At the same time he holds on to everything he can as do others there. Until I found that out I thought it was a good idea...



  • @scottalanmiller said in Getting IT Wrong, Every Day:

    Still using RAID 5 on spinners (this is finally starting to fade away)

    Witch hunt successful


  • Service Provider

    @jmoore said in Getting IT Wrong, Every Day:

    I asked today if I could do something proper with our documentation since we have stuff scattered around everywhere. I wanted to do a wiki since I do that at home. I found out that it can be switched on in our new ticketing system but just has not yet. The person in charge of the ticketing system is very knowledgeable but just has too much to do. At the same time he holds on to everything he can as do others there. Until I found that out I thought it was a good idea...

    Ugh

    Wiki is a good way to go.


  • Service Provider

    Using the words

    "I've been doing this for x years"
    "I do this for all my clients"
    "There are over _____ number of users of this worldwide"



  • @Breffni-Potter said in Getting IT Wrong, Every Day:

    Using the words

    "I've been doing this for x years"
    "I do this for all my clients"
    "There are over _____ number of users of this worldwide"

    Just because said person has done this a number of times does not mean that they've done it right a number of times and has just been lucky to get it to work this number of times.



  • What about not having backups....? It keeps happening time and over again.


  • Service Provider

    @dbeato said in Getting IT Wrong, Every Day:

    What about not having backups....? It keeps happening time and over again.

    Not nearly so often, though.



  • @jmoore said in Getting IT Wrong, Every Day:

    I asked today if I could do something proper with our documentation since we have stuff scattered around everywhere. I wanted to do a wiki since I do that at home. I found out that it can be switched on in our new ticketing system but just has not yet. The person in charge of the ticketing system is very knowledgeable but just has too much to do. At the same time he holds on to everything he can as do others there. Until I found that out I thought it was a good idea...

    No one is irreplaceable. Some people just don't know that yet.



  • @jmoore said in Getting IT Wrong, Every Day:

    I asked today if I could do something proper with our documentation since we have stuff scattered around everywhere. I wanted to do a wiki since I do that at home. I found out that it can be switched on in our new ticketing system but just has not yet. The person in charge of the ticketing system is very knowledgeable but just has too much to do. At the same time he holds on to everything he can as do others there. Until I found that out I thought it was a good idea...

    Go with the Wiki - Don't put all your information into one system. If it's down, your documentation on how to get it back won't be available...


Log in to reply
 

Looks like your connection to MangoLassi was lost, please wait while we try to reconnect.