Complain about it. Walk away from it. Work on it. That’s it, no further explanation needed. You can apply all three to any problem – get angry at it at first glance, take a breather from it and then come back to work on it. Nothing wrong with that approach, just don’t focus on the first two for too long.
“I’m better than them, I should be doing that?” But you’re not, so you can either keep dwelling on it, move forward. No one is stopping from going ahead and doing it on your own, somewhere else, in another role, perhaps just not with there. The choice is up to you how long you want to let it hold you back.
“No, but I can learn it.” That’s all I need to hear in an interview, if I can hear that, I don’t need to dissect whether you know something or not or what level of syntax you know. That tells me that you are honest in what you know but you are driven to learn something new and contribute to our team by going beyond what is asked of you. What more could you want?
There are many stories of developers retiring and going into the forest, dropping all technology behind them and just being with nature. I don’t think this is true for just developers but for any job where there is a great deal of complexity that lives within our minds where the simple task of “dumping” everything out is cathartic and our minds are left to wander. Oddly enough, part way through emptying my wandering mind I…
I’ve taken to reading the autobiographies of singers and bands I grew up with. What is consistent in each biography – they were all looking for something bigger than themselves, and they were willing to work for it to get there. Doesn’t matter where they came from, or how creative they were, they were all willing to work for it and they had the drive to not give up on it.