Again thanks for questioning our decisions, that's the way we can evolve the product and that helps us to make it better.
First of all let me clarify the process we have used to define if we should do this change or not, because I believe transparency is the best tool anyone can use. During this last year we have been performing lots of usability tests, on advanced developers and newcomers (being the latests our main focus). On these tests we have found some amazing insights, things like people going to the search and not noticing that they have to click on the magnifying glass, people searching for text on it, people searching for community content... among other things. With these insights in mind, we decided to check some data points that we have to see if these could represent common patterns, and in some cases we found that these were possible false positives, on other cases we found that these were possible issues, that could be affecting more users than we would like.
That said, you stand correct Kilian, there are power users for which change is harder because it impacts your daily work, I’m a developer and I know the impact these kind of changes have on my productivity (for example when I have to use a computer of a co-worker, I miss my shortcuts, tools…). We have been thinking on ways in which we can do these changes while minimizing the impact, because we believe that change is good and necessary but we don’t want to make your daily work harder, actually we want to improve everyone's productivity. However, we still haven’t found a good way to do this because of possible issues on our training materials, and other excuses that at the end of the day I believe you would understand, but that you would also say: “You shouldn’t use that as an excuse, and you should allow us to…”. It’s just a matter of cost/benefit, and again I stand on your side that we need to be more careful, and to learn with these small annoyances.
By the way, could you share some of your latests concerns? We may not fix them now, but we would like to avoid them on the future. As you say, the number of developers that uses the platform is rapidly increasing, and we want to empower them with the best options we have, that’s why we focus our tests on the newcomers, but one of the best ways to empower these guys is by having guru’s on our technology sharing your knowledge, on the forums, on stackoverflow… and for that we cannot “annoy” you =)
That’s why we want to learn with you, the community, and that’s why we have things like the Ideas zone (by the way we also had an idea to merge the find and the omni-search).