What is computer crime? Computer crime, often called “cyber crime” is any type of illegal activity that takes place on a computer with a network. Oftentimes, when you think of computer crime, you might picture a home user downloading a virus that wipes out his hard drive or spyware that hijacks her system for the purposes of spying. 

Computer crimes can also affect businesses too and they do, sometimes with devastating results. For example, in 2012, the IRS paid a whopping 5.2 billion dollars in tax refunds to identity thieves!

Protect your business and improve your bottom line by staying one step ahead of the cybercriminals.

5 Common Computer Crimes

Python and Ruby, each with roots going back into the 1990s, are two of the most popular interpreted programming languages today. Ruby is most widely known as the language in which the ubiquitous Ruby on Rails web application framework is written, but it also has legions of fans that use it for things that have nothing to do with the web. Python is a big hit in the numerical and scientific computing communities at the present time, rapidly displacing such longtime stalwarts as R when it comes to these applications. It too, however, is also put to a myriad of other uses, and the two languages probably vie for the title when it comes to how flexible their users find them.

A Matter of Personality...

That isn't to say that there aren't some major, immediately noticeable, differences between the two programming tongues. Ruby is famous for its flexibility and eagerness to please; it is seen by many as a cleaned-up continuation of Perl's "Do What I Mean" philosophy, whereby the interpreter does its best to figure out the meaning of evening non-canonical syntactic constructs. In fact, the language's creator, Yukihiro Matsumoto, chose his brainchild's name in homage to that earlier language's gemstone-inspired moniker.

Python, on the other hand, takes a very different tact. In a famous Python Enhancement Proposal called "The Zen of Python," longtime Pythonista Tim Peters declared it to be preferable that there should only be a single obvious way to do anything. Python enthusiasts and programmers, then, generally prize unanimity of style over syntactic flexibility compared to those who choose Ruby, and this shows in the code they create. Even Python's whitespace-sensitive parsing has a feel of lending clarity through syntactical enforcement that is very much at odds with the much fuzzier style of typical Ruby code.

For example, Python's much-admired list comprehension feature serves as the most obvious way to build up certain kinds of lists according to initial conditions:

a = [x**3 for x in range(10,20)]
b = [y for y in a if y % 2 == 0]

first builds up a list of the cubes of all of the numbers between 10 and 19 (yes, 19), assigning the result to 'a'. A second list of those elements in 'a' which are even is then stored in 'b'. One natural way to do this in Ruby is probably:

a = (10..19).map {|x| x ** 3}
b = a.select {|y| y.even?}

but there are a number of obvious alternatives, such as:

a = (10..19).collect do |x|
x ** 3
end

b = a.find_all do |y|
y % 2 == 0
end

It tends to be a little easier to come up with equally viable, but syntactically distinct, solutions in Ruby compared to Python, even for relatively simple tasks like the above. That is not to say that Ruby is a messy language, either; it is merely that it is somewhat freer and more forgiving than Python is, and many consider Python's relative purity in this regard a real advantage when it comes to writing clear, easily understandable code.

And Somewhat One of Performance

Technology has continued to evolve in ways that few would have been able to imagine. This has allowed electronics to become smarter, more connected and far more useful.

With the Internet of Things (IoT), they're allowing more than just computers to become connected to the Internet. This aims to make the life of the average person easier, better and more care-free.

Let's examine why the Internet of Things has become such a powerful idea that an estimated one out of every five developers currently works on an IoT project.


What is the Internet of Things?

The Internet of Things hinges on one seemingly simple concept: electronics can be embedded in machines, clothing, animals and even people to provide a networked world where the whole is more than just the sum of its parts.

For example, consider how the Internet of Things can influence things like refrigerators. They can be networked directly to the manufacturer for readings that can warn if the refrigerator is about to malfunction. They can even be connected to a grocery shopping service to allow someone to restock them automatically or to notify the owner that the refrigerator is almost out of an item.

The most interesting notion about the Internet of Things is that it's not just a situation where one “thing” connects with a party. They typically communicate with other things, which in turn allows for a network of automated processes to occur.

These processes can simplify and expedite tedious tasks to make everyday life for everyone easier, which is why projects involving the Internet of Things are so popular.


How Prevalent is IoT Development?

An estimated one in five developers are currently developing projects for the Internet of Things. Their chosen languages vary widely because of the flexibility that IoT enjoys.

For example, IoT projects that hinge on interacting with mobile phones tend to have apps written in JavaScript or Java. The back-end code that runs the IoT functionality for machines tends to be written in Assembly, C++,Java,Perl,Pythonor another compiled language for efficiency.

To put the growth of IoT work into perspective, Evans Data Corp. performed research to create predictions about IoT projects in 2014. They stated that 17% of companies would be developing IoT projects.

In this year, that figure's risen to a solid 19%. Given the fact that 44% of developers have stated that they will enter into the IoT scene this year or next, this means that development will only grow in the coming future.


The Future Involving the Internet of Things

Development of IoT-related projects will likely explode in the next few years. The advantages it brings, such as more efficient work in manufacturing environments and the projected 15% savings to the restaurant industry over the next five years, will make it one of the most valuable technological changes in the near future.

Without a comprehensive understanding of the Internet of Things and the skills to lead IoT projects, businesses and developers may find themselves falling behind. Don't let the Internet of Things pass you by.

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?