I am DVDKOURIL. This is my blog.

How not to look for bugs in your code

In the project at work I basically have data that I’m rendering with a very sophisticated rendering pipeline. I was not getting exactly correct results so this week I had to look into that. From my point of view, there were two parts where things could go wrong: the data loading or the sophisticated, complex, error-prone rendering routine. I’ve spent two days going through every single part of the rendering, making sure that everything does exactly what I need it to. Of course everything was fine. The problem was in a code which loads the data from a text file. At some point I thought that this might be the problem but I dismissed it because it was “too much work” to debug.

It was just a gentle reminder of how much I still have to learn. Sometimes I get really hyped up and I’m excited to deliver things. But then I get stuck for few days on one thing and I’m reminded how hard software development actually is. It kinda makes me appreciate higher-level programming languages and other people’s libraries.

I was at my colleague’s “proficiency evaluation” this Friday. It’s a new kind of exam at TU Wien for PhD students. You are supposed to do it some where in the middle of your PhD and basically you show what you’ve already done and what’s your plan for the rest of the PhD. He was the first one to do it in the Vis Group and even though he passed, it wasn’t 100%. I took a lot of notes and I’m going to make sure that I have a better plan for my PhD.

This week were also notifications for IEEE Vis 2017 conference and quite a few papers got through! The one that I was participating on too! That’s good news because more people are going to go to Phoenix this autumn.