Found this in our code today

Interlude (Break Room)

Me (Lead Developer), HR lady (HR)

Enter stage right ME

Me > "Oh hey HR lady, how was your vacation?"

HR lady > "Well, we didn't end up taking the kids to Disneyland after all."

Me > "What? Why not? Come on, I have to hear this!"

HR lady > "Long story short my husband and I are getting a divorce."

Me > "Oh shi-"

Act I

Me (Lead Developer), Boss (Head of IT), CEO

> enter stage left CEO

CEO > "Alright Boss, give it to me straight. Are we going to be able to release app x by this date?"

Boss > "Yup we'll have a beta release on that date"

> exit stage right CEO

Me > types long email to Boss outlining exactly why we won't be able to release app x anywhere near that date, beta or otherwise, because:
1. We have a development team of 2
2. I've never developed an iOS app before
3. Developer 2 is still trying to understand git, because
3a. Developer 2 isn't even a developer (but he's doing iOS front-end so w/e)
4. We don't have the required database systems in place
5. Or CRM
6. Or CPQ
7. We'll need to conduct a security audit

Boss > "yeah, but CEO is gonna need to hear that date a few more times before he can fully understand"

Me > *internally screaming BUT YOU HAVEN'T TOLD HIM THAT AT ALL*
"ok cool just glad we're on the same page on that one"

Holy shit. Do NOT open a Wells Fargo banking account. On top of their ridiculous password limitations, your password is NOT CASE SENSITIVE. I tested. Caps lock, no caps, a mix, it doesn't matter.

More info on the password limitations at my other rant https://devrant.io/rants/905148/...

Set up an account at Wells Fargo today and they told me the password requirements... This is a joke right?

When you write your own unit tests, and feel like an actor doing their own stunts.

No? Anybody?