The short answer is, yes and no. It depends upon who you are. The purpose of this entry is to help you determine, yes or no.

Full disclosure. This entry is created on a Mac mini. And doing so on Windows 8 (Release Preview). If you are a developer, in my humble opinion you need to test on all platforms you expect your app to run or you are not much of a developer.

To be successful you need to leave politics in geographical territory known as Washington DC. My definition of that is: 14 mi.² of real estate surrounded by reality.

Only in politics can we afford to take sides. Those of us in IT, especially developers need to do our best to be all things to all people. Certainly this is a technical impossibility. However in our game we can get some points for at least being serviceable if not outstanding.

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

Much of success is about performance. It’s about what we do and what we are able to inspire others to do. There are some simple performance principles I have learned in my life, and I want to share them with you.  They really bring success, and what it takes to be successful, into sharp focus. They are also the basis for developing and maintaining an expectation of success.

The Five Principles of Performance

1. We generally get from ourselves and others what we expect. It is a huge fact that you will either live up or down to your own expectations. If you expect to lose, you will. If you expect to be average, you will be average. If you expect to feel bad, you probably will. If you expect to feel great, nothing will slow you down. And what is true for you is true for others. Your expectations for others will become what they deliver and achieve. As Gandhi said, “Be the change you wish to see in the world.”

2. The difference between good and excellent companies is training. The only thing worse than training employees and losing them is to not train them and keep them! A football team would not be very successful if they did not train, practice, and prepare for their opponents. When you think of training as practice and preparation, it makes you wonder how businesses survive that do not make significant training investments in their people.

Actually, companies that do not train their people and invest in their ability don’t last. They operate from a competitive disadvantage and are eventually gobbled up and defeated in the marketplace. If you want to improve and move from good to excellent, a good training strategy will be the key to success.

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.