Interesting observation... this is something I struggled with as well coming from a coding background and trying to do design -- at the individual element level the colors seemed great, but pulling back to the larger picture everything looked washed out. Did you ever come up with a solution for this?
Think about it (loosly) the way you think about inheritance in OOP. What is the parent, what are the ancestors.
All elements on pages have a priority. That priority should be the guide of your visual heiarchy. This can be done with size alone but it can also be done with color.
Also black or almost black (#222-#333) as copy is always a good way to make sure your page has contrast. But again it depends on what you are doing.
I really need to finish my book on design for developers. I think I have found a way to create the bridge between being a developer and a designer. When I get to new york I will have more time.
I'd say that depends on the subject. I don't want bold decisions to try and energize my experience with my text editor.
I feel like Google has suffered from a similar problem - the solution to every UI problem these days is minimalism. Remove borders, accents, highlights, colors. On the surface it looks clean and simple but scratch beneath that and it seems to have no soul and no reason to exist.
I think the same issue goes directly to functional aspects as well - the functions and features on the page should feel alive as if they are speaking to me. I should be attracted to them, immersed in them, like they've been incorporated as parts of myself - but I'm not - I can barely differentiate them from the inactive, static parts of the page. Most of Google these days feels like I am filling out an IRS tax form. At best it is boring, at worst it is aggravating.
I'm looking forward to when we get through this new style of design from Google.