10Nov
Basic Diagnoses For When Your Technology Is Ill

RXkeys

Technology is exciting! We’ve expressed this sentiment before, and we’ll certainly express it again. It’s why we do what we do, and we thrive on this excitement. But one of the biggest wrenches in the gears that is one’s excitement over their technology is when, well, it just doesn’t work!

Uh Oh!

Now, our iterative development process prevents this right from the start. But we can’t really account for the existing web or application based technology that we didn’t engineer ourselves. As often as we are asked for a whole new from-the-ground-up solution, we are asked to take a look at existing sites or apps and fix them. We are your ‘technology doctors,’ after all.

And this is fine. We’re always willing to take a look and help. But along the lines of the classic IT joke, “did you turn it off and back on again?” (which, by the way, should resolve approximately 50% of your technical problems) there are some simple issues you can troubleshoot yourselves before seeking out a professional. Not that we’re in the business of turning down business, but your issue may be so simple that you could diagnose and cure it yourself faster than you could explain to us what’s not working.

So without further ado, here are a few basic troubles you may encounter with your web-based technology.

Server Side

Often a problem may be what we call a server side issue. This typically manifests when information that is either inputted by a user and/or outputted by your website aren’t quite jiving properly. In the interest of over-simplifying, web based information typically goes through a process that looks something like this:

  1.   Information is entered somewhere by someone (a user, or the application itself).
  2.   Something happens to that information (sometimes that “something” is, in fact, nothing).
  3.   The new information, even if unchanged, is then displayed and/or stored somewhere.

So if you’re noticing issues pertaining to the input, output, or the changes that take place in between, you may be able to deduce the issue is server side. And if you’re really wearing your detective hat, you may be able to discern during which of the above 3 steps problems are occurring. And that can provide further clues as to what the problem may be.

Browsers? Wowsers!

Has this ever happened to you?

Person 1: I opened this thing and it doesn’t work!
Person 2: That’s weird, it works fine for me.

Whether you’re Person 1 or Person 2 in this scenario, you’re suddenly acutely aware that a problem exists. And when this happens, one of the first things you want to check is on which web browsers each party is attempting to open their “thing.” Not all web browsers are created equal! Now, I don’t want to call out any browsers specifically, but experienced web EXPLORERS may be aware of some of the more frequent offenders.

When we are developing new web-based sites or apps, a critical part of the process is testing on all existing major web browsers. Unfortunately, not all developers are created equal either. And disparities as illustrated above can often be the result of a browser conflict. If you suspect this may be what’s going on, this concept should guide your troubleshooting efforts. And should you determine that, yes, you’ve EXPLORERED the options and it does seem to be a browser issue, here is the recommended recourse:

  1. www.google.com
  2. www.curotec.com/contact

 

Overload!

Sometimes a website will load slllooooowwwwwlllyyyyyyy, or won’t even load at all. This is commonly a symptom of an overloaded server. This can happen when there is too much traffic, too many users, or too much information being processed by your server. Unfortunately(or fortunately, depending on your outlook), the repair in this case may not be a matter of adjusting code syntax, but of upgrading your server(s).

If you’ve got servers to spare, and the staff to configure and deploy them, this may be an open and shut case, troubleshooting-wise. If not, you may want to consult an expert. Of all of the technological issues discussed, server overload can often be one of the easiest to diagnose, but taxing to repair. But at least it is better to know what kind of problem is plaguing your site or app than to have it remain a mystery.

Prescription…

So there you have a decent basis for exploration when you’re faced with the ol’, “It’s not working!” conundrum. You’ll notice that even if you can now identify some of these issues, you’re still going to want to end up consulting an expert to help resolve them. It’s just the nature of the beast when dealing with technology (especially technology that wasn’t originally developed by Curotec, wink wink).

Technology excites us, and it should excite you. But of course, functioning technology is far more exciting than the alternative. And while we would just as soon see you troubleshoot the equivalent of, “turn it off, turn it back on” kinds of problems yourself, it should be noted that our website and app development and creation initiatives are painstakingly executed so as to avoid all but the nittiest grittiest technical issues. And even those we can easily find and eliminate. The point is, if you’ve got a technology based nut that you just can’t crack, let us know and we can help. Or if you’re in the need of either a brand new or replacement site or app, also let us know and we can help. Preventative medicine is often the best, but even if your existing technology is feeling under the weather, let us know today. Because when it comes to the ills of your online presence, Curotec really is just what the doctor ordered.