Heh well, you know most programmers hate doing UI work. Look at most open source projects that have a GUI, there is no polish or real effort put into usability (with a few exceptions). I consider the UI to be the “face” of the application, it’s what users see and what they have to deal with, and the quality of the UI is what people have as their first impression. A good UI doesn’t get noticed, it just works and feels right. It’s the bad UIs that get the attention.
This having been said, I always polish my application UI to the greatest extent possible That’s why little things like the drag image, getting the listbox to scroll in whole row increments, paging / mouswheeling in the viewport scrollbar by (visible rows - 1) pixels, hinting for small fonts, having a native menu bar that works as expected, constraining the content component’s size instead of the heavyweight peer, etc… all mean a lot to me. I will not even allow a single pixel to be out of place, part of quality control is taking a screenshot of the application and going over it at 800% magnification in Photoshop, pixel by pixel - this is how I found the problem with curve flattening and rounded rectangles.
I know that listboxes, having robust object passing for drag and drop, etc… are boring compared to fun and exciting things like drawables, component transformations, and iphone compatibility but I’m not trying to be a pain in the ass I just have to fulfill the design criteria.