I would react the same if I had worked on a really really tough problem and made an incremental advance, which I thought was a breakthrough, but everybody dished it because they didn't understand it.
I was once part of a company that thought it had superior technology that everyone else "didn't understand." It was true, it had marvelous technology. It was also true that lots of people didn't understand it.
Here's what it also had: 1) a deployment system everyone agrees is a pain in the @@@, which they never paid much attention to, 2) user interfaces which didn't repaint themselves like native widgets and which looked terrible and had terrible APIs, 3) intermittent bugs the customers kept reporting and getting disregarded and blamed for, 4) a less than open, "not invented here" culture with a big dose of "us versus them."
It's cool to make an incremental advance. The hard part is getting people to understand it. The hard part is reaching your audience. For this, it's more productive to enlist their help, not to blame them.
I was once part of a company that thought it had superior technology that everyone else "didn't understand." It was true, it had marvelous technology. It was also true that lots of people didn't understand it.
Here's what it also had: 1) a deployment system everyone agrees is a pain in the @@@, which they never paid much attention to, 2) user interfaces which didn't repaint themselves like native widgets and which looked terrible and had terrible APIs, 3) intermittent bugs the customers kept reporting and getting disregarded and blamed for, 4) a less than open, "not invented here" culture with a big dose of "us versus them."
It's cool to make an incremental advance. The hard part is getting people to understand it. The hard part is reaching your audience. For this, it's more productive to enlist their help, not to blame them.