8 karma · joined May 12, 2013
> For a new project there aren't any well defined states of the code that make sense to be persisted. This means the commits will be arbitrary and their messeages not very meaningful.
I didn't understand this? The problem is well scoped and defined. Regardless of whether it's a new project or old, we expect candidates to be able to split their work as atomically as possible.
Took us about a week to write everything down the first time and then we continuously updated it until it reached the current state.
We had the advantage of being a "public by default" company, so there was no need for approvals of any sort.
But this guy seems too immature to take seriously. In fact, I stopped taking him seriously at the first mention of "Shitizen". That doesn't really do him any favours.
There are good devs and bad devs everywhere. The problem in India is that the average software developer is one not because they wanted to code, but because the family pushed them to do it since it pays well. As a result, you get a bunch of devs who don't really care about what they do, and are incompetent.
The kicker is that these devs are the ones the rest of the outside world works with since they come to India for cheap labour, and hence, you get the impression than coders in India are mediocre.