VMWare Training Classes in Cincinnati, Ohio

Learn VMWare in Cincinnati, Ohio and surrounding areas via our hands-on, expert led courses. All of our classes are offered on an onsite, online and public instructor led basis. Here is a list of our current VMWare related training offerings in Cincinnati, Ohio: VMWare Training

Get pricing information (3 or more students may receive a discount)
Contact us to discuss our pricing structure for groups of 3 or more attendees.
Cincinnati  Upcoming Instructor Led Online and Public VMWare Training Classes
VMware vSphere 6.5 Optimize, Upgrade, Troubleshoot 25 February, 2019 - 1 March, 2019 $2850 Hartmann Software Group Training Registration
VMware vSphere 6.7 with ESXi and vCenter 28 January, 2019 - 1 February, 2019 $2850 Hartmann Software Group Training Registration

Course Directory [training on all levels]

Upcoming Classes

Blog Entries publications that: entertain, make you think, offer insight

What are the three most important things non-programmers should know about programming?
 
Written by Brian Knapp, credit and reprint CodeCareerGenius
 
 
Since you asked for the three most important things that non-programmers should know about, and I’ve spent most of my career working with more non-programmers than programmers, I have a few interesting things that would help.
 
Number One - It Is Impossible To Accurately Estimate Software Projects
 
No matter what is tried. No matter what tool, agile approach, or magic fairy dust people try to apply to creating software… accurately predicting software project timelines is basically impossible.
 
There are many good reasons for this. Usually, requirements and feature ideas change on a daily/weekly basis. Often it is impossible to know what needs to be done without actually digging into the code itself. Debugging and QA can take an extraordinary amount of time.
 
And worst of all…
 
Project Managers are always pushing for shorter timelines. They largely have no respect for reality. So, at some point they are given estimates just to make them feel better about planning.
 
No matter how much planning and estimation you do, it will be wrong. At best it will be directionally correct +/- 300% of what you estimated. So, a one year project could actually take anywhere between 0 and 5 years, maybe even 10 years.
 
If you think I’m joking, look at how many major ERP projects that go over time and over budget by many years and many hundreds of millions of dollars. Look at the F-35 fighter jet software issues.
 
Or in the small, you can find many cases where a “simple bug fix” can take days when you thought it was hours.
 
All estimates are lies made up to make everyone feel better. I’ve never met a developer or manager who could accurately estimate software projects even as well as the local weatherman(or woman) predicts the weather.
 
Number Two - Productivity Is Unevenly Distributed
 
What if I told you that in the average eight hour work day the majority of the work will get done in a 30 minute timeframe? Sound crazy?
 
Well, for most programmers there is a 30–90 minute window where you are extraordinarily productive. We call this the flow state.
 
Being in the flow state is wonderful and amazing. It often is where the “magic” of building software happens.
 
Getting into flow can be difficult. It’s akin to meditation in that you have to have a period of uninterrupted focus of say 30 minutes to “get in” the flow, but a tiny interruption can pull you right out.
 
Now consider the modern workplace environment. Programmers work in open office environments where they are invited to distract each other constantly.
 
Most people need a 1–2 hour uninterrupted block to get 30–90 minutes of flow.
 
Take the 8 hour day and break it in half with a lunch break, and then pile in a few meetings and all of a sudden you are lucky to get one decent flow state session in place.
 
That is why I say that most of the work that gets done happens in a 30 minute timeframe. The other 7–8 hours are spent being distracted, answering email, going to meetings, hanging around the water cooler, going to the bathroom, and trying to remember what you were working on before all these distractions.
 
Ironically, writers, musicians, and other creative professionals have their own version of this problem and largely work alone and away from other people when they are creating new things.
 
Someday the programming world might catch on, but I doubt it.
 
Even if this became obvious, it doesn’t sit well with most companies to think that programmers would be paid for an 8 hour day and only be cranking out code for a few hours on a good day. Some corporate middle manager would probably get the bright idea to have mandatory flow state training where a guru came in and then there would be a corporate policy from a pointy haired boss mandating that programmers are now required to spend 8 hours a day in flow state and they must fill out forms to track their time and notify their superiors of their flow state activities, otherwise there would be more meetings about the current flow state reports not being filed correctly and that programmers were spending too much time “zoning out” instead of being in flow.
 
Thus, programmers would spent 7–8 hours a day pretending to be in flow state, reporting on their progress, and getting all their work done in 30 minutes of accidental flow state somewhere in the middle of all that flow state reporting.
 
If you think I’m joking about this, I’m not. I promise you this is what would happen to any company of more than 2 employees. (Even the ones run by programmers.)
 
Number Three - It Will Cost 10x What You Think
 
Being a programmer, I get a lot of non-programmers telling me about their brilliant app ideas. Usually they want me to build something for free and are so generous as to pay me up to 5% of the profits for doing 100% of the work.
 
Their ideas are just that good.
 
Now, I gently tell them that I’m not interested in building anything for free.
 
At that point they get angry, but a few ask how much it will cost. I give them a reasonable (and very incorrect) estimate of what it would cost to create the incredibly simple version of their app idea.
 
