Let’s face it, fad or not, companies are starting to ask themselves how they could possibly use machine learning and AI technologies in their organization. Many are being lured by the promise of profits by discovering winning patterns with algorithms that will enable solid predictions… The reality is that most technology and business professionals do not have sufficient understanding of how machine learning works and where it can be applied.  For a lot of firms, the focus still tends to be on small-scale changes instead of focusing on what really matters…tackling their approach to machine learning.

In the recent Wall Street Journal article, Machine Learning at Scale Remains Elusive for Many Firms, Steven Norton captures interesting comments from the industry’s data science experts. In the article, he quotes panelists from the MIT Digital Economy Conference in NYC, on businesses current practices with AI and machine learning. All agree on the fact that, for all the talk of Machine Learning and AI’s potential in the enterprise, many firms aren’t yet equipped to take advantage of it fully.

Panelist,  Michael Chui, partner at McKinsey Global Institute states that “If a company just mechanically says OK, I’ll automate this little activity here and this little activity there, rather than re-thinking the entire process and how it can be enabled by technology, they usually get very little value out of it. “Few companies have deployed these technologies in a core business process or at scale.”

Panelist, Hilary Mason, general manager at Cloudera Inc., had this to say, “With very few exceptions, every company we work with wants to start with a cost-savings application of automation.” “Most organizations are not set up to do this well.”

Sage wisdom states that there are two sides to every coin. This timeless wisdom will be borne out in spades with Windows 8/RT. Let's get into the dark side first.

If your users are veterans of Windows it is safe bet they are going to take one look at Windows 8 and scream blasphemy. Users whose brains are geared towards visual learning will undoubtedly yell the loudest and longest.

There's a good reason for this. Mick Jagger brought his band to the Redmond campus, performing live "Start Me Up" in the summer of 1995 (it was a great show). This heralded in the abandonment of program icons sitting on the desktop and introduced the now legacy Start button.

Ending the life of the 17-year-old start button is not going to go well with some users.

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.

C# PROGRAMMING –MAIN DESIGN GOALS

C# is a popular programming language these days, and it was designed from inception to provide a simple, clean, general purpose programming language for those intending to work within the confines of Microsoft’s .NET framework.  Since then, it has been approved as one of the standard languages by both ECMA and ISO, making C# programming an essential tool in every programmers’ kit.

Different languages have different uses and specialties, and C# was designed for programmers to be able to use it to create different components for use in software that would be deployed and distributed en masse, to live use environments.  This means that designers had to really put an emphasis on making the actual source code extremely compatible and portable.  Those already familiar with C or C++ should definitely notice this emphasis.

Another particular point of emphasis during design was focus on internationalization of the language; it was intended from inception to be available all over the world, and to see all sorts of different implementations based on variance in regional programming technique.  The resultant use should help the language develop sophistication as it is refined throughout different versions.