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

One of the biggest challenges in pursuing a career in software development is to figure out which language you want to work. In addition to commonly used software programming languages like C, C++, C# and Java a lot of new programming languages such as Python, Ruby on Rails have surfaced especially because they are used by a lot of consumer based start-ups these days.

It could then be a daunting task to figure out the technical language you should learn which helps you prosper in a software engineering career no matter the technology advancements that happen in the marketplace. Learning a fundamental and universal language like C# could be a great start to your career as the language is very mature and extensively used by companies large and small

What is C#

Similar to Java, C# is a multi-paradigm, object oriented language developed by Microsoft. C# is intended for use in developing software components meant to be deployed in distributed environments. So in essence, learning C# can enable you to write applications for large and complex server side systems that use sophisticated operating systems as well as compact mobile operating systems such as Android

The line between IT consulting and management consulting is quite often blurred, with overlaps between the two fields habitually happening. Worse still, most people do not understand who an IT consultant really is, or what he/she does. There are those who think the job entails fixing computers, others – selling computers and associated accessories. This is misleading though.

In a nutshell, IT consultants are professionals who aid businesses in deciding what computer tools and technologies are best placed to grow and sustain a profitable business. They work hand in hand with clients to help integrate IT systems into the latter’s business. They show clients how to use technology more efficiently, and in so doing, the client is able to get a higher return on their technology investments, and ultimately, increase the bottom-line.

IT consultants, or IT advisories, could work independently or for a consulting firm, with their clientele spread across all sorts of businesses and industries. Companies hire or contract the consulting firm to come in and analyze their IT systems and structure.

The job itself is not short of challenges, however, and the path to becoming a successful IT consultant is fraught with its fair share of ups and downs. But hey, which job isn’t? Experience is the best teacher they say, and only after you’ve worked as a consultant for a number of years will you finally gain invaluable understanding of what is expected of you. Learning from the experiences of those who’ve been in this business for long is a good starting point for those who decide to venture into the world of IT consultancy.

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!