Let’s say it’s some number like $25,000.
 
They look at me like I’m a lunatic, and so I explain how much it costs to hire a contract programmer and how long it will actually take. For example’s sake let’s say it is $100/hr for 250 hours.
 
To be clear, these are made up numbers and bad estimates (See Number One for details…)
 
In actuality, to build the actual thing they want might cost $250,000, or even $2,500,000 when it’s all said and done.
 
Building software can be incredibly complex and expensive. What most people can’t wrap their head around is the fact that a company like Google, Apple, or Microsoft has spent BILLIONS of dollars to create something that looks so simple to the end user.
 
Somehow, the assumption is that something that looks simple is cheap and fast to build.
 
Building something simple and easy for the end user is time consuming and expensive. Most people just can’t do it.
 
So, the average person with a brilliant app idea thinks it will cost a few hundred or maybe a few thousand dollars to make and it will be done in a weekend is so off the mark it’s not worth considering their ideas.
 
And programmers are too eager to play along with these bad ideas (by making bad estimates and under charging for their time) that this notion is perpetuated to the average non-programmer.
 
So, a good rule of thumb is that software will cost 10 times as much as you think and take 10 times as long to finish.
 
And that leads to a bonus point…
 
BONUS - Software Is Never Done
 
Programmers never complete a software project, they only stop working on it. Software is never done.
 
I’ve worked at many software companies and I’ve never seen a software project “completed”.
 
Sure, software gets released and used. But, it is always changing, being updated, bugs get fixed, and there are always new customer requests for features.
 
Look at your favorite software and you’ll quickly realize how true this is. Facebook, Instagram, Google Search, Google Maps, GMail, iOS, Android, Windows, and now even most video games are never done.
 
There are small armies of developers just trying to keep all the software you use every day stable and bug free. Add on the fact that there are always feature requests, small changes, and new platforms to deal with, it’s a treadmill.
 
So, the only way out of the game is to stop working on software. At that point, the software begins to decay until it is no longer secure or supported.
 
Think about old Windows 3.1 software or maybe old Nintendo Cartridge video games. The current computers and video game consoles don’t even attempt to run that software anymore.
 
You can’t put an old video game in your new Nintendo Switch and have it “just work”. That is what happens when you think software is done.
 
When programmers stop working on software the software starts to die. The code itself is probably fine, but all the other software keeps moving forward until your software is no longer compatible with the current technology.
 
So, those are the four most important things that non-programmers should know about programming. I know you asked for only three, so I hope the bonus was valuable to you as well.

It is said that spoken languages shape thoughts by their inclusion and exclusion of concepts, and by structuring them in different ways. Similarly, programming languages shape solutions by making some tasks easier and others less aesthetic. Using F# instead of C# reshapes software projects in ways that prefer certain development styles and outcomes, changing what is possible and how it is achieved.

F# is a functional language from Microsoft's research division. While once relegated to the land of impractical academia, the principles espoused by functional programming are beginning to garner mainstream appeal.

As its name implies, functions are first-class citizens in functional programming. Blocks of code can be stored in variables, passed to other functions, and infinitely composed into higher-order functions, encouraging cleaner abstractions and easier testing. While it has long been possible to store and pass code, F#'s clean syntax for higher-order functions encourages them as a solution to any problem seeking an abstraction.

F# also encourages immutability. Instead of maintaining state in variables, functional programming with F# models programs as a series of functions converting inputs to outputs. While this introduces complications for those used to imperative styles, the benefits of immutability mesh well with many current developments best practices.

For instance, if functions are pure, handling only immutable data and exhibiting no side effects, then testing is vastly simplified. It is very easy to test that a specific block of code always returns the same value given the same inputs, and by modeling code as a series of immutable functions, it becomes possible to gain a deep and highly precise set of guarantees that software will behave exactly as written.

Further, if execution flow is exclusively a matter of routing function inputs to outputs, then concurrency is vastly simplified. By shifting away from mutable state to immutable functions, the need for locks and semaphores is vastly reduced if not entirely eliminated, and multi-processor development is almost effortless in many cases.

Type inference is another powerful feature of many functional languages. It is often unnecessary to specify argument and return types, since any modern compiler can infer them automatically. F# brings this feature to most areas of the language, making F# feel less like a statically-typed language and more like Ruby or Python. F# also eliminates noise like braces, explicit returns, and other bits of ceremony that make languages feel cumbersome.

Functional programming with F# makes it possible to write concise, easily testable code that is simpler to parallelize and reason about. However, strict functional styles often require imperative developers to learn new ways of thinking that are not as intuitive. Fortunately, F# makes it possible to incrementally change habits over time. Thanks to its hybrid object-oriented and functional nature, and its clean interoperability with the .net platform, F# developers can gradually shift to a more functional mindset while still using the algorithms and libraries with which they are most familiar.

 

Related F# Resources:

F# Programming Essentials Training

