4 f*ing years since the app is published and f*ing QA team still can't read f*ing logs and find out why the f*ing backend messed up and f*ing blaming it on the frontend in a f*ing scenario that has nothing to do with the f*ing REST API. F**********CK!

R&D: here's a really convoluted qualitative AND quantitative algorithm we want you to implement
Me: *asks to the meaning of one of the columns in a spreadsheet*
R&D: yeah that's probably wrong. We'll get back to you

So turns out my manager wants me to do QA automation (not in Espresso btw) of my own items "because we're all in the same team". The weirdest thing is that she's obsessed with "best practices" about daily iteration work such as not starting to work on something until test planning is done (she gets CRAYZEEE about that). Violating one of the core development principles is out the window so I guess the question is am I in a good place to ask for a raise since I'm going to have dual roles?

Today I got a reply to a PR comment from a coworker literally stating that "it's not a good practice to add unit tests to hotfixes".

I can't, just can't. Left me speechless. Wonder where this guy gets his "good practices" from.

OK...

Seriously, where is people learning Android these days? The School of Retards? Gee-sus christ!

Every. Single. Time. I've tried to learn and implement proper Unit/Instrumentation testing, the main Android devs decide to go for something else or introduce some feature or Gradle plugin that breaks every tutorial out there. I find it way easier to just test everything manually than learning the new yearly trend. Am I the only one?

Last nite, one of my projects started crashing with a ClassCastException because it couldn't cast a string to a boolean, inside an if. This is Java. You can't even run a project if you evaluate a string inside an if. Has anyone seen such a thing before? I'm running BBQLinux which at least for me it has a lot of permissions issues and somehow things got so f'd up that it even messed up the Android image to a point that the compiler couldn't find a method to set a string into a TextView. I'm not kidding.