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?

Evolving technologies become fun due to the immense advantages and features they bring with them. Fighting change though is human and while we may initially resist such changes, it is always better to accept them to our advantage.

Switching to HTML 5 is one such change we need to be ready for and there are at least 8 reasons why we should be doing so which are explained later in the article.

Earlier HTML was mainly used only for Web content development. But with the arrival of HTML 5, there would be a radical shift in that it would be used more and more for the development of many of the client side applications as well. The advantages straight away are that CSS as well as JavaScript become free due to the open architecture environment. HTML 5 is also pretty light and has a much easier code to read, making it convenient for devices like smart phones and tablets running on batteries to use the applications.

The 8 reasons mentioned above are as under:

Due to the advancements in technology, teens and adults alike can now partake in virtual worlds thanks to video games. Video games are enjoyed as a hobby all over the globe, but some gamers have made it their career with help from the ever-growing e-sport community. This is an inside look at the professional level of gaming from an ex-MLG participant, and what I remember going through when starting to play video games at an elite level.

One of the premiere and most popular leagues within the United States happens to be Major League Gaming or MLG for short. This is a league that usually involves more of the most recent games out, and they create circuits for each major title and its subsequent releases. Two of the most major game circuits within the MLG league were the Halo series and the Call of Duty series, both which happened to be first person shooters (FPS). There were a potential hundred or so teams within each circuit, but much like other competitions, the circuits were ran with winner’s brackets and losers brackets. This means that out of all the teams that would show up to MLG events, about the top eight of each bracket would really be known as the "elite" players. I personally played in the Gears of War circuit at venues like MLG Raleigh and MLG Toronto, and we had very few teams compared to Call of Duty and Halo. The amount of participants at each event usually varies in each circuit based on the popularity of the game being played.

When you win tournaments, the payouts are split between the team members. This means that looking at playing in the MLG for a life career is an ill-advised move. The cost to get to events and buy team passes usually negates the prizes you win most of the time, considering by the time that the prize money is split you are left with about $800 in a popular circuit (Like Call of Duty). The payouts are usually only high in special and certain occasions, one for example being the million dollar showdown that Infinity Ward hosted for Call of Duty: Modern Warfare 3 a couple years back. The way that players that make professional gaming their career get the big money now is by being sponsored by the big companies that back the league like Red Bull and Hot Pockets. MLG players like "Walshy" and "FeaR Moho" were sponsored early on in the league and were able to make a living off of the games they played. I would imagine them getting around $60K in a good year off of sponsors alone. I would go even as far as to say that if you do not have a sponsor in e-sports, you will not be financially successful in the career.

Being an MLG gamer requires passion and understanding for the games. If you just want to make money, then you are better off working at McDonalds.

How to Keep a Start Up Team Motivated?

What People Should Know Before Getting Rid of Old Tech Stuff

Surprising Ways Viruses, Malware, Etc. are Infecting Computers

Writing Python in Java syntax is possible with a semi-automatic tool. Programming code translation tools pick up about 75% of dynamically typed language. Conversion of Python to a statically typed language like Java requires some manual translation. The modern Java IDE can be used to infer local variable type definitions for each class attribute and local variable.


Translation of Syntax
Both Python and Java are OO imperative languages with sizable syntax constructs. Python is larger, and more competent for functional programming concepts. Using the source translator tool, parsing of the original Python source language will allow for construction of an Abstract Source Tree (AST), followed by conversion of the AST to Java.

Python will parse itself. This capability is exhibited in the ast module, which includes skeleton classes. The latter can be expanded to parse and source each node of an AST. Extension of the ast.NodeVisitor class enables python syntax constructs to be customized using translate.py and parser.py coding structure.

The Concrete Syntax Tree (CST) for Java is based on visit to the AST. Java string templates can be output at AST nodes with visitor.py code. Comment blocks are not retained by the Python ast Parser. Conversion of Python to multi-line string constructs with the translator reduces time to script.


Scripting Python Type Inference in Java
Programmers using Python source know that the language does not contain type information. The fact that Python is a dynamic type language means object type is determined at run time. Python is also not enforced at compile time, as the source is not specified. Runtime type information of an object can be determined by inspecting the __class__.__name__ attribute.

Python’s inspect module is used for constructing profilers and debugging.
Implementation of def traceit (frame, event, arg) method in Python, and connecting it to the interpreter with sys.settrace (traceit) allows for integration of multiple events during application runtime.

Method call events prompt inspect and indexing of runtime type. Inspection of all method arguments can be conducted. By running the application profiler and exercising the code, captured trace files for each source file can be modified with the translator. Generating method syntax can be done with the translator by search and addition of type information. Results in set or returned variables disseminate the dynamic code in static taxonomy.

The final step in the Python to Java scrip integration is to administer unsupported concepts such as value object creation. There is also the task of porting library client code, for reproduction in Java equivalents. Java API stubs can be created to account for Python APIs. Once converted to Java the final clean-up of the script is far easier.

Related:

 What Are The 10 Most Famous Software Programs Written in Python?

Python, a Zen Poem