Fortsätt till huvudinnehåll

Code at work, code at home, dream of coding

I still remember my first lines of code. Ten years old, C64 BASIC, 10 PRINT "Eric "; 20 GOTO 10;.

Now 26 years later I do more coding than ever. I code at work, at home and even dream of solving coding tasks (actually I am a bit concerned about the dreams part, doesn't feel all that healthy).

I believe the best thing about coding is that it is so easy to get started and no matter how much you learn there is always so much more to pick up.

Recently I have been started thinking about ways to show my oldest son things you can do with code. He can not read much yet so showing him lines of code won't give anything just yet. I have heard about some apps and games where you code using pictures in sequence. Will check what I can find and put up some reviews here later.

Kommentarer

Skicka en kommentar

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

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

Does TDD really improve software quality?

I have asked myself this question several times, and searched for answers, without coming up with any clear answer. Therefore I have decided to go hard core TDD for a longer period of time (at least 6 months) to really evaluate the effects. There are several things that I find confusing when it comes to TDD. One example is what actually defines a unit test. What is a "unit" anyway? After reading a bit about it I found a text claiming that the "unit" is "a unit of work", i.e. something quite small. Like converting a string to UPPERCASE or splitting a string into an ['a','r', 'r', 'a', 'y'] of chars. This work is usually performed by a single call to a single method in a single, isolated, class. So, what does it mean that a class is isolated? Does it mean that it doesn't have any dependencies to other classes? NO! In the context of TDD it means that any dependencies are supplied by the test environment, for exa...
3 kommentarer
Läs mer

Is it necessary to have some basic knowledge of algorithms and datastructures in order to be a good programmer?

The short answer, yes, absolutely. This is a follow up to my previous blog post where I claimed that you don't need to know advanced algorithms by heart in order to be a good programmer. That is still totally true. However, you should have at least some basic understanding of algorithms and data structures. Having this knowledge will help you select the correct tools for the job, for example knowing when to use a stack over a queue, when a linked list is a better selection than an array, when to use a hashset, or a dictionary, and so on. This will help you write easier and more robust code. It is also a really good idea to have some feeling for how your code will perform when input data grows. How will memory consumption and running time be effected if the input data grows by a factor 100, or 1000? This knowledge will help you identify performance bottlenecks in your application and help you come up with ideas on how to attack them. So, if you haven't done it already, ta...
3 kommentarer
Läs mer