I explain.
For example Unit Testing, testing is essential. However, sometimes a manual test is more effective, is fast, and it generates a quality code. I'm not saying that Unit Test is bad, but it's not a universal solution. But, there is a significant trend for developers that consider Unit Test a kind of game, where the goal is to achieve a 100% test coverage, no matter if it's useful or not. I checked many unit tests that are useless; they test nothing. For example, if you are testing database access (DAL, DAO, Repo), then you MUST test a real database, testing a mockup is similar to "I will test the database sans the database", is it crazy?.
Then, it's the libraries. Again, I have seen a lot of juniors programmers that are added dozen libraries. Adding libraries add more dependencies and dependencies are bad, sheesh.
I approve the people that want to convert the workplace, a fun yet productive space but, as a programmer, we are solving business needing and some programmers are not solving a thing but giving rounds and doing automatic jobs that produce zero results.
