We are not all equally motivated. Some people have more self-drive than other people. This is why we find that some people always end up at the top even when the odds are against them. An employee, with this realization, through the Human Resource department, should be able to design efficient career development systems. For this system to work, the employer must understand the nature of the business environment in which they are operating.

Why Train Employees?

The purpose of training employees is to enable them to grow with time and increase their efficiency. The business world is quite dynamic, nothing stays the same for long. Training one’s employees allows them to keep abreast with the ever changing technological advancements and many other factors that are relevant to his/her line of work. Employees cannot be expected to solve all their employer’s expectations with static skills and techniques. Even the most updated technology becomes obsolete at some point.
People are the biggest assets in organizations. For an establishment to flourish, it is important that the employer understands certain key things that help spur their development.

In a report from the Harvard Business Review, “The Impact of Employee Engagement of Performance,” the most impactful employee drivers are:

If you're someone who's interested in computer programming, chances are you've considered pursuing a career in it. However, being a computer programmer is definitely not for everyone, as it takes some special characteristics to succeed as a computer programmer.

Good at Math

While you don't have to be a math genius in order to be a good computer programmer, being good at math really does help. In general, as long as you know your trigonometry and advanced high school algebra, you should be set for programming.

However, in a few instances, knowledge of more advanced math ends up being necessary. For example, for shader programming, you should be familiar with integration of multiple variables, matrix algebra, and basic differentiation. You will also require considerable math skills in order to program 3D.

Excellent Problem Solver

To be a successful computer programmer, you definitely need to be an excellent problem solver. It is vital for a computer programmer to break a problem down into small parts. They must then be able to decide the best way to approach individual pieces of the problem. Computer programmers also need to know how to anticipate and prevent potential problems. While problem-solving, they also need to keep in mind things like user experience and performance.

If you're not a good problem solver, knowing a particular language and syntax will be useless if you can't even identify the problem at hand. Therefore, excellent problem solving skills are a critical foundation for computer programming.

Patience

If you are not a patient person, you will quickly become very frustrated with computer programming. Problem-solving is not always easy and fast. In fact, it may take a very long time, especially if you're either inexperienced or working on an especially hard project.

Debugging after the coding process is also very frustrating and tedious. No matter how hard you try, you will always have bugs in your coding, and these bugs, while often easy to fix, tend to be very difficult to detect. Therefore, you will end up spending a lot of your time searching for bugs that take very little time to fix.

Well-Rounded Skills

Generally, computer programmers who are very skilled in one area tend to stick around longer than jack-of-all-trades, as specialized programmers are harder to replace with outsourcing than general programmers. Therefore, it will do you well to specialize in one area of computer programming.

However, while specializing is good, you should still know at least a little about everything, especially skills that relate to the area you specialize in. For example, if you're a core Java programmer, you should know about SQL programming and ideally a scripting language or some regular expressions.

As you can see, not everyone has what it takes to pursue computer programming as a career and succeed at it. In fact, just because you love to program doesn't mean it's a good career choice for you. However, if you feel that you possess all the characteristics listed above, then you should definitely consider computer programming as a career.

Passbook is one of the newest features of the iPhone. What many people were offput by standards today is that we rely too much on disposable tickets, and the like, such as when you go to the airport for a boarding pass, or a movie ticket. Apple strove to solve that with a new application that is bundled with the newest update: Passbook.

Passbook offers everything you need, especially when a ticket, coupon, or gift card is needed. When you first open the application you are greeted by a sampling of applications that support Passbook, and its features. To begin, install the particular application you want to use. For example, we will be going with the Starbucks application to satiate our coffee needs every morning, as we have a gift card to spend.

Open up the freshly downloaded application, and get ready to be blown away. Like most applications, especially when it has to do with airlines, or coffee, you are almost always required to sign up for a respective account. Don’t worry, it is easy. All you will be asked is to fill out your email, a password, and other miscellaneous information to identify you when you lose your password or others.

Once you have finished signing up, you’re ready to roll. It will prompt you to enter a gift card that you already own, or begin a digital gift card. If you don’t have a gift card, you can start a digital gift card (or, as many may call it: a prepaid card), and pay for your coffee in a fast, and efficient way. Just tap on “Tap to Pay” when you are ready to pay, and tap again after you have paid. It’s really that easy.

