Hello everyone reading my blog,
I just wanted to say that I am not sure how often I will update my blog. I have started to work on a new job which I enjoy a lot.
I am going to keep a low profile on game development. I believe I will be back to it sooner or later.
Thank you for reading. 
Someone showed me her cross stitches today. She said there are millions of website where you can buy cross stitches images and samples.
Some of them are a representation of a photo or a realistic artwork. But some are also more schematic.
I am not sure about the legal issues here, but I would think that the cross stitches samples may be a really good source for pixel art.
What do you think?
When you are in a position that you don’t know if your code is the faulty one or the bug is somewhere else. Sometimes you can just use another program that you know is working and use it to verify where the bug is at.
An example. Say you have written code to load a BMP file format. You use your program, but the image has some weird artifacts. Is it a bug in your code? Or is it a corrupted BMP file?
You can simply load the same BMP file with another program such as window’s paint, and see if it loads properly or if paint is having problems with this file as well. If paint loads the BMP file properly, the bug might be in your code.
I have given the BMP file format as an example, but this is true to many other fields where you have some tool you know is working right. It is kind of similar to the Bug negative verification.
Making sense isn’t always good. I was debugging some code and printed some number on the screen. The number had weird initialized values, so I rationalized why these values are not 0 at the beginning.
Bottom line, I just forgot to initialize the debug variable so I had garbage values.
I think it’s a common trait of humans to try rationalize everything. Sometimes they are so convinced at something and the logic behind it, even though it has no basis or it is even something that can’t make sense.
Does it happen to you too?
I was starting to work at a new workplace last week. They have set me up a temporary desktop computer.
It was placed on a “table corner”, where two perpendicular tables connect. The set up was inconvenient. The monitor was placed far into the corner, and the mouse and keyboard cord barely reach the table’s edge.
Since the monitor was far, it was making my eyes tired. I don’t know exactly what I was thinking, but I rationalized why I should not try to pull the monitor closer.
At first I thought that because the mouse and keyboard cords can’t be pulled, there will be a problem with the monitor cord as well. Then I was told that I will get a new monitor today, so I said after I will get the new monitor this problem will be fixed.
I then talked about it with my boss, and while talking to him I figured how silly it sound that I just didn’t check or try to pull the monitor closer. I tried to gently pull the monitor and found out there was a lot of loose cable.
We some time rationalize things or find excuses to not try things because of a future event we are looking forward to.
It is a really important quality to be able to try things out even if you have no prior knowledge if it will work or how you are going to do it.
