TLDR: Scope creep.

Fuck it! I hate scope creep! 2 days before the deadline is due, slip in a little scope creep to bolster your already ambiguous as fuck scope! Of course, more fool me for taking on a project with a scope as ambiguous as this one. Or for accepting the 'just do x and y and your done' as gospel. But then again I enjoy paying my bills and you know, eating from time to time!

Fuck 'em! Fuck Clients! Fuck Scope Creep! Fuck Ambiguity to it's very Fucking core! Fuck it! Fuck me! Fuck code! I'm venturing under my table for a little cry and a sulk, then back at the god-damned grindstone to finish the project and all it's creepy scopy bits before the deadline tomorrow! FUCK!

For fucks sake...
If it is a new feature, out of scope for the next release ...

It is OUT OF SCOPE FOR THE NEXT RELEASE, MKAY?????

Do any other junior devs get secret joy when the architects and senior devs argue out on open?

The disallow: in a robot.txt file is the web crawler version of new phone who dis?

After lunch today I had review meeting with the stakeholders on project where the content was late plus a lot more than previously stated requiring changes to the angular app. So I ate a shit ton of garlic from the salad bar as we sat and my desk and reviewed it.

Commitizen Fucking Sucks!!!!

It makes me commit less and write shittier commit msgs because I am not sure if it’s going to bark at using a capital letter.

If someone asks you for a quote on a project and they use the phrase "It's like [SOCIAL_MEDIA_SERVICE], but for [TARGETED_DEMOGRAPHIC]" and they don't have VC funding, you're gonna have a bad time.