Troubleshooting techniques: What it can do and what it’s designed to | Tech, No Babel

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 it can do and what it’s designed to

It’s valuable to know everything a piece can do, even if it’s not designed to do it. When you’re troubleshooting, you should check if the system depends on making a piece of equipment do something it’s not supposed to do because sometimes that will cause a failure later.

[tweet “Sometimes you can stretch what something can do; other times, that’s the problem. Watch this to see what I mean:”]

Other times, by stretching the capabilities of a piece, you can do more than your budget allows. The trade out is that sometimes it won’t be as stable as the right piece or sometimes you’ll spend more time and effort making the wrong piece work than buying the right piece. So, do the research to see which is the case.

For more, 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:

Tech, No Babel is a weekly podcast premiering every Thursday at 11a eastern (-4 UTC), 8a pacific on Watch it and join the chat then.

But, if you miss the live show, I’ll put up the edited show later (usually on the same day) right here.

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):

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

Comments are closed.