This is why part of my profile says "reformed rocket scientist". I spent a little under two years working for a NASA contractor on their sounding rocket program. The problems I was paid to solve were relatively un-interesting (find the best ways to fit the experimenter's data requirements into our ancient, antiquated, badly-in-need-of-replacement hardware). The problems the experimenters were solving were actually fascinating, but I didn't get much exposure to their side of things.

Now yes, I am struggling with Information Assurance people and their cantankerousness, but I also have the unique pleasure of being the primary data scientist on this very large project, which is exposing me to new things every day. I just haven't had an environment for learning this rich before.

You're right, but at some point, I need to draw the line of whether I can actually do the work and be productive instead of fighting the system.