Fortsätt till huvudinnehåll

Do you need to be able to solve complex algorithmic tasks by heart in order to be a good developer?

Short answer, no, absolutely not.
If your daily work consist of designing algorithms and implementing them in code, then you should have a good understanding of algorithms and how to adapt and apply well proven solutions to various problems. However, 99% of all development work does not involve writing complex algorithms.

Take a look at the source code of any software. The absolute majority of the code will not involve any complex algorithms at all. Hence, there are a lot of other qualities that are far more important in order to be a good software developer. One of the top qualities is the ability to write clear and simple code that is easy to understand. Avoid using complex solutions unless absolutely necessary, keep the code as short and simple as possible and use clear naming.

Another important quality that makes a good software developer is the ability to quickly find information and adapt it to the problem you are working on. Today there are tons of information available online on how to solve different programming difficulties. There is no need to know all of these by heart, but knowing how to quickly find the information, understand it, and adapt it in order to solve the challenge you are currently facing are very important.

So, if you're not into algorithm theory, don't worry, you can still be an awesome developer. And, for those of you that are into hiring developers, understand that good developer qualities can not be reduced to a number, you have to put more effort into recruiting than handing the candidates an automatic online test.

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi
Skicka en kommentar
Läs mer

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i
7 kommentarer
Läs mer