Your search did not yield any results.
Course Directory [training on all levels]
- .NET Classes
- Agile/Scrum Classes
- Ajax Classes
- Android and iPhone Programming Classes
- Blaze Advisor Classes
- C Programming Classes
- C# Programming Classes
- C++ Programming Classes
- Cisco Classes
- Cloud Classes
- CompTIA Classes
- Crystal Reports Classes
- Design Patterns Classes
- DevOps Classes
- Foundations of Web Design & Web Authoring Classes
- Git, Jira, Wicket, Gradle, Tableau Classes
- IBM Classes
- Java Programming Classes
- JBoss Administration Classes
- JUnit, TDD, CPTC, Web Penetration Classes
- Linux Unix Classes
- Machine Learning Classes
- Microsoft Classes
- Microsoft Development Classes
- Microsoft SQL Server Classes
- Microsoft Team Foundation Server Classes
- Microsoft Windows Server Classes
- Oracle, MySQL, Cassandra, Hadoop Database Classes
- Perl Programming Classes
- Python Programming Classes
- Ruby Programming Classes
- Security Classes
- SharePoint Classes
- SOA Classes
- Tcl, Awk, Bash, Shell Classes
- UML Classes
- VMWare Classes
- Web Development Classes
- Web Services Classes
- Weblogic Administration Classes
- XML Classes
- Introduction to Spring 5 (2022)
15 July, 2024 - 17 July, 2024 - Ruby Programming
19 August, 2024 - 21 August, 2024 - Go Language Essentials
29 July, 2024 - 1 August, 2024 - Introduction to C++ for Absolute Beginners
14 October, 2024 - 15 October, 2024 - VMware vSphere 8.0 with ESXi and vCenter
19 August, 2024 - 23 August, 2024 - See our complete public course listing
Blog Entries publications that: entertain, make you think, offer insight
I’ve been a technical recruiter for several years, let’s just say a long time. I’ll never forget how my first deal went bad and the lesson I learned from that experience. I was new to recruiting but had been a very good sales person in my previous position. I was about to place my first contractor on an assignment. I thought everything was fine. I nurtured and guided my candidate through the interview process with constant communication throughout. The candidate was very responsive throughout the process. From my initial contact with him, to the phone interview all went well and now he was completing his onsite interview with the hiring manager.
Shortly thereafter, I received the call from the hiring manager that my candidate was the chosen one for the contract position, I was thrilled. All my hard work had paid off. I was going to be a success at this new game! The entire office was thrilled for me, including my co-workers and my bosses. I made a good win-win deal. It was good pay for my candidate and a good margin for my recruiting firm. Everyone was happy.
I left a voicemail message for my candidate so I could deliver the good news. He had agreed to call me immediately after the interview so I could get his assessment of how well it went. Although, I heard from the hiring manager, there was no word from him. While waiting for his call back, I received a call from a Mercedes dealership to verify his employment for a car he was trying to lease. Technically he wasn’t working for us as he had not signed the contract yet…. nor, had he discussed this topic with me. I told the Mercedes office that I would get back to them. Still not having heard back from the candidate, I left him another message and mentioned the call I just received. Eventually he called back. He wanted more money.
I told him that would be impossible as he and I had previously agreed on his hourly rate and it was fine with him. I asked him what had changed since that agreement. He said he made had made much more money in doing the same thing when he lived in California. I reminded him this is a less costly marketplace than where he was living in California. I told him if he signed the deal I would be able to call the car dealership back and confirm that he was employed with us. He agreed to sign the deal.
I suspect that many of you are familiar with the term "hard coding a value" whereby the age of an individual or their location is written into the condition (or action) of a business rule (in this case) as shown below:
if customer.age > 21 and customer.city == 'denver'
then ...
Such coding practices are perfectly expectable provided that the conditional values, age and city, never change. They become entirely unacceptable if a need for different values could be anticipated. A classic example of where this practice occurred that caused considerable heartache in the IT industry was the Y2K issue where dates were updated using only the last 2 digits of a four digit number because the first 2 digits were hard-coded to 19 i.e. 1998, 1999. All was well provided that the date did not advance to a time beyond the 1900’s since no one could be certain of what would happen when the millennia arrived (2000). A considerably amount of work (albeit boring) and money, approximately $200 billion, went into revising systems by way of software rewrites and computer chip replacements in order to thwart any detrimental outcomes. It is obvious how a simple change or an assumption can have sweeping consequences.
You may wonder what Y2K has to do with Business Rule Management Systems (BRMS). Well, what if we considered rules themselves to be hard-coded. If we were to write 100s of rules in Java, .NET or whatever language that only worked for a given scenario or assumption, would that not constitute hard-coded logic? By hard-coded, we obviously mean compiled. For example, if a credit card company has a variety of bonus campaigns, each with their own unique list of rules that may change within a week’s time, what would be the most effective way of writing software to deal with these responsibilities?
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.
Disruptive technologies such as hand-held devices, cloud computing and social media are rattling the foundations upon which traditional businesses are built. Enterprise customers have grown smarter at ensuring the latest technological trends work in their favor. Everyone is trying to zero in on their core competencies by employing commodity services to run their business.
Likewise, enterprise application vendors need to zero in on their core competencies and enhance more value to the businesses of their clientele by leveraging standards-based commodity services, such as IaaS and PaaS, provided by leaders in those segments (e.g. Amazon EC2, Google Cloud Platform etc.).
What else enterprises need to do is learn to adopt new and emerging technologies such as cloud, utility and social computing to build on them to penetrate new market avenues.
New small and medium-sized entrants into the market are constantly challenging enterprises given their ability to rapidly turnaround and address the requirements of the customers in a cost-effective manner. Additionally, these new advancements also affect how enterprises create, deploy, and manage solutions and applications. If you take the example of Force.com, for instance, you find that it’s a common war zone for enterprise application vendors to furnish SME markets with their applications, with the new entrants mostly having an edge.
training details locations, tags and why hsg
The Hartmann Software Group understands these issues and addresses them and others during any training engagement. Although no IT educational institution can guarantee career or application development success, HSG can get you closer to your goals at a far faster rate than self paced learning and, arguably, than the competition. Here are the reasons why we are so successful at teaching:
- Learn from the experts.
- We have provided software development and other IT related training to many major corporations since 2002.
- Our educators have years of consulting and training experience; moreover, we require each trainer to have cross-discipline expertise i.e. be Java and .NET experts so that you get a broad understanding of how industry wide experts work and think.
- Discover tips and tricks about programming
- Get your questions answered by easy to follow, organized experts
- Get up to speed with vital programming tools
- Save on travel expenses by learning right from your desk or home office. Enroll in an online instructor led class. Nearly all of our classes are offered in this way.
- Prepare to hit the ground running for a new job or a new position
- See the big picture and have the instructor fill in the gaps
- We teach with sophisticated learning tools and provide excellent supporting course material
- Books and course material are provided in advance
- Get a book of your choice from the HSG Store as a gift from us when you register for a class
- Gain a lot of practical skills in a short amount of time
- We teach what we know…software
- We care…