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.”

Learning SQL development can seem like an overwhelming task at first. However, mastering just a few key points will help ease your way through 80 percent of the day-to-day challenges when writing stored procedures and solving common problems. Here are three important SQL development factors to keep in mind:

Outer Joins
One of the most crucial things to understand in SQL server are joins. Joins are a way to retrieve data from two or more tables based on logical relationships between them. Joins dictate how Microsoft SQL Server ought to use data from one table to select the rows in another table.

In my experience inner joins are intuitive while outer joins can present additional hours of grief by overlooking associations in the other table(s). The outer join is the key to answering questions about what the database does not have. For example, if you need to make a query to display all the students who are without report-cards, you’ll need a left join to get all students coupled with a “where clause” to return the ones who have nulls for their report card table columns in the results.

Many talented Java script programmers have muddled through the SQL Server by deficient coding around the inner join. As a result, their queries can take five hours to run, whereas, properly written left joins, can take only two seconds to run.

Aggregation
Grouping results comes up in SQL a lot more than you might think. Knowing how to write a query when answering questions such as, “What’s the average grade for each teacher’s student list?” is invaluable. This kind of question cannot be answered with a single table or solely by joins.  You’ll often find you need to use joins in conjunction with group by statements. Always write the raw query first and then look at the results. Next, you have to figure out the best way to group them, rewrite your select clause and add a group by clause in the end.

Digging Through Data
I find this is the most lacking skill in many programmers. In fact, many otherwise-talented programmers holding Master’s Degrees fail to get jobs because they couldn’t analyze rows of data objectively during interviews. It’s just something that’s not taught but is crucial to get under you belt. Why? Eventually, some query is not going to perform as you may expect. And, the only way to find discrepancies is to look at rows of data, identify what join isn’t finding a match or where bad data is throwing things into chaos. Get familiar with how joins actually work, even if you have to manually walk through the logic of a large stored procedure’s tree of joins. It’s boring and time-consuming but absolutely necessary.

Take the time to master the core skills that will make you a successful SQL Programmer and avoid queries that run for five hours!

Unlike Java, Python does not have a string contains method.  Instead, use the in operator or the find method.  The in operator finds treats the string as a word list whereas the find method looks for substrings.  In the example shown below, 'is' is a substring of this but not a word by itself.  Therefore, find recoginizes 'is' in this while the in operator does not.

s = "This be a string"
if s.find("is") == -1:
    print "No 'is' here!"
else:
    print "Found 'is' in the string."
    
if "is" in s:
    print "No 'is' here!"
else:
    print "Found 'is' in the string."

#prints out the following:
Found 'is' in the string
No 'is' here!

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.