No matter what type of business you’re in, boosting your bottom line is always in the back of your mind. In a rough economy, it can be tempting to focus too much on pulling in more money and not enough on containing it from within.

That’s right, containing it. You have the potential to lose hundreds of thousands of dollars every year right under your nose from something as simple as lack of or ineffective computer training.

How much do the employees you have working for you right now really understand about technology? How good is your IT tech department? Technology changes faster than a blink of an eye and oftentimes, businesses struggle to keep their top employees trained.

With millions of dollars being lost to Internet espionage, file corruption and other computer crimes, staying on top of changes is essential. Recently, online learning centers have been emerging as the go-to method for quick and inexpensive learning. Unfortunately, this type of computer learning isn’t always the best solution.

Straight up and full disclosure. I'm prejudiced. As a research assignment, the heading is a joke. I'll give you the answer in two words, and then tell you why.

How does HTML 5 compare with flash? Answer: it doesn't.

Lest you think I dislike Adobe's Flash, let's put the cards on the table. I loved Flash. Long before Adobe was Adobe, they had a competitor called Macromedia. Adobe bought that firm. That made my life simpler. I only had to work with one vendor.

Flash was a pretty compelling solution. I used it to mimic operations in Windows to prepare people for the CompTIA exams. The only bugaboo was that dang right-click stuff. A little bit of code from the Microsoft Visual Studio .Net let me flip the left and right mouse buttons so that the right mouse button instead of controlling the Flash player, emulated doing a right-click in the Windows operating system.

Recently, I asked my friend, Ray, to list those he believes are the top 10 most forward thinkers in the IT industry.  Below is the list he generated. 

Like most smart people, Ray gets his information from institutions such as the New York Times, the Wall Street Journal, the Huffington Post, Ted Talks ...  Ray is not an IT expert; he is, however, a marketer: the type that has an opinion on everything and is all too willing to share it.  Unfortunately, many of his opinions are based upon the writings/editorials of those attempting to appeal to the reading level of an 8th grader.  I suppose it could be worse.  He could be referencing Yahoo News, where important stories get priority placement such as when the voluptuous Kate Upton holds a computer close to her breasts.

Before you read further, note that missing from this list and not credited are innovators: Bill Joy, Dennis Ritchie, Linus Torvalds, Alan Turing, Edward Howard Armstrong, Peter Andreas Grunberg and Albert Fent, Gottfried Wilhelm Leibniz/Hermann Grassmann ... You know the type:  the type of individual who burns the midnight oil and rarely, if ever, guffaws over their discoveries or achievements.

It’s the eternal conundrum of a hiring manager – you have to hire for every single position in the company without any first-hand experience. How to do it? If you can have a trusted programmer sit in on the interview, that’s ideal, of course. But what if you’re hiring your first programmer? Or what if you’re hiring a freelancer? Or what if company policy dictates that you’re the only person allowed to do the interviewing? Well, in that case, you need some helpful advice and your innate bullshit detector. We questioned programmers and hiring managers and compiled a list of dos and don’ts. Here are some things to ask when interviewing programmers:

Past Experience

Ask the programmer about the biggest disaster of his career so far, and how he handled it. Did he come in at midnight to fix the code? Was he unaware of the problem until someone brought it up? Did someone else handle it?  According to our programmer sources, “Anyone worth their salt has caused a major meltdown. If they say they haven’t, they’re lying. Or very, very green.” Pushing a code with bugs in it isn’t necessarily bad. Not handling it well is bad.

As usual, your biggest asset is not knowing the field, it is knowing people. Asking about career disasters can be uncomfortable, but if the interviewee is experienced and honest then she won’t have a problem telling you about it, and you will get an idea of how she handles mishaps. Even if you don’t understand what the disaster was or how it was fixed, you should be able to tell how honest she’s being and how she handles being put on the spot.