What is the absolute minimum for a merge request? Is it that the code compiles? Because that's a super low bar. A bar still missed by some...

What is your preferred coding style? Such as those imposed by Checkstyle.

Seen it done wrong so many times makes me wonder what it may look like if done right. What are your thoughts on "micro-services" and maybe specifically "AWS Lambdas"?

I find it very dangerous to work with folks that prefer speed over quality. I would prefer that folks do not request me to code review if they are going to ignore my comments and push to production without answering all my questions.

How many devs are also really into creating music?

Podman or Docker, and why?

Has anyone ever worked anywhere that actually had complete user stories to work on? Every job I've had requires me to ask clarifying questions for almost every part of a ticket before I work on it. I wonder how nice a job could be if acceptance criteria and expectations were known before a ticket was assigned.

Spilled juice on my desk. Now everything "feels sticky". I quote that because nothing is actually sticky, but I was so upset that now I think I feel sticky when I don't. I keep checking my fingers after typing or anything. Never having juice in my office again...

How can one phrase things in a way that they won't be ignored? As in how to ask questions that will lead to actual answers and a path forward instead of being ignored or dismissed as "not enough"? Too frequently everywhere I work I've experienced the pattern that I'll be close to identifying a problem/solution but my mentions are often dismissed, and then months later when things are really bad someone else, usually a manager or higher ranking engineer, says the same exact thing and it is suddenly this huge revelation. Of course I can share links to previous meetings about the topic where I tried suggesting whatever this is, but it again goes ignored as "contextually invalid" or something similar.
Is this normal? Do I just need to wait until I'm a higher ranking engineer to earn this respect of opinions?

Isn't it awesome when someone's "bugfix" causes new bugs which prompt "bugfixes" for the bugfixes in the same merge request?

How do you help coworkers that gaslight you about their understanding and skills? If they outright refuse help, yet their work is consistently low quality and unacceptable?

100 new lines of code. 6 of them are new, the rest are tests. 30 comments and 100 commits later, changed code still not getting touched by tests. Who tests mocks?