QA In Charge of Merging PRs

Thoughts on QA being in charge of merging PRs SWE with 7 YoE here, and not in those years have i ever seen or heard of this. So i currently unfortunately work in a shithole with no standards. We generally have no code reviews, no one cares about quality, and quantity is above all and is literally stated out every now and then "do whatever, just get shit out!". Recently they've decided that a QA person should be in charge of merging PRs, these PRs could come from FE, BE (across two different languages and frameworks). Obviously i should have left this shithole a long ass time ago but unfortunately life happened and I've been here for a few years now. The lack of standards, the absolute shit codebases, the lack of concern from anyone for best practices or the right way to do anything has killed me everyday. How do i survive this role until i secure another? I literally want to quit and would rather be jobless than endure anymore of this shit show

A Reddit post describes a software engineer working in a chaotic company where a QA employee is suddenly made responsible for merging pull requests across different languages and frameworks. The writer complains about missing code reviews, poor standards, and pressure to prioritize quantity over quality. The joke is the exaggerated despair and relatable depiction of a dysfunctional workplace, making it suitable as a reaction to terrible engineering processes or a miserable job. EN: A Reddit post describes a software engineer working in a chaotic company where a QA employee is suddenly made responsible for merging pull requests across different languages and frameworks. The writer complains about missing code reviews, poor standards, and pressure to prioritize quantity over quality. The joke is the exaggerated despair and relatable depiction of a dysfunctional workplace, making it suitable as a reaction to terrible engineering processes or a miserable job.

• @gentoomemes / 10523 2024-04-10