A business rule is the basic unit of rule processing in a Business Rule Management System (BRMS) and, as such, requires a fundamental understanding. Rules consist of a set of actions and a set of conditions whereby actions are the consequences of each condition statement being satisfied or true. With rare exception, conditions test the property values of objects taken from an object model which itself is gleaned from a Data Dictionary and UML diagrams. See my article on Data Dictionaries for a better understanding on this subject matter.

A simple rule takes the form:

if condition(s)

then actions.

An alternative form includes an else statement where alternate actions are executed in the event that the conditions in the if statement are not satisfied:

if condition(s)

then actions

else alternate_actions

It is not considered a best prectice to write rules via nested if-then-else statements as they tend to be difficult to understand, hard to maintain and even harder to extend as the depth of these statements increases; in other words, adding if statements within a then clause makes it especially hard to determine which if statement was executed when looking at a bucket of rules. Moreoever, how can we determine whether the if or the else statement was satisfied without having to read the rule itself. Rules such as these are often organized into simple rule statements and provided with a name so that when reviewing rule execution logs one can determine which rule fired and not worry about whether the if or else statement was satisfied. Another limitation of this type of rule processing is that it does not take full advantage of rule inferencing and may have a negative performance impact on the Rete engine execution. Take a class with HSG and find out why.

Rule Conditions

data dictionary workThe 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.data dictionary

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.

Tech Life in Ohio

Ulysses S. Grant, Rutherford B. Hayes, James A. Garfield, Benjamin Harrison, William McKinley, William H. Taft, and Warren G. Harding, were all U.S. Presidents born in Ohio. The first recognized university in Ohio was Ohio University founded in 1804. It wasn?t long until the first interracial and coeducational college in the United States, Oberlin, was founded in 1833. The Buckeye State produced some interesting discoveries such as: Charles Goodyear discovering the process of vulcanizing rubber in 1839; Roy J. Plunkett inventing Teflon in 1938; and Charles Kettering inventing the automobile self-starter in 1911.
If you do build a great experience, customers tell each other about that. Word of mouth is very powerful. Jeff Bezos Amazon.com founder
other Learning Options
Software developers near Cincinnati have ample opportunities to meet like minded techie individuals, collaborate and expend their career choices by participating in Meet-Up Groups. The following is a list of Technology Groups in the area.
Fortune 500 and 1000 companies in Ohio that offer opportunities for VMWare developers
Company Name City Industry Secondary Industry
Nationwide Insurance Company Columbus Financial Services Insurance and Risk Management
Owens Corning Toledo Manufacturing Concrete, Glass, and Building Materials
FirstEnergy Corp Akron Energy and Utilities Gas and Electric Utilities
The Lubrizol Corporation Wickliffe Manufacturing Chemicals and Petrochemicals
Sherwin-Williams Cleveland Retail Hardware and Building Material Dealers
Key Bank Cleveland Financial Services Banks
TravelCenters of America, Inc. Westlake Retail Gasoline Stations
Dana Holding Company Maumee Manufacturing Automobiles, Boats and Motor Vehicles
O-I (Owens Illinois), Inc. Perrysburg Manufacturing Concrete, Glass, and Building Materials
Big Lots Stores, Inc. Columbus Retail Department Stores
Limited Brands, Inc. Columbus Retail Clothing and Shoes Stores
Cardinal Health Dublin Healthcare, Pharmaceuticals and Biotech Healthcare, Pharmaceuticals, and Biotech Other
Progressive Corporation Cleveland Financial Services Insurance and Risk Management
Parker Hannifin Corporation Cleveland Manufacturing Manufacturing Other
American Financial Group, Inc. Cincinnati Financial Services Insurance and Risk Management
American Electric Power Company, Inc Columbus Energy and Utilities Gas and Electric Utilities
Fifth Third Bancorp Cincinnati Financial Services Banks
Macy's, Inc. Cincinnati Retail Department Stores
Goodyear Tire and Rubber Co. Akron Manufacturing Plastics and Rubber Manufacturing
The Kroger Co. Cincinnati Retail Grocery and Specialty Food Stores
Omnicare, Inc. Cincinnati Healthcare, Pharmaceuticals and Biotech Pharmaceuticals
The Procter and Gamble Company Cincinnati Consumer Services Personal Care

the hsg library depth in learning

training details locations, tags and why hsg

the hartmann software group advantage
A successful career as a software developer or other IT professional requires a solid understanding of software development processes, design patterns, enterprise application architectures, web services, security, networking and much more. The progression from novice to expert can be a daunting endeavor; this is especially true when traversing the learning curve without expert guidance. A common experience is that too much time and money is wasted on a career plan or application due to misinformation.

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.
    1. We have provided software development and other IT related training to many major corporations in Ohio since 2002.
    2. 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 VMWare programming
  • Get your questions answered by easy to follow, organized VMWare experts
  • Get up to speed with vital VMWare 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…
learn more
page tags
what brought you to visit us
Cincinnati, Ohio VMWare Training , Cincinnati, Ohio VMWare Training Classes, Cincinnati, Ohio VMWare Training Courses, Cincinnati, Ohio VMWare Training Course, Cincinnati, Ohio VMWare Training Seminar