Are you transitioning from the classroom to the workplace?

Technology is evolving so quickly that as a developer, it is inconceivable to learn everything. In the past 12 months, I have created programs using C, Java, Angular 1 and 2, ASP.NET MVC, .NET Core, Xamarin, Ionic, React and Redux, Meteor, jQuery and a plethora of other frameworks (and if you are reading this, you probably have, too). I have to admit that it’s impossible to know everything about each one of these. Often, new releases in these technologies by the vendor break a previously working piece of software. How do you solve some of these issues so you can continue developing and stay productive? I have found some of the approaches I take now in the workplace are different than what was commonplace in the classroom. Here are my top tips for you if you’re a recent graduate to stay successful in the workplace:

1. Seek Help From Outside Sources

Now, this one may seem like a ‘no-brainer’ but the reality is that some methods not allowed in a school environment are acceptable (and common) in the workplace. In order to solve some of the issues outside of your control such as the previously mentioned release updates, sometimes it is necessary to sift through multiple results from a Google search or crowdsource the solution by posting the problem on a forum. In today’s fast-paced world, these are critical outside resources that allow developers to not have to recreate the wheel every time we encounter a hurdle.

2. Embrace the Fact You Will Fail

Failures in code are different than failures in school. The typical coding exam in school consists of writing the code down to a question on a piece of paper. Then the grader takes the code, plugs the program into a computer and see if it works (I know this because I was one). If there is an error and the code fails to compile the student automatically fails. The real world behaves much differently — there is a gray zone. An error in your code does not mean you are stupid or bad at programming. It simply means there is a divide between what you believe the computer should be doing and what you have instructed it to do. These errors usually provide a message for what is causing the hiccup and how you can solve it. If you are not receiving errors as a programmer this means you are probably not challenging yourself or testing new platforms. Instead, errors should be viewed as opportunities which finding solutions for will allow you to grow as a developer.

3. Be Flexible and Accommodate Change

In industry everything is much more opaque than university. Sometimes the problem the client originally wanted you to solve is changed as you are just about to implement a solution. As a consequence, the estimated deadline is changed- or worse, it’s not! The tools to solve the issue are oftentimes picked by your own team so you may seek an open source solution, re-purpose old code from another project, or maybe you have to write an entire program from scratch. The final assessment of the product is the satisfaction of the client and knowing you can accommodate change makes serving them much more possible.

4. Be Authentic About Your Strengths and Weaknesses

I encourage new developers to understand your strengths and weaknesses. Are you better at back-end or front-end development? Which languages frameworks do you have a preference for? Inevitably, you will be confronted with a problem you do not know how to solve and you can streamline finding a solution by reaching out to someone more knowledgeable than you rather than thrashing to find a solution while wasting the client’s time and money.

5. Be Curious

Young developers should expose themselves to as many new technologies as possible. Always orient yourself towards using new languages and technologies. It is easier to consistently use a small set of languages you are most comfortable with rather than going through the stress of learning something new. However, plowing through the adversity that comes with learning new technologies you will become a much more well-rounded developer and find the challenges a reward for your hard work.

School curriculum can sometimes foster an environment that works well inside the universities’ walls, but isn’t all you need to thrive in a real-world environment. In the real-world failure is a key ingredient to becoming a successful developer. There is a great discrepancy between the cookie cutter solutions provided at school and the ambiguous answers found in industry. That is why seeking help, embracing failure, learning to be flexible, knowing your skillset, and staying curious will help you thrive in your early development career.