How do I put "forced to cowtow to a product manager who doesn't know the product" into my resume?

As an addition, maybe add in "asked questions several times but was browbeat into conformity only to realize conformity was wrong" and "asked for support I never got, then thrown under the bus when I acted on my own on a deadline". If it helps matters, I have been in meetings I never should have been in and had to make decisions I never should have been in the position to make.

In a sprint planning meeting, tickets are supposed to be detailed prior right? Right? So why are people asking basic "what are we supposed to be doing in this ticket?" questions in this meeting? I proposed doing these meetings and as soon as the concept got hijacked I knew this was going to happen, but damn it I had hope.

And I am so sick of my product manager not knowing the product. These meetings go so fucking cock-eyed because this woman can't be bothered to know the damn product. At all.

Just had a meeting about what our product's vision was going to be. Without actually talking about what that vision was. It was a statement of the business goal amd some nonsense about how we were going to pick tickets based on reaching said business goal.

Like, yeah. That's what we have been doing. You are not new here so why are you acting like it. And yet these people are the ones who make more money than me. I need to start saying more obvious things. Maybe I'll be made a director.

Anyone else's job expect you to fix bugs in your niche app that even the global giants don't give a shit about? Like, have you seen the weird shit that happens with YouTube and Hulu? Our app has neither the staff nor the budget of these big brands, if they haven't fixed it, we probably won't.

Couple months ago I mentioned that the product group needed to involve engineering when making promises to the business. Otherwise they were going to write checks our asses can't cash.

Welp, now the situation has happened and I pointed out that a lot of things have been promised for delivery that we haven't planned for or even seen in engineering. And things that I have been harping on haven't even been accounted for and, unlike business promises, these are legal requirements. Now I'm the asshole because I pointed this shit out in front of the whole team.

I get the point of a daily check in meeting for the team. I really do. But when all it is is pushing pet projects and bitching about shit that has nothing to do with the entire team, it gets tedious. Also, why are product managers so needlessly optimistic and peppy? It's early in the morning. Stop it.

My boss is still forcing us to support IE11. Recently, we started having even more bugs with one of our vendors on IE. We filed bug reports with the vendor to fix it, and they came back with "no. Why would we fix anything for IE11? Not even Microsoft is fixing anything for IE11." Boss's answer: well, let's make a separate component for IE11. Probably using flash and/or silverlight. We asked about redirecting IE traffic to Edge, he said that's "the nuclear option." So, doing the thing that Microsoft suggests, that involves not much work at all is "the nuclear option"; ignoring industry standards and recommendations, introducing well known security vulnerabilities, losing money, and trying to circumvent the vendor that serves out our major product, however, is totally reasonable. Our IE traffic is less than 3% of our users at this point.

Holy shit. In a meeting that literally makes no sense. We're taking credit for work by claiming story points. Story points. How the hell does that work? Especially since we have told management CONSTANTLY that story points are abstract LOE shit and NOT time spent. Yet I suggest if we REALLY want to estimate who worked what we track time spent I get shot down. You can't get a concrete measurement from an abstract concept. Also, we're being encouraged to argue over who does what? What does THAT help? AND we're not even reestimating if we over or under estimating, but being forced to massage our numbers into the estimate. What the fuck?

Does anyone else's job just hate documentation? I have wasted most of the day trying to get our new build to work because I keep hitters snags that aren't documented. Hour release was delayed 6 hours because our QA doesn't have any kind of written procedure or checklist and missed bugs in something that is usually problematic, and I am being forced to stay online by a micromanaging boss that needs to realize he's not an engineer anymore. And I am supposed to have a feature done by today, but this clusterfuck consumed all of the resources I need. I'm polishing the ol' resume. Anyone looking for a remote .net dev?

Wish me luck. Looks like the feature I am developing is going to be late because QA doesn't feel like following the estimates we agreed on. We already identified that development was going to be the longest part of this whole effort and that QA was going to be relatively easy, but but no. Because this is the day we have to be "code complete", they don't want to test a relatively simple feature. In fact we had to talk them into even starting testing on it today. Even though regression day is Monday and they are basically going to be done testing their last ticket this morning. Like what the fuck were they going to do for the next 7-8 hours? They don't write any documentation. There are no reports to do. There are no meetings. Did they just want a virtual day off?

Edit: they are literally playing with people's careers here. This is not the first time I have had something delayed by QA even though they agreed that it was simple to test and it was delivered with enough time to fucking test. Then I get in trouble because of late delivery.

I do all this work to make an elegant solution to, frankly, a dumb requirement. And a newer dumber requirement comes out that requires someone to modify my solution. Normally not a problem. But this is a backend solution given to a frontend developer to modify. I told them how my solution works since it did 90% of what she needed. But instead, they reinvent the wheel and I have to fix it. I was supposed to be done with this 3 hours ago, but unraveling this knot is taking for fucking ever.

Web programming is great. Except, you know, WHEN THE TEST SERVER WITH THE API YOU'RE INTERFACING WITH ISN'T WORKING CORRECTLY!!! WORSE STILL WHEN YOU DON'T OWN THE FUCKER AND CAN'T RESTART IT!!! I hate my life sometimes.

