If I might post an experience of such please thank you very much no alright then.
I was technical lead on project to deliver change to a suite of legacy applications. We were a dependency for a 16m SAP rollout. However, my project was not part of the SAP programme. Also from a different budget. We did not meet with the SAP team, and were not invited to their project planning meetings.
The reason, I know for fact, is that we were the patsie. Left outside in the cold to be hung from the highest yard arm as the excuse for the SAP delivery being late.
This is project politics. So our deadline was entirely arbitrary, based on another entirely arbitrary deadline set by the BOD to the SAP team. They called it a "drive to date" rather than a deadline. Also in meetings the senior exec had a "pet phrase of the week" so it seemed. One week it was "skin in the game". So every meeting they would drop the phrase in, no matter how clumsily or incorrectly. It was something of great amusement to me, and I have learned to smile, laugh, pee myself with hysterics internally while still waters run very very deep.
Now in this situation the temptation is to sit around and scoff at these ridiculous deadlines, just how idiotic the management are with their stupid "drive to dates" and buzzphrases. This is a valid thought process, but it must not end there.
At the time I was just back in work after a nervous breakdown, and when the technical lead left with a nervous breakdown (seriously) and I was asked to take over as tech lead I had to do some soul searching before accepting.
Then I decided to not only turn this project around, but also then turn it around in such a way that these SAP guys would be in the line of fire. They were shameless. Each meeting would start with "Ok to first order of business, who can we blame ..." then the eyes would swivel toward me and my project. More grist to the mill.
So the tactics were simple. Accept the deadline. Prioritise the work, estimate the work, find out what fits. So for each mini deadline, we were always on blob. Cover yer arse emails all in the drawer. Because one thing I do know is I nearly always see problems coming way before anyone else does. One day I think I may make a good PM.
In the end we called the tune, delivered on time and discovered some dependencies going back the other way and pointed them out in good time.
To be fair to them, they went live only 2 months late, which for a SAP programme is terrific. I learned a lot from them about "management reporting", and the art of "spin". It's ok so long as you don't get found out, and you're confident you can make up the lost ground.
The point is a date is just a date. It's nothing to loathe, or fear or moan about. It's just a string of numbers written down. If you learn how to use a deadline to your advantage you'll even start to love them, like Stockholm syndrome I suspect.
The greater problems arise when people or projects you depend on don't share your sense of urgency, through bad planning. Stakeholders that are only "dotted line" reporting to the board. These are the things to watch out for.
When in life you have great pain, is definately the time when you learn the most. Ever heard the expression "no pain no gain". The same is true for projects. The way to build a career is to think that if you work your nuts off and hit the deadline then you not only have a good reference, but a great story to tell for interviews to come.
Try and zoom out and see the bigger picture, and stop letting deadlines annoy you but rather see them as empowering.
HTH
PS The above is all true.