csongor.fagyal.com

Pair programming is an agile development technique, where two programmers sit down together, and work on the same task simultaneously, mutually controlling and helping each-other’s work. The effectiveness of this process is questioned by some, and strongly supported by others. So – who is right? Should we employ this technique or not?

Web programming – on which I basically mean “creating whatever websites”, BTW – is a rather special kind of animal. In introduction to unit testing I wrote about how it is NOT a special case, but that is only one way to look at it – there certainly are some differences which might require a different perspective from the developer.

If you don’t know what unit testing is, and you are a programmer, you should probably read this post. If you do know what unit testing is, and yet you think it does not apply to you, then you are probably wrong, or you do NOT really know what unit testing is. (If after reading this post you still think it is a waste of time, then you are probably a bad programmer. Sorry!)

There is no CV on this site.

When I first had the idea of creating this page, I briefly thought about that, but dismissed the idea quickly. Of course I had some privacy concerns, but that’s not the point. The point is: I felt that posting a CV to your blog is cheap. I am not looking for a job. A job might be looking for me, yes, but for a job like that I don’t need a CV -instead, I need a page like this.

This is a description of an almost noiseless HTPC I built based on an ITX Atom/ION board, running XBMC and Linux. The Hardware I used is somewhat outdated now, but it is still available and cheap, providing excellent power consumption figures. I will give detailed instructions on how to build your own, with thoughts given to alternatives.