Jeff Nelson, a former Googler and inventor of Chromebook says on Quora, “One habit I've clung to is writing small prototypes when I'm trying to learn new concepts.
For example, I'll sit down with a book or a web page, and over the course of a few hours, write 30 or 40 programs all of them only a few dozen lines long.  Each program intended to demonstrate some simple concept. This prototyping makes it very easy to try out many concepts in a short period of time.”

Miguel Paraz, Software Engineering Student habit is to “keep a log in a text file or document on my work computer. Before trying to solve a problem, I write it down first. And then I describe the details as they happen.”

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?

Have you ever played a game on your iPhone and wondered how to share it with your friends? Of course, not everyone has iPhones, and they aren’t always watching the leaderboards on the Gaming app, provided by Apple. Well, guess what? You don’t have to take a whole other camera to take a picture of your iPhone to create a photo of that particular score you have achieved. All you have to do is simultaneously press the “Home Button” and the “Lock Button” on your iPhone. After that, your iPhone should consequently flash to white, as if it were snapping its shutter, and taking a picture. Afterwards, you should be able to find the picture in your Photo Albums and share it with your friends.                                                                                        

But, taking screenshots of your iPhone doesn’t always have to deal with your game scores, you can take screenshots of almost any happening on your phone and share it with people! Have you ever had a memorable texting conversation with your friend, where you mistyped something, and the conversation went haywire? Sharing it becomes easy by using this feature. Want to show how odd a website looks on your iPhone compared to looking at it on your computer, and give it to their support to fix it? Take a screenshot of it! The possibilities of this feature are endless, and can become timeless with a simple picture.