The original article was posted by Michael Veksler on Quora

A very well known fact is that code is written once, but it is read many times. This means that a good developer, in any language, writes understandable code. Writing understandable code is not always easy, and takes practice. The difficult part, is that you read what you have just written and it makes perfect sense to you, but a year later you curse the idiot who wrote that code, without realizing it was you.

The best way to learn how to write readable code, is to collaborate with others. Other people will spot badly written code, faster than the author. There are plenty of open source projects, which you can start working on and learn from more experienced programmers.

Readability is a tricky thing, and involves several aspects:

1. Never surprise the reader of your code, even if it will be you a year from now. For example, don’t call a function max() when sometimes it returns the minimum().
2. Be consistent, and use the same conventions throughout your code. Not only the same naming conventions, and the same indentation, but also the same semantics. If, for example, most of your functions return a negative value for failure and a positive for success, then avoid writing functions that return false on failure.
3. Write short functions, so that they fit your screen. I hate strict rules, since there are always exceptions, but from my experience you can almost always write functions short enough to fit your screen. Throughout my carrier I had only a few cases when writing short function was either impossible, or resulted in much worse code.
4. Use descriptive names, unless this is one of those standard names, such as i or it in a loop. Don’t make the name too long, on one hand, but don’t make it cryptic on the other.
5. Define function names by what they do, not by what they are used for or how they are implemented. If you name functions by what they do, then code will be much more readable, and much more reusable.
6. Avoid global state as much as you can. Global variables, and sometimes attributes in an object, are difficult to reason about. It is difficult to understand why such global state changes, when it does, and requires a lot of debugging.
7. As Donald Knuth wrote in one of his papers: “Early optimization is the root of all evil”. Meaning, write for readability first, optimize later.
8. The opposite of the previous rule: if you have an alternative which has similar readability, but lower complexity, use it. Also, if you have a polynomial alternative to your exponential algorithm (when N > 10), you should use that.

Use standard library whenever it makes your code shorter; don’t implement everything yourself. External libraries are more problematic, and are both good and bad. With external libraries, such as boost, you can save a lot of work. You should really learn boost, with the added benefit that the c++ standard gets more and more form boost. The negative with boost is that it changes over time, and code that works today may break tomorrow. Also, if you try to combine a third-party library, which uses a specific version of boost, it may break with your current version of boost. This does not happen often, but it may.

Don’t blindly use C++ standard library without understanding what it does - learn it. You look at std::vector::push_back() documentation at it tells you that its complexity is O(1), amortized. What does that mean? How does it work? What are benefits and what are the costs? Same with std::map, and with std::unordered_map. Knowing the difference between these two maps, you’d know when to use each one of them.

Never call new or delete directly, use std::make_unique and [cost c++]std::make_shared[/code] instead. Try to implement usique_ptr, shared_ptr, weak_ptr yourself, in order to understand what they actually do. People do dumb things with these types, since they don’t understand what these pointers are.

Every time you look at a new class or function, in boost or in std, ask yourself “why is it done this way and not another?”. It will help you understand trade-offs in software development, and will help you use the right tool for your job. Don’t be afraid to peek into the source of boost and the std, and try to understand how it works. It will not be easy, at first, but you will learn a lot.

Know what complexity is, and how to calculate it. Avoid exponential and cubic complexity, unless you know your N is very low, and will always stay low.

Learn data-structures and algorithms, and know them. Many people think that it is simply a wasted time, since all data-structures are implemented in standard libraries, but this is not as simple as that. By understanding data-structures, you’d find it easier to pick the right library. Also, believe it or now, after 25 years since I learned data-structures, I still use this knowledge. Half a year ago I had to implemented a hash table, since I needed fast serialization capability which the available libraries did not provide. Now I am writing some sort of interval-btree, since using std::map, for the same purpose, turned up to be very very slow, and the performance bottleneck of my code.

Notice that you can’t just find interval-btree on Wikipedia, or stack-overflow. The closest thing you can find is Interval tree, but it has some performance drawbacks. So how can you implement an interval-btree, unless you know what a btree is and what an interval-tree is? I strongly suggest, again, that you learn and remember data-structures.

These are the most important things, which will make you a better programmer. The other things will follow.