Well.. It depends... If development is what you want to do, then it's not OK. In terms of losing your edge, I agree with you completely and I'm in a similar sit

Well.. It depends... If development is what you want to do, then it's not OK. In terms of losing your edge, I agree with you completely and I'm in a similar situation at the moment(though for different reasons): the company I work for is infuriatingly conservative. The newest thing in use is the oldest which is still maintained. Any technology invented after 2011-2 is considered witchcraft. And even suggesting something which would clearly make things better for everyone, results in a long convoluted answer as to why not(without an actual answer, just a way to brush it off) or "open a jira ticket in the suggestions project" if someone is busy. Basically this is just a formal way to tell someone to leave a comment in the guest book. And the "suggestions project" has tickets dating back to 2014, all of them completely ignored. While I appreciate that there are no pointless hour-long meetings discussing made-up acronyms and whatnot, the fact that I feel like living in 2010 is not just frustrating, I'm absolutely furious. So it's easy to see why I'm looking elsewhere, even if I haven't spent a whole lot of time here. But in my experience if you want to be a developer and live on the edge, steer clear of the "architect" types of roles and stick to strictly "developer" roles.