Have you ever known that person who won't check in his/her code until they're satisfied? Have you ever been that person? I know I have. It is a very, very bad

Have you ever known that person who won't check in his/her code until they're satisfied? Have you ever been that person? I know I have. It is a very, very bad sign when somebody is in a social environment and will not share their code. It means they are insecure, it might mean they're not getting any work done. It always means that the code is in a state where they are not proud of it and aren't comfortable receiving feedback. It typically means that the code isn't getting a whole lot better. A major software company like Google, or a team within that company, can't be compared to a lone cowboy coder. There are perfectly legitimate reasons to hold back code. In this case, though, if this is really the reason - that Honeycomb was rushed to market and the code just doesn't look good, we'll fix it later and let you know - how does that make the relationship with the open community look? Not good. It's not good to be afraid of community feedback, whether you're the Android team or a fresh programmer in an unfamiliar shop. And as for me personally, it doesn't give me a lot of hope for a pleasant experience on the Honeycomb development I'm going to be doing soon.