I love when devs bitch about the size of PRs on a very standard sized one. They're all related changes that can't be broken up. Do you want the app to be broken between PRs? He spent more time bitching about the size of the diff and telling me how he does it better instead of just reviewing the code. A tip or an ask is one thing, this was a wall of text.

Oh and he still didn't approve the PR, which I know he looked at, and didn't leave any blocking comments.

Kinda pissed. Ordered a WD red plus 8TB on November 20th from newegg along with some other stuff. He drive showed up DOA on the 26th, tested everything I could to make it work. But in the end I couldn't even get it to initialize.

Ok. No problem this happens. request a return and replacement.

Got that in today. Over 2 weeks later. Fucking EXACT same problem.

and just to make sure I'm not fucking crazy I grabbed a 1tb thats been sitting on my desk unused for years. Plugged that into my NAS. Works fucking perfectly. Even able to pull it and wipe it using my USB drive reader on my desk after. I can even fucking reinitilize it back and forth from mbr to gpt.

Not asking for replacement this time. Just refund. Gonna order directly from WD. If this one fucks up I'm switching to Seagate for a couple of years

There has to be a software project bingo somewhere where I could just mark one item at a time of what's wrong and should be fixed, eventually leading to the same loop all over again. Items include, but are not limited to:

- The application is too tightly coupled
- There are too many repos and people can't keep track
- Someone forgot to create a naming convention for everything
- Nobody is reviewing pull requests
- Someone opened a PR for their 1 month of work
- Some team created a service for themselves, that doesn't cover use cases for every other team (who didn't tell anyone they needed it), thus it was a bad thing
- Business owners telling something needs to get done now and go talk directly to a developer
- Nobody thought about network latency in microservice architecture
- There's an invalid translation in this string, let's push the MVP another two months to make sure everything is perfect before launch
- The API gateway has business logic in it
- Business wants to focus on output, development teams in outcome
- "You need to request a virtual machines from the IT department so we know you won't mine bitcoin there!" Takes two months to fulfill that request.
- <add documentation here>
- 675 vulnerabilities in packages
- People complain about not knowing what others are doing, but nobody wants to speak up

My boss has been pretty insistent on us writing good tests (which I wholeheartedly agree with) for our new project, and being the less-experienced junior that I am, asked if we could get some guidance or a demonstration.

Took two weeks, but I finally got it said guidance... by opening a pull request with tests that weren't absolutely perfect.