The Context Of Design Thinking And Its Application In Employee Skill Training

The World Wide Web is a fun place to connect with old friends, make new ones, and stay involved in social media. It can also be a dangerous place for those who don’t know how to be safe on the web. Children, teenagers, and young adults with Asperger’s syndrome are especially vulnerable to fraud, sexual predators, and other online dangers.

What is Asperger’s Syndrome?

Asperger’s syndrome is a pervasive developmental disorder on the autistic spectrum. Children, teenagers, and adults with this developmental disorder are not sick. They’re brains are wired differently from people who are not on the spectrum. In the autistic community, people who are not on the spectrum are referred to as neurotypical.

The reason Internet dangers are so much more of a risk for people with Asperger’s syndrome is because of the symptoms associated with it. The best way to describe Asperger’s to someone who is not familiar with it is to call it a social learning disability. The parts of the brain responsible for reading facial expressions, body language, and other social cues do not function properly.

Although the index is an important itemized guide of what people are searching for on the internet, it’s arguable that certain languages getting recognition is a direct result of early adopters posting tutorials and filling up discussion boards on current trends. Additionally, popular tech blogs pick up on technological shifts and broadcast related versions of the same themes.

When does the popularity of a software language matter?

1. If you want marketable skills, knowing what employers are looking for is beneficial. As an example, languages such as Java and Objective C are highly coveted in the smart-phone apps businesses.
2. A consistently shrinking language in usage is an indicator not only that employers are apt to pass on those skills but fall in danger of being obsolete.
3. Focusing on languages that are compatible with other developers increases your chances to participate on projects that companies are working on.

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?