Critical Skills for Software Developers that too Few People Talk About
Join the DZone community and get the full member experience.Join For Free
There are many discussions of what you should learn or need to know as a software developer. Most of the time these discussions are about technical stuff, like IDEs, programming languages, patterns, tools and so on. Of course there are also discussions about soft skills: How to give feedback, how to deal with difficult coworkers or customers. All important stuff.
But there is something in between. That’s what this article is about.
Take tiny steps: I spend a lot (read: too much) of my time on stackoverflow answering questions. And very often I find questions of people being completely lost in the mess they created. You can often tell simply from the tags they use. If they combine things like jsf, cdi and hibernate they obviously haven’t the slightest clue where even their problem is. They created 5 different files for 3 different frameworks and now something doesn’t work. Many very experienced developers will have a hard time setting up their preferred persistence framework, front end framework, build tool, DI-framework and what not in one go. So no surprise they failed. But how does a seasoned developer do this kind of thing? What is the advice?
Walk with tiny steps! Actually, at first don’t move at all. Think: What is the smallest possible change to the code base that can give you working code that is a little closer to your goal? If this involves changing more than 10 lines of code, keep thinking until you have a better idea.
Now make that step.
STOP! Look around. Did it work? If not you have at most 10 lines to worry about, ok I give you another 3 for possibly missing changes, but that’s it. And a tiny step never includes front end, back-end, and domain logic at the same time.
Understand stacktraces: This one comes again from stackoverflow questions. Actually from two kinds of questions. The one kind goes like this: “My code is broken, please help.” The other kind looks like this: “When I do x my application fails with this error message:
Application failed with XNotSupportedException in line 11, do y instead.
Yupp: the first kind didn’t even realize that a call stack might be important, the other kind didn’t bother to read it. I know error message can be intimidating and hard to understand. But a lot of work goes into these things and for a good reason: Learn to read them. You need to understand every single line of a stacktrace. If you have problems with a line, there is probably a stackoverflow question about it. Find it and read it.
Create and test theories: Developing software is an art. But it also has a lot of scientific work to it. And science works like this: You make an educated guess about something, and then you cook up an experiment to test it. (This is how Feynman defined it, and if you don’t know Feynman you should fix that too.)
The art part is back in the game when it comes to creating good theories. Good theories are easy to test. If you need a week to test a theory, you might want to test other theories first.
Good theories have a good chance of being true and of being false. A theory that is false with high probability is just a stupid idea and a theory that is certainly true is also known as a fact we already know. Everything in between allows us to learn about the problem at hand.
The term “Theory” might sound scary and complicated but it is actually rather easy. Let me give you an example. Your application doesn’t have an effect you are expecting. You inspect the code involved where a method gets called which should cause the effect. An obvious theory would be: “That method never gets called”, Another one, kind of the opposite: “The method does not cause the effect” a third one might be: “The effect does happen, but you fail to observe it due to some other problem”. If you like me a couple of years ago you don’t even think about this kind of stuff, because it seems so obvious and natural, but trust me: I have seen people randomly editing code trying to fix bugs with some kind of simulated evolution: apply random changes until the chances of survival increase. It seems like these developers forget that evolution involves as an essential part the death of millions of specimen …
Ask good questions: I consider the previous three points to be a precondition for being able to ask good questions. If you need more tips, go here.
Abstract: This one might be the one most difficult. At least it is difficult to teach. Software development is about abstracting over things. A small child can add two specific numbers, using their fingers. Describing the algorithm they use without reference to specific numbers is programming (and a little more difficult).
I consider my time as a physics student an excellent training for this. Boy was it abstract at times. Sometimes it was so abstract, we literally didn’t know what we were talking about. But you can hardly expect people to study physics just for this. One thing that might help is learn different languages, because different language can easily abstract over different things. Learning this different ways to abstract over stuff will help you to abstract over your next problem in a meaningful way. Oh, and if a coworker keeps replacing pages of your code with 5 lines of her code, you know whom to ask for mentoring.
Published at DZone with permission of Jens Schauder, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.