Have been using OO for years, never noticed the .org in the name until you pointed it out, and it's already annoying!

The "bugs" one made me think this was written by someone who had no idea how a sustainable development model works. Then I read Marc Garcia is a student. How does this shit pass thru Slashdot's editors?

This is my experience as well. However, in my case the definition of project is a bit loose:
- Someone wrote a script in perl and left the company.
- Someone else needs to make Improvements to this code but they dont know perl. Even though the original code is written in as clear and readable perl as possible, they automatically think perl is hard. This is in fact company policy now. They write a python script and make a system call to it from the perl code. Soon there are two, three... seven python calls in the perl code.
- Someone now wants to break the perl code up, so now there are python calls in the perl code and perl calls in the python code.
- Someone wraps this up in a shell script.
- Someone else learnt bash and not sh so they make bash calls in this code and it no longer works on non linux architectures.
- Someone who knew the original developer calls him and they enjoy a wry laugh.

I just sold the fact that dgatwood has anal retention issues to Ex-lax.

My eyes are particularly sensitive to bright light and flicker and things like that -- I havent read this study, but I tend to concur as after oodles of tweaking, I have settled on white text on blue background. I have found that not using too many colors (eg. turning off syntax highlighting) helps, and choosing bigger and clearer fonts (dont know how to quantify "clearer"). Refresh rate should be high too. Contrast and brightness should be lower than default. Tend to pick greys instead of whites, eg. rgb=0.9 each instead of 1.