Message I just sent my boss about a new person on a completely different team...

"Hey boss, would you be able to figure out who supervises [xyz] and ask them to... Supervise some more? Been getting a bunch of super basic questions and don't have time to train them up from scratch for [other team] right now"

We've got a case statement spanning 3.5k lines.

"you write the most interesting bugs"

Y'know how they say it's always DNS?

...it was DNS.

We should rename our "users" table to "losers".

It would be more accurate, plus the added benefit of security through obscurity - we'd be immune to little Bobby Tables.

Goodbye, imposter syndrome.

Today I patched a StackOverflowException bug (that I myself introduced a few months ago) which caused the prod application to crash the other day.

Now I truly feel like I belong! 😂

Windows updates are a bit like SAW, you either inflict the pain on yourself or wait until it is forced upon you.

🤬

12,000-line DAO file 💀

FUCK. YOU. SILVERLIGHT.

AND FUCK YOU DEAR EMPLOYER FOR NOT RETIRING YOUR SILVERLIGHT UI.

Issue reporter:
Feed from external service provider is overwriting the wrong things, pls fix

Resolution:
Service provider is sending duplicate unique IDs, you need to get with them to discuss

Service provider response:
This is a *RE-USABLE UNIQUE ID* . . . The bottom line is you should not use this UNIQUE ID as a primary key.

Feels like every damn day I'm learning about another language feature that we CAN'T use... So much legacy code everywhere.

C# is more like C-blunt at this point.

"I don't have the luxury of choosing clients... If I did, I'd have 0 clients"

"hey, you know that help site that our main app users rely on to know wtf is going on?"

"yeah...?"

"let's change the URL without pre-planning or advance warning for any relevant teams, and just tell them afterwards!"

"hell yeah, great idea!"

seems like information here is on a need to know basis, if you need to know then you definitely aren't getting it