I have no problem with offering ideas and suggestions when discussing how to build software, but honestly, I don't care if management decides to go a different

I have no problem with offering ideas and suggestions when discussing how to build software, but honestly, I don't care if management decides to go a different route. I'll code what they want the way they want it the best I can. That's the job. This approach can lead to some "I told you so" moments when I've been ignored and I deal with those when we run into them. Over the years I've seen a lot of my coworkers get overly upset in these kinds of scenarios and have endured way too much time listening to them complain about it. The thing is, there's almost always more than one way to do something. If it's my job to choose the route I'll do that and lead the way, and if it's not I'll follow the route chosen but I don't see any reason to get hurt or frustrated by it because I'm getting paid the same to work on it no matter which route is taken. That said, there have been a few times when my route wasn't chosen and we got stuck right where I said we'd get stuck and in those cases the project either collapsed or we went back and started over using the tools and methods I suggested. Doing that "feels good" but it pays the same.