Overengineering. I didn't knew before is possible to spend so much time on discussing how to reinvent the wheel. Some people may tell it's ensuring the quality but for me, for QA responsible are tests and code review.
I think this does indeed happen a lot. I think most developers, given the choice, would prefer to build as many things as possible themselves - there's more of a feeling of learning and accomplishment in this - you feel more like an actual architect/developer than a manual labourer. Obviously not the best approach in a business setting though :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Overengineering. I didn't knew before is possible to spend so much time on discussing how to reinvent the wheel. Some people may tell it's ensuring the quality but for me, for QA responsible are tests and code review.
Code review is for the birds.
I think this does indeed happen a lot. I think most developers, given the choice, would prefer to build as many things as possible themselves - there's more of a feeling of learning and accomplishment in this - you feel more like an actual architect/developer than a manual labourer. Obviously not the best approach in a business setting though :)