Tihy

http://blog.tetrack.com/2009/05/take-away-software-setup/

http://blog.tetrack.com/2009/05/on-code-quality-a-small-quality-fix-with-every-bug-fix/

http://blog.tetrack.com/2009/02/thoughts-about-job-interviews/

http://blog.tetrack.com/2009/02/too-many-passwords/

http://blog.tetrack.com/2009/02/small-experiment-unplug-your-mouse-for-a-day/

http://blog.tetrack.com/2009/02/what-is-this-crisis/

http://blog.tetrack.com/2009/02/creating-html-using-tree-structures/

http://blog.tetrack.com/2009/02/eiffel-goodies-for-pascal-programmers-part-i/

http://blog.tetrack.com/2009/01/enterprise-application-development-reinventing-the-wheel/

http://www-users.cs.york.ac.uk/~susan/joke/foot.htm

http://blog.tetrack.com/2009/01/exceptions-or-return-codes/

http://blog.tetrack.com/2009/01/the-doomsday-argument/

http://blog.tetrack.com/2009/01/read-your-code/

http://blog.tetrack.com/2009/01/on-code-quality-symptoms-of-rotting-design/

http://blog.tetrack.com/2009/01/allow-multiple-remote-desktop-connections-on-vista/

http://blog.tetrack.com/2009/01/companies-as-persons/

It’s no news that there have been a lot of layoffs in the IT industry lately. And there are more to come, I expect, because layoffs are supposed to have a positive economic impact for the company (which is higly desired in stormy economic times). But layoffs also come with a big price tag: they leave behing a cloud of doubt, lack of trust and uncertainty over the remaining employees.

http://blog.tetrack.com/2009/01/on-code-quality-rewrite-once/

All you have to do is delete your first implementation and rewrite all the code from scratch. The main reason for this is that you can focus on code quality without being constrained by the existing implementation.

http://blog.tetrack.com/2009/01/is-yahoo-messenger-free-guess-again/

I guess many of you know how much time it takes for this software to start, how much memory it uses and so on. However lately I discovered a more disturbing thing: it also eats POWER. Yes you heard me electric power.