TNoB Archives - TrinityDigitalMedia.com

TNoB Archives - TrinityDigitalMedia.com

By TNoB Archives - TrinityDigitalMedia.com
Download on the App Store

TNoB Archives - TrinityDigitalMedia.com episodes

  • Troubleshooting Techniques: Putting it all together | Tech, No Babel

    Troubleshooting Techniques: Putting it all together

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Putting it all together
    When you’re troubleshooting, you may come across the answer very quickly. Most of the time, though, it will be a process where you ask a lot of questions, whether remotely or in person. It can take some time, but don’t give up.

    Troubleshooting can be a process that takes many steps. Don’t give up. Here’s how to put it all together:Click To Tweet

    Ideally, you would start with the scientific method, and then devise tests to prove or disprove your suspicions. Sometimes those test will be the “short-leash” test, or just simpling it down. Sometimes, it will be just as simple as rebooting a computer or recognizing that the problem is one inherent to digital technology.
    Don’t give up, though. It’s worth the trouble of putting all the pieces together to arrive at the solution.
    For more, watch the video above.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):
    Subscribe on YouTube
    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    8 min
  • Troubleshooting Techniques: Reterminating Cables | Tech, No Babel

    Troubleshooting Techniques: Reterminating Cables

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Reterminating Cables
    All things being equal, cables tend to have problems before hardware. Beyond that, the ends tend to have problems before the middle of a cable. So, reterminating cables will fix problems more than almost any other solution.

    Cables tend to break before other hardware, especially their ends. Here’s what to do about that:Click To Tweet

    This happened to me just last Saturday. I had just done some cleaning and rearranging of my office, moving the router from the far wall from my desk to one of the sides. In doing so, the whole system initially worked, until I moved the cables to make them neater.
    After checking the obvious things (everything was plugged in and I restarted the router and the cable modem), it still didn’t work. Then I asked, “What changed?” The only thing that I had done was move cables. That told me I probably had an intermittent short.
    Knowing that cables tend to break at the ends and not in the middle, I decided to reterminate the cable. I cut off the end that was most likely to have moved during the move and added a new end.
    After testing, I found that I’d fixed the problem. Troubleshooting doesn’t go like that very often.
    For more about reterminating cables, watch the video above.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):
    Subscribe on YouTube
    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    11 min
  • Troubleshooting Techniques: Using a Fox and Hound Tool | Tech, No Babel

    Troubleshooting Techniques: Using a Fox and Hound Tool

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Using a Fox and Hound Tool
    One of the great things about troubleshooting is that you don’t always have to rely on tests you devise to figure out what’s wrong. Sometimes, there’s a tool that will help you.

    That’s what today’s show is all about. A fox and hound (also known as a tone generator and probe) is a tool that helps you find cables. You may know where each end is, but not know which end on one side goes with what cable.

    Sometimes, you can use a specially designed tool to take the trouble out of troubleshooting. That’s what a fox and hound tool does:Click To Tweet

    Basically, it’s pretty simple. You connect the fox (tone generator) to one end of the cable and use the hound (probe) to test to find out which cable it is on the other end.
    This is especially helpful in situations where the cable runs through a wall or conduit. Really, all that matters is that you know where both ends of the cable are. Once you know that, you can connect (or reconnect them correctly).
    Here are a couple of examples of this tool (affiliate links) if you need to buy one yourself:
    Triplett fox and hound
    Triplett home version of fox and hound (less expensive and not as durable)
    Another inexpensive fox and hound tool
    Watch the video for more on how you use this tool.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):
    Subscribe on YouTube
    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    8 min
  • Troubleshooting Techniques: Using a Multimeter | Tech, No Babel

    Troubleshooting Techniques: Using a Multimeter

    Listen to the audio:
    http://TrinityDigitalMedia.com/tnb
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Using a Multimeter
    Electricity is generally invisible in most electronics applications. If something goes terribly wrong, you’ll see a spark, but that generally lets the “magic smoke” out. Then it won’t work at all
    10 min
  • Troubleshooting Techniques: Making the invisible visible | Tech, No Babel

    Troubleshooting Techniques: Making the invisible visible

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Making the invisible visible
    Most of the time, electricity is invisible. If you see a spark, something has gone really wrong, except in rare exceptions. So how can you tell if electricity is flowing? You’ve got to figure out a way to make it visible.

    If electricity is mostly invisible, how can you see if it’s flowing? Try these tips:Click To Tweet

    Sometimes it’s as simple as using a special cable. There are cables that light up or have LEDs at one end or the other to show you they’re getting or sending power.
    If you’re testing an IR remote, try pulling out your smart phone and shooting the beam into the camera lens. While in camera mode, most of the time, if it’s working, you’ll see blinking on the screen.
    Finally, you can use a multimeter to see more information. With the first two tests, you could see if there was electricity, but with a meter, you can see how much, polarity, etc.
    We’ll talk more about these devices next week.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):
    Subscribe on YouTube
    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    8 min
  • Troubleshooting Techniques: Troubleshooting Remotely | Tech, No Babel

    Troubleshooting Techniques: Troubleshooting Remotely

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Troubleshooting Remotely
    1. Ask a lot of questions. Questions are your life line. The more you ask, the more information you’ll have.
    2. Look for evidence to rule out your hypothesis. It’s easy to jump to conclusions early. When you do so, though, you may miss the actual solution.
    3. Devise tests. How can you prove a problem or narrow down which one it is? Figure out a way to test and you’ll see.
    4. Use the best communications medium you can. If it’s text, it’s text. If it’s voice it’s voice. If it’s a video chat, use that. Try and choose the best medium for the situation.

    Sometimes you’ll need to troubleshoot remotely. If so, keep these things in mind:Click To Tweet

    5. Get the person on the other end to describe it to you like you can’t see (because you can’t). When you can’t see, get the person you’re working with to describe, in vivid detail what they see and prompt them where to look.
    6. If the person doesn’t believe you, devise a test to show them. They might be right and you might be, but figure out a way to show it for sure.
    7. Don’t tell them they’re wrong; help them realize it themselves. Show them the evidence and let them realize it for themselves. Don’t belittle. Make them feel important and smart, even if they’re not.
    14 min
  • Troubleshooting techniques: Paying in time and trouble | Tech, No Babel

    Troubleshooting techniques: Paying in time and trouble

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting techniques: Paying in time and trouble
    Most people only think of things costing money, but there are other costs.
    Consider:
    -how much something costs to replace.
    -how often you replace it.
    -how much maintenance does it require.
    -does it require more people to operate?
    -does it add unnecessary frustration to someone’s life?

    A lot of people think money is the only way to pay for things. Not true. Click here to see how else you’re paying:Click To Tweet

    Should you just replace it?
    -How much is the person who has to deal with it being paid to do so?
    -Are maintenance costs making repairs more costly than new?
    -Does a new one bring additional benefits that add to the calculation?
    For more on this, watch the video above.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):

    * Subscribe on YouTube
    * RSS feed
    * iTunes one-click subscription and don’t forget to rate the show there as well.
    *

    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    7 min
  • Troubleshooting Techniques: What to do with bad information | Tech, No Babel

    Troubleshooting Techniques: What to do with bad information

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: What to do with bad information
    Troubleshooting Techniques: What to do with bad information
    How to know you have bad information:
    -The problem doesn’t make sense.
    -Fixes don’t seem to work
    -The piece doesn’t normally break this way
    -The symptoms seem odd

    Troubleshooting can sometimes be hard, but when you get the wrong information, it’s much harder. Here’s how to fix that:Click To Tweet

    How to clear up bad information:
    -Ask about the location of the gear (is it close, is it in a well-lit area?).
    -Ask for a description of the problematic piece, including any displays, or UI.
    -Go back to basics, eliminate everything you can from the situation (aka “simple it down”)
    Look for anomalies:
    -What is present that shouldn’t be?
    -What’s missing that should be present?
    -What’s it doing that makes some of the information you’re getting wrong?
    Design a test to figure out what is happening.
    -How can you prove that the information you’re getting is bad?
    -If you’re talking to someone else, how can you help them save face, while getting the right information?
    For more, watch the video above.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):

    * Subscribe on YouTube
    * RSS feed
    * iTunes one-click subscription and don’t forget to rate the show there as well.
    *

    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    12 min
  • Troubleshooting techniques: Affirming the consequent | Tech, No Babel

    Troubleshooting techniques: Affirming the consequent

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting techniques: Affirming the consequent
    “Affirming the consequent” is a term in the study of logic. It means, basically, inferring one of many possible causes from the effect.

    Just because it could be the cause, doesn’t mean it is. Learn why here:Click To Tweet

    The problem with doing this in troubleshooting is that you immediately eliminate possible causes, concentrating, instead on one, which may or may not be the cause.
    Here’s an example from my own life. My microphone needs a battery to work. It also needs a working XLR cable. When I recently had trouble with the microphone not working, I thought to myself, “If the battery is dying, the microphone won’t work. The microphone doesn’t work. I’ll change out the battery.” That didn’t fix it. Why? It was a possible cause, but it wasn’t the cause. The actual cause was a short in the XLR cable that connected the microphone to the sound board.
    Affirming the consequent is like that. You think of a cause and get convinced that it’s the cause. It’s much better to do it the other way around. What are all the possible causes? Can you eliminate any of them based on other evidence. Then, and only then, do you try testing to see which is the cause.
    Keep in mind, though, that sometimes testing will fix a problem when you didn’t purposely address the cause. Moving a cable with a short while changing a battery may make it seem like the battery was the cause, when it was the cable.
    So, just because one thing seems to fix the problem, that doesn’t mean it did. You have to be vigilant and keep your eyes open for things that don’t fit.
    For more tips on avoiding this mistake, watch the video.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):

    * Subscribe on YouTube
    * RSS feed
    * iTunes one-click subscription and don’t forget to rate the show there as well.
    *

    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    13 min
  • Troubleshooting Techniques: Correlation vs Causation | Tech, No Babel

    Troubleshooting Techniques: Correlation vs Causation

    Listen to the audio:
    Join the conversation; call 1-877-763-3246, leave a comment below the video, or hit me up on Twitter (@PaulAlanClif)
    On today’s Tech, No Babel: Troubleshooting Techniques: Correlation vs Causation
    There’s a danger that you can fall into when you’re troubleshooting. It’s possible to start to think that things that are correlated in time are cause and effect. That may be the case, but it may not as well.

    Correlation isn’t causation. No matter which of the troubleshooting techniques you choose, be careful not to make that mistake.Click To Tweet

    Today’s featured image shows this mistake perfectly well. Time is the only relationship between use of Internet Explorer and the murder rate, but you may be tempted to think that they’re somehow linked because of the chart I’m showing here.
    Don’t. There’s no relationship between these things. Likewise, while “what changed” is a good question to ask, not all changes caused what happened after them. Maybe they did, but there should be a stronger correlation. If something is truly a cause, it should make sense. Work by a plumber is unlikely to cause a projector to quit working, but work by an electrician might.
    For more examples, watch the video above.
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate: http://patreon.com/paulalanclif
    If you’d like to chip in a few bucks, anything you do is appreciated. Just click this link to donate.
    About this show:
    If you do video or graphic design to advance your church’s mission, this show is for you.
    How to Subscribe to the show (for free):

    * Subscribe on YouTube
    * RSS feed
    * iTunes one-click subscription and don’t forget to rate the show there as well.
    *

    For more questions, comments, or snide remarks, comment below or contact me at:
    Facebook or Twitter
    More video can be found on YouTube.com
    Also check out my Google+ page
    13 min

About TNoB Archives - TrinityDigitalMedia.com

From the publisher's feed

Making church tech understandable.