Dude I only got this job because you were offering an internship two summers ago. We don't have the budget for that. We're still working on the last changes you made and the plan was to return to the normal schedule after we implemented your "fixes." Why do you not know this stuff man you're the boss, you should know our team has been cut down by half over the past 6 months. Where are we going to get the time for this? We're already pushing crunch time. You just got here and had a 1 hour meeting now you know everything we're doing?
What I'm thinking: WHO THE FUCK KEEPS CHANGING SHIT ON THE REQUIREMENTS TRACEABILITY MATRIX MASTER DOC? I SWEAR TO FUCK I WILL REVOKE SHAREPOINT ACCESS FOR EVERY LAST ONE OF YOU PERPETUALLY BIKESHEDDING DIPSHITS!
What comes out: Uhhh, yeah, I think this is going to expand our scope and we need to revisit scheduling and resource allocation. Is this still priority for the current release milestone, or can it be pushed back as not needed for a minimum viable product, in which case these new scope changes can go back in our priority queue? I can go ahead and refactor some of the existing interfaces to account for future change to the implementation in these couple of submodules, but implementing those changes right now is going to throw our user acceptance testing schedule out the window.