What I Wish I Knew When I Started as a Software Developer
What I Wish I Knew When I Started as a Software Developer
I hope that the couple of items listed here will be useful to people on their way out of college and into the software industry.
Join the DZone community and get the full member experience.Join For Free
Having worked in the software engineering field for six years, I sometimes pause and consider how much I have learned since I started my career. One thing that strikes me is how many things I would want to tell just-out-of-college me if I had the occasion. While I don’t have that capability, I hope that the few items below will be useful to people on their way out of college and into the software industry.
Keep on Learning
You just obtained your diploma, are overwhelmed by a sense of accomplishment, and now feel the desire to prove yourself to your new colleagues. That is great. Congratulations and good luck, but keep in mind that this is just the beginning of your learning.
You will find soon that you need to keep learning new technologies, new methods, new techniques, new languages. Start as soon as possible, because learning in an unsupervised way (no syllabus, no teacher, no final exam) is a skill that you need to hone.
Learn things outside your comfort zone. If you work on a dynamic language, learn a statically typed one. Use VIM or Emacs if you are used to an IDE, etc.
Find a Mentor
I just said that there are no teachers after college, but that is not entirely true. Nobody will sit in a classroom with you and go over a predefined lesson. But it is still extremely beneficial to find one more experienced person that can guide you.
Sandro’s book “The Software Craftsman” describes how a mentor is beneficial to a new software developer at great lengths.
Depending on the company with which you are working, you might be provided with a mentor or someone will come to you and spontaneously offer their help. Sometimes you will need to look for them. If you cannot find them amongst your colleagues, look for them in community events for example.
I did not know what a framework was when I got out of college. Looking up the definition of Wikipedia did not help, either, and for several long months I was too afraid to show my ignorance and ask.
Do not repeat my mistake. You are not expected to arrive at your first job knowing everything. Ask; don’t be afraid to show you do not know something.
Most of the time, you will find out that either at least one other person in the team had the same question or that people have slightly different definitions of the term you are asking about. Even if you are the only one asking the question, you will not be the only one learning something in return.
Get Good Practices Early
These good practices will be the foundation upon which you will build your career. Get them as early as possible.
Leverage Existing Libraries and Frameworks
I barely knew how to properly use a library when I got out of college. As I said earlier, I did not even know what a framework was.
As juniors, we have a tendency to reinvent the wheel. Our custom-made solutions will usually be of less quality than a library on which hundreds of people have collaborated over several years. Try to reuse what is already available.
On the other hand, understand what are the tradeoffs of a given library. Is it still maintained? Is it easy to use? Does it require huge changes in your application’s architecture? Make sure that you isolate that library so that replacing it does not mean making changes all over your code.
But Still Understand the Fundamentals
Libraries are convenient because they remove complexity. However, take the time to understand a bit of how they work under the hood.
While your web framework will handle HTTP requests for you, you need to get what HTTP is and how it conveys information between two computers. Similarly, take the time to understand the basis of DNS, TLS, and other low-level protocols. If your application uses OAuth or session-based authentication, you need to know it and you need to know what the consequences are. This page is a good starting point.
Assume the Mistake Is Yours
You will face unexplainable bugs, sometimes even heisenbugs that disappear when you debug them. In despair, you might be tempted to reject the fault to something else than your code. Always start with the assumption that it is an issue with your code, not the library, the OS or anything else.
This is a lesson in humility. There is a much higher chance that your barely tested, two-days old code is buggy than a battle-hardened library that has been around for years. As your debugging skills and your bug-hunter instinct improve over time, you will come to that conclusion anyway.
Sometimes, it is indeed a bug in another software component than yours. However flagrant the bug, however careless the offending code seemed, remember of how many bugs your code was littered to being with, and don’t hold it against the authors of the faulty code.
Test, Test, Test
I think that automated testing and test-driven development are not practiced enough in software engineering courses. Those are amongst the most important skills in software development today, and I wish I was made aware of that earlier in my career.
Learn how to write tests and how to maintain them. Pair with someone who can teach you test driven development. If you cannot find someone like that amongst your colleagues, look at a software craftsmanship community next to where you live.
Clean Code Principles
Learn how to write clean code from the start. The book by Robert C. Martin is an excellent way to start. There is also plenty of content online (just check other articles on the Codurance blog). Take the time to read some of that content and apply it. Ask your mentor or colleagues for feedback.
Programming Is A Social Activity
Depending how much programming practice you’ve had before starting your career, you might still believe that a programmer’s day is spent sitting alone in front of their editor. You need to understand as soon as possible how much you win by working with others.
This is a very important skill to develop. Get used to coding with someone else, passing the keyboard from one person to the other from time to time. Practice this both with people more skilled than you and with beginners.
Being Good at Writing Code Is Not Even Half the Job
You need to learn how to work with users or Product Owners, ask questions about features, and manage expectations.
You will discover that sometimes, the answer will not be to add more code to your project; either the feature is not needed or it can be implemented with the current version of the app, or there is another application that provides 80% of the functionality.
Don’t Be “Clever”
Being clever is rewarded in college. You may have been encouraged to optimize a for loop or write one less line of code by replacing
i++ in the line before.
Being creative and clever to solve a hard, complex problem is good. But do not use clever micro-optimizations that make your code less readable.
One of the greatest challenges as a beginner software engineer is to make your code readable. Your teammates need to be able to understand your code and evolve it without your help. Clever optimizations often go against that by making the code’s intent less obvious. Unlearn this “academic” reflex.
But understand it is a tradeoff, and readable code is more important that clever code. Boring code is good.
This article was first published on the Codurance blog.
Published at DZone with permission of David Hatanian , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.