8
ctnqhk
251d

Me: [jira comment] We have similar text for the mobile version of the site already. [includes screenshot of what site looks like now] Are you sure about this?

[radio silence for a few hours]

Me: [slack] I want to follow up.

Web Operations: What’s the issue?

Ooh k. Slack messages can have a tone.

Me: I just want to confirm we’re not repeating copy.

Web Ops: We’re not.

I complete the ticket and submit for review. The C-suite for my department reviews.

C-suite: [to web ops in JIRA comment] This looks weird. Is this right? [sends screenshot of my work because there is repeated copy, like I said there’d be]

Web Ops: [in JIRA comment] Oh, I thought X was questioning the request. X changed the wrong text.

C-suite: The website has always looked like that. You’re looking at X’s screenshot for the current website. Look at the screenshot I sent over.

Later, I complain because web ops was completely unprofessional with the comment about “questioning the request.”

C-suite: Web Ops is working hard. It’s our busy season and it’s their first time dealing with it. You know, I’m going to teach them some css and html so they can make content changes in the CMS and they’re not sending over changes so often and bothering you.

Me: [to myself] ๐Ÿคจ wtf so it’s ok for web ops to treat me like dirt. And in writing. And with service that’s version controlled—JIRA emailed web ops comment to me. And lol no ๐Ÿ˜‚ on teaching them how to code. That’s such bullshit. We all know you’d never allow them to edit the CMS because they’d fuck up the site. And they wouldn’t do edits anyway because it’s beneath them. And idk how this relates to web ops gross behavior.

A few days later.

Me: I was offered a job elsewhere. Here’s my two weeks notice.

C-suite: Can you push back your last day? It’s our busy season.

Me: Nope. Bye Felicia.

Comments
  • 2
    Those are just signs of a company culture with some problems ..
Add Comment