Like me, I believe most people go about their business never to give a serious thought about their assumed private correspondence when using Gmail to email friends, colleagues and business associates.  As it turns out, your daily banter may not be so private after all.  A recent article in Fortune Magazine, “Judge Rejects Google Deal Over Email Scanning” caught my attention and an immediate thought dominated my curiosity…Google email and scanning scam.  

In essence, the article describes Googles’ agreement to change the way it scans incoming messages so that it no longer reads emails while they are in transit, but only when they are in someone's inbox! So, what exactly does that mean? Judge Koh, a San Francisco federal judge, said she's not so sure about that. Her ruling claims the settlement does not provide an adequate technical explanation of Google's workaround, which involves scanning in-transit emails for security purposes, and then later parsing them for advertising data. The judge also proposed a legal settlement to pay $2.2 million to lawyers, but nothing to consumers.

My interest in this story is not so much about the proposed settlements or the specific details about how Google or any of the web giants settle claims based on vague legal language. It is however, more about the naiveté of myself and perhaps many others that never question how the email scanning process really works. I wonder, do most of us really care that Gmail uses contents of our mail to display targeted ads?

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.

Outsourcing IT needs in the corporate world has become extremely popular because it is cost-efficient and it gives IT resources to companies that may not otherwise be able to afford them. Another positive side effect of IT outsourcing is that it has brought many technology jobs back to the United States.

As convenient and patriotic as IT outsourcing has become, it also have several limitations that have caused many companies to re-think the idea of funding their own internal IT group. It is important for a company to be completely familiar with these limitations before developing any kind of company policy in regards to IT.

The Customer Could Outgrow The Outsource Company

When an IT outsourcing company first takes on a new client, the relationship is beneficial to both sides. But things can start to get inconvenient for the client when the client's business starts to outgrow the capabilities of the IT outsource group.

An IT outsourcing company can become entrenched in the daily routine of its clients, which is great at first. But when the IT company can no longer keep pace with the growth of its clients, then the clients are stuck trying to find a new solution and keep track of its own IT assets at the same time.

The IT Outsourcing Company Lacks The Necessary Technical Expertise

IT outsourcing clients like to believe that their support company knows everything there is to know about computers and the Internet. But every IT support company has its areas of expertise and they have the technical areas where they are not quite as strong. If the client starts to experience needs from the areas where the IT outsourcing company is not so strong, then that can become a significant business issue.

This problem can be amplified if the client is a small business experiencing growth. An IT outsourcing company is not as likely to bring on new personnel for a smaller client, which leaves the client without a solution.

The Client Losses A Measure Of Control Over Its Data

No matter how large or successful an IT outsourcing company may be, there will always be the limitation of client security and the protection of critical customer data. All it takes is one rogue employee of the IT outsourcing company to compromise all of the client's critical data.

Some IT outsourcing companies have safeguards put in place to try and prevent client data compromise, but those safeguards are limited by how much access the IT company has to the client network. In most cases, that access has to be comprehensive for the IT outsourcing company to be able to do its job.

Outsourcing IT responsibilities can take a lot of stress off of a client and allow that client to operate his business by focusing on his core competencies. But there are limitations to IT outsourcing that could make it necessary for a client to do his own IT support and pay the extra costs.

The mainstay of a corporation is the data that it possesses. By data, I mean its customer base, information about the use of its products, employee roles and responsibilities, the development and maintenance of its product lines, demographics of supporters and naysayers, financial records, projected sales ... It is in the organization of this data that advancements to the bottom line are often realized i.e. the nuggets of gold are found. Defining what is important, properly cataloging the information, developing a comprehensive protocol to access and update this information and discerning how this data fits into the corporate venacular is basis of this data organization and may be the difference between moving ahead of the competition or being the one to fall behind.

Whenever we attempt to develop an Enterprise Rule Application, we must begin by harvesting the data upon which those rules are built. This is by no means an easy feat as it requires a thorough understanding of the business, industry, the players and their respective roles and the intent of the application. Depending upon the scope of this undertaking, it is almost always safe to say that no one individual is completely knowledgeable to all facets needed to comprise the entire application.

The intial stage of this endeavor is, obviously, to decide upon the intent of the application. This requires knowledge of what is essential, what is an add-on and which of all these requirements/options can be successfully implemented in the allotted period of time. The importance of this stage cannot be stressed enough; if the vision/goal cannot be articulated in a manner that all can understand, the knowledge tap will be opened to become the money drain. Different departments may compete for the same financial resources; management may be jockeying for their day in the sun; consulting corporations, eager to win the bid, may exaggerate their level of competency. These types of endeavors require those special skills of an individual or a team of very competent members to be/have a software architect, subject matter expert and business analyst.

Once the decision has been made and the application development stages have been defined, the next step is to determine which software development tools to employ. For the sake of this article, we will assume that the team has chosen an object oriented language such as Java and a variety of J EE components, a relationsional database and a vendor specific BRMS such as Blaze Advisor. Now, onto the point of this article.