I remember the day like it was yesterday. Pac Man had finally arrived on the Atari 2600.  It was a clear and sunny day, but it was slightly brisk. My dad drove us down to the video store about three miles from our Michigan house. If I remember correctly, the price for the game was $24.99.  It was quite expensive for the day, probably equaling a $70 game in today’s market, but it was mine. There *was* no question about it. If you purchase a game, it’s your game… right?

You couldn’t be more wrong.  With all the licensing agreements in games today, you only purchase the right to play it. You don’t actually “own” the game. 

Today, game designers want total control over the money that comes in for a game. They add in clauses that keep the game from being resold, rented, borrowed, copied, etc. All of the content in the game, including the items you find that are specifically for you, are owned by the software developer. Why, you ask, do they do this? It’s all about the money.

This need for greed started years ago, when people started modifying current games on the market. One of the first games like this was Doom. There were so many third part mods made, but because of licensing agreement, none of these versions were available for resale. The end user, or you, had to purchase Doom before they could even install the mod.  None of these “modders” were allowed to make any money off their creation.

Since its foundation, HSG has been a leader in Business Rule Management Systems Training and Consulting services by way of the Blaze Advisor Rule Engine.  Over the years we have provided such services to many of the worlds largest corporations and government institutions whose respective backgrounds include credit card processing, banking, insurance, health and medicine and more, much more.  Such training and consulting services have included:

Create a wrapper object model in either Java, .NET or XML

Identify and catalog business rules

Develop a rule architecture within Blaze Advisor that isolates rule repositories as they relate to functionality and corporate policies

Configure, develop and implement a variety of interfaces to the rule engine from disparate systems ranging from mainframe applications written in Cobol to UNIX/Windows applications using Enterprise Java Beans, Windows Services, Web Services, Fat Clients, Java Messaging Services and Web Applications.

Review and update code to boost efficiency either by way of

    Removing functions calls within conditional statements

    Ensuring that database calls are essential or can be rearchitected in some other manner

    Employing the rete algorithm where necessary

    Paring down extensively large class models

    Deploying such appliations in multi-threaded systems

·         ...

Call us if you:

    are in need of Blaze Advisor Expertise
    are developing SMEs in Blaze
    want to speak directly with an expert (no placement agencies)
    want an affordable alternative to FICO
    want to work with an industry leader

The iconic software company that is based in King County Washington has been getting almost universally slammed from it's recent Los Angeles press announcement about its entry into the hardware business with the convertible laptop/tablet known as Surface.

Certainly I can see the point that it is now competing with its hardware vendors/partners. Intel has done a good job in the arena creating 'reference designs' without competing with its partners.

There is another viewpoint which seems to be ignored. The cold facts are Microsoft is a public company. This puts Microsoft in a legal position of doing the most it can to return value to its shareholders. Failure to do so means somebody is going to jail.

Microsoft has a vision, which at the end of the day is, a certain way to get enough people to see enough value to hand over their money, to fulfill their fiduciary duty.

Learning SQL development can seem like an overwhelming task at first. However, mastering just a few key points will help ease your way through 80 percent of the day-to-day challenges when writing stored procedures and solving common problems. Here are three important SQL development factors to keep in mind:

Outer Joins
One of the most crucial things to understand in SQL server are joins. Joins are a way to retrieve data from two or more tables based on logical relationships between them. Joins dictate how Microsoft SQL Server ought to use data from one table to select the rows in another table.

In my experience inner joins are intuitive while outer joins can present additional hours of grief by overlooking associations in the other table(s). The outer join is the key to answering questions about what the database does not have. For example, if you need to make a query to display all the students who are without report-cards, you’ll need a left join to get all students coupled with a “where clause” to return the ones who have nulls for their report card table columns in the results.

Many talented Java script programmers have muddled through the SQL Server by deficient coding around the inner join. As a result, their queries can take five hours to run, whereas, properly written left joins, can take only two seconds to run.

Aggregation
Grouping results comes up in SQL a lot more than you might think. Knowing how to write a query when answering questions such as, “What’s the average grade for each teacher’s student list?” is invaluable. This kind of question cannot be answered with a single table or solely by joins.  You’ll often find you need to use joins in conjunction with group by statements. Always write the raw query first and then look at the results. Next, you have to figure out the best way to group them, rewrite your select clause and add a group by clause in the end.

Digging Through Data
I find this is the most lacking skill in many programmers. In fact, many otherwise-talented programmers holding Master’s Degrees fail to get jobs because they couldn’t analyze rows of data objectively during interviews. It’s just something that’s not taught but is crucial to get under you belt. Why? Eventually, some query is not going to perform as you may expect. And, the only way to find discrepancies is to look at rows of data, identify what join isn’t finding a match or where bad data is throwing things into chaos. Get familiar with how joins actually work, even if you have to manually walk through the logic of a large stored procedure’s tree of joins. It’s boring and time-consuming but absolutely necessary.

Take the time to master the core skills that will make you a successful SQL Programmer and avoid queries that run for five hours!