In the ever changing landscape of software programming, it is not surprising that developers and employees have a different set of preferences for desired skills.  However the number one language that developers want to learn according to a survey of developers by technical recruiter, Hacker Rank is Python. This is not a surprise considering that Python has been in demand for several years and programmers tend to really enjoy this language for clear syntax, good OOP support and great shortcuts. Python, named “the language of the year” in 2007 and 2010 in the TIOBE Index and has climbed to #4 status in May of 2018.

According to the study, employers want developers who:

-  Have problem-solving skills, such as the ability to break down large, complex problems.
- Are proficient in their programming language and debugging.
- Can design systems.
- Can optimize performance.
- Have experience in reviewing and testing code.
- Are proficient in database design

Surprisingly, formal education is not the deciding factor when it comes to what companies care about the most. People with computer degrees or certifications on a resume are not necessarily a first choice for hiring managers. Others that have years of experience even if those individuals are partially self-taught in the field stand to be taken seriously in the field.   For those individuals with a passion to learn and master a skill, there are ample opportunities with smaller to mid-sized companies.

Some interesting FAQ’s from the study:

    On average, developers know 4 languages, and they aspire to learn 4 more.
    Younger developers between 18 and 24 plan to learn 6 languages.
    Folks older than 35 only plan to learn and additional 3 languages.
    The top languages developers said they will learn were, Go, Python, Scala, Kotlin, and Ruby.
    There is a large gap between employers seeking developers that know React than there are folks that can do it.

So, Why Learn Python?
It is now the most popular introductory teaching language in U.S. universities.  Python is easy to use, powerful, and versatile, making it a great choice for beginners and experts alike. It allows you to think like a programmer and not waste time understanding difficult syntax that other programming languages can command. And, because of its rapid growth, many developers contribute to the Python community and share Python libraries making creativity that much more a reality

Another blanket article about the pros and cons of Direct to Consumer (D2C) isn’t needed, I know. By now, we all know the rules for how this model enters a market: its disruption fights any given sector’s established sales model, a fuzzy compromise is temporarily met, and the lean innovator always wins out in the end.

That’s exactly how it played out in the music industry when Apple and record companies created a digital storefront in iTunes to usher music sales into the online era. What now appears to have been a stopgap compromise, iTunes was the standard model for 5-6 years until consumers realized there was no point in purchasing and owning digital media when internet speeds increased and they could listen to it for free through a music streaming service.  In 2013, streaming models are the new music consumption standard. Netflix is nearly parallel in the film and TV world, though they’ve done a better job keeping it all under one roof. Apple mastered retail sales so well that the majority of Apple products, when bought in-person, are bought at an Apple store. That’s even more impressive when you consider how few Apple stores there are in the U.S. (253) compared to big box electronics stores that sell Apple products like Best Buy (1,100) Yet while some industries have implemented a D2C approach to great success, others haven’t even dipped a toe in the D2C pool, most notably the auto industry.

What got me thinking about this topic is the recent flurry of attention Tesla Motors has received for its D2C model. It all came to a head at the beginning of July when a petition on whitehouse.gov to allow Tesla to sell directly to consumers in all 50 states reached the 100,000 signatures required for administration comment. As you might imagine, many powerful car dealership owners armed with lobbyists have made a big stink about Elon Musk, Tesla’s CEO and Product Architect, choosing to sidestep the traditional supply chain and instead opting to sell directly to their customers through their website. These dealership owners say that they’re against the idea because they want to protect consumers, but the real motive is that they want to defend their right to exist (and who wouldn’t?). They essentially have a monopoly at their position in the sales process, and they want to keep it that way. More frightening for the dealerships is the possibility that once Tesla starts selling directly to consumers, so will the big three automakers, and they fear that would be the end of the road for their business. Interestingly enough, the big three flirted with the idea of D2C in the early 90’s before they were met with fierce backlash from dealerships. I’m sure the dealership community has no interest in mounting a fight like that again. 

To say that the laws preventing Tesla from selling online are peripherally relevant would be a compliment. By and large, the laws the dealerships point to fall under the umbrella of “Franchise Laws” that were put in place at the dawn of car sales to protect franchisees against manufacturers opening their own stores and undercutting the franchise that had invested so much to sell the manufacturer’s cars.  There’s certainly a need for those laws to exist, because no owner of a dealership selling Jeeps wants Chrysler to open their own dealership next door and sell them for substantially less. However, because Tesla is independently owned and isn’t currently selling their cars through any third party dealership, this law doesn’t really apply to them. Until their cars are sold through independent dealerships, they’re incapable of undercutting anyone by implementing D2C structure.

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

F#, which is usually pronounced as F sharp is one of the newly launched and rapidly developing programming languages.  It has recently become focus of attention due to its quick advancement to the 12^th position in the recent TIOBE index and the overall rise in popularity.

What is F#?

F# is an open source, functional and object oriented programming language which is available in cross platform. It was developed by a company called F# software foundation with help of Microsoft and other open contributors. F# runs on Linux, windows, iOS, Android and the GPUs and HTML as well. It is a mature programming language which helps the users as well as the organizations to solve the complex problems in a much simpler way with easy code. With its wide range of usage in the specialist and application areas, it is proving itself to be a worthy contender for the top 10 list.

Why choose F#?