- Joined
- Dec 28, 2021
- Tests don't pass? Delete the tests, 100% pass rate.
while i havent seen them delete them, in my previous job i was working with my team to add junits to all of our codebase and the jeets would write the tests in a way that they would always pass without doing any meaningful testing of the code. basically they would hardcode a test to always pass just so we could get to the required level of code coverage. i was never able to explain to them this is bad and how to properly write a test case. i eventually gave up since the entire company was trash. (also illustrates that simply seting some metric, such as %code coverage, is actually a very useless thing to do)
it was a pajeet company hired on contract by a major us company because the jeets were so cheap. i got hired because simply because there was a requirement that some of the databases could only be accessed in the US so they needed some guys in the US to work part of their contract. i dont feel too sorry for them, and have no regrets on giving up, they got cheap and outsourced their work to jeets, you get what you deserve. and to nobody's suprise that entire codebase was a dumperfire, i am legit shocked that it ever managed to work at all.
- Plagiarize code and don't even bother to cut out the original guy's comments and license.
seen this. but ive seen more them copy paste code and do the bare minimum to hide it, but not enough that it isnt obvious it is copied code that i can easily just paste into google and get the stack overflow/ blog where it came from.
one more thing ive seen of pajeets. we eventually starting using sonarqube to scan our code. one of the things i would do is list code vulnerabilities, explain why they are vulnerable, and suggest ways to fix them. (i actually liked this feature of sonarqube, i found it useful.) the last part is key, since the tool would tell you what to do and a lot of times the jeets still couldn't figure out how to fix things.