Emily, I'm sorry you are going through this, but it seems to be pretty common in the rapidly changing world of software engineering. I've been bitten by this as well, years before I came out.
The cause, such as it is, appeared to me to be folks trained in more recent trends in software practices combined with managers (think Pointy Haired Bosses) whose ear they were bending. The purity of some piece of methodology just wasn't found in implementations of software that had to meet poorly defined and constantly evolving customer demands (higher level software developers, in my case), that had grown over a decade of use and development.
I sat through too many meetings where I was told my projects would have been much more manageable if only I had adopted proper pair programming practices to leverage spiral development in an agile scrum environment... Auggggh! And why on earth was something coded this way? (Because that's how the hardware works, dear... Chips have bugs, too, and we aren't spending $200K to spin the part when a hundred lines of code fixes it...)
It gets insane being nitpicked and critiqued by someone who "wasn't there" for the design and development process. Very frustrating, but you might be able to get something out of it if you can get the other folks to engage constructively. That is, explain why something had to be done a certain way, the constraints involved (tech, budget, available skills on the team, timeline...), and ask for input on what can be done to avoid these constraints on future projects. (It always comes down to time and budget, and we all know what happens when we ask for more of either...)
Unless things are really unprofessional at work, it's not likely to be related to your transition, as much as the usual workplace dynamics.