Another pointless ass meaning. My fucking director and coworkers act like they have never had to do any frontend and backend development in parallel. We've been doing this for literally the lifetime of this project. It hasn't changed. And this literally spawned because the director can't give an actual answer to the real question of what the fucking requirements are.

Parents were supportive in that they forced me to go to college, but let me do whatever I wanted while there.

Pretty sure they still don't really know what I do.

The more I work with videojs-ima, the more I am convinced it is not the solution for what we are doing. Any time I try to figure out how to do a thing on my current project, the answer is usually "don't". Then I need to hammer the app til "don't" becomes "does sorta"

What does my current job hate descriptive names? Like to the point of active antagonism? We're a subscription based service. Why is SubscriptionExpiration the date you log in? Why does SubscriptionStatus only contain the name and id of product you're subscribed to and nothing to do with an actual status? All I need is the date a user subscribed. Why is this so hard!?!?

Is it common to have QA and Product Management in sprint planning? Cuz they are derailing sprint planning SO MUCH!!! I am internally screaming. Aaaaaaaaand they just extended the scope of one of the issues. Neat.

Alright so I have been trudging around in javascript land for a bit and one thing kind of bothers me (correct me if I am wrong I would love to be wrong on this). It seems like a lot of javascript, or at least frameworks, leave a lot of possibility for memory leaks. Like you can create an anonymous object with a method that just kind of hangs out and acts with no way to retrieve it and turn it off. Am I wrong here? Please tell me I am wrong. And for the record I know I can assign anonymous objects to variables in various ways, but I am not forced to.

Anyone use slick for carousel navigation? Have you had to deal with slow building of the carousels? How did you deal with it?

Ever work on a codebase that's so shitty, that if you do something in a generally accepted and expected way the entire product shits the bed? Cuz that's the situation I am in. Been working on the same fucking feature for like 4 sprints because it keeps being sent back because every time I adjust it to the shittiness that is currently in the baseline, someone changed something and it explodes again. And the worst part is that this is a well known and established problem. Basically every engineer, except the guy who wrote it of course, hates this system. Hates the baseline, and hates the platform. Yet I'm the one who is "losing trust" with the team, even though I get my shit up and running early all the time. They just break the foundation every time.

QA people hurt my head. "I found this issue" cool write it up. Proceeds to not write it up. "Hey this isn't working" yeah your on the wrong PR. For the 80th time. "Hey I just found out 4 days after deploying this key feature is no longer working" did . . . did you test it? I'm irritated. Probably because all of my tickets got sent to triage because I pushed them to the wrong PR. My life hurts. The burn out is real.

In case anyone wonders why I am PC over mac, I just had a macbook pro crash on me under a load my HP POS I bought 3 years ago for $750 calls Tuesday.

So my boss tells me that industry standard for serving images is that you have one image on the server that is approximately 3x larger than the largest size you need it to be and resize it on the client side as you need. However, a lot of the tutorials I have seen online lead me to believe that is not true. Is it? Because I have to serve up a whole lot of 150kb images for something I didn't even want to do in the first place and it's causing serious performance issues, even with lazy loading.

You know, I don't mind getting dragged if I deserve it. But it would be nice to have ALL the information I need to make an estimate BEFORE you hang me out to dry.

First I was told that work on this issue could be kicked down the road since we were getting big contracts. The next day the issue was in the sprint.
I tell you I won't be able to get it done with the business critical stuff you said absolutely had to be done that sprint (turns out we had 3 months of leeway even before COVID). You say alright cool. We push it to next sprint. The next day you say we have been pushing that issue too much and we absolutely have to get it done this sprint. At least have it so QA can look at it by Tuesday.
I give a preliminary look to QA cuz I found a bug, but they can test other shit about this fucking issue, but then get shut down fucking again because it isn't code complete.
STOP. MOVING. FUCKING. GOAL POSTS. AND. GASLIGHTING. ME.

And as a bonus, I disagree with the necessity of this work in general. I think it's fucking stupid, unnecessary, and zero value added. It's a management jerkoff issue that is going to piss off all of our users.

Kind of thinking of making one of those COVID-19 infection simulators. Might be interesting to use a particle swarm type of algorithm for it.

My job forces me to work 9-6 with a one hour lunch. Since I am forced to be full time wfh, I eat while working and take a nap during my "lunch".

I am much more productive.

*when forced work from home started*

Boss: look guys, since we aren't gonna be in the office we need to prioritize communication and fully utilize Slack, email, and company phones.

*today at 4pm when release is supposed to happen*
Boss: *crickets*

*1 hour later*
Boss: *crickets*
Me: what's going on with the release?
Coworker: QA found something late breaking we're trying to roll it back.

*1 hour later*
Work: *crickets*

*Release is 3 hours late and it's an hour after quitting time*
Work: *crickets*

In a meeting about how to make the app I am working on worse. They want the same ad to pop up every ten minutes during live video to plug and get sign ups for a newsletter. And in mobile they want it to take over the entire screen. It's so user unfriendly.

Pros of the pandemic . . . ?

Had food poisoning and was out for 2 days. Now we're all 100 wfh cuz of coronavirus so I was going to catch up. But then our build and deploy engine went down and since it is controlled by a third party vendor, we have to wait for the ticket to be fixed. I think the powers that be are telling me to get drunk, fuck the schedule.