Not saying that people don't try, and there is that odd politician who does come only from money. By and large most chief ministers victory can be explained not by money, but more by identity/group based politics.
This is pretty much also exactly the same to what happens in the US.
Buying votes happens mostly in slums and other non-affluent areas. These are the places where the concept of privacy hasn't yet formed and everybody knows what everybody else is doing. Also, a politician is not expected to work for them his whole term. It is natural to see your local representative only during the times of election. So politicians have the two key ingredients to enforce an implicit contract. But the biggest weapon these politicians have is intimidation. Since it's not hard to mostly figure out the faction that refused to vote for the money they took, they can be persecuted and intimidated.
Of course there's no official source to cite this. My driver is very chatty and quite insightful about the politics in India.
So, reading someone else's code can be like reading a model of something that has gone through dozens of iterations, where the bottleneck isn't really understanding "the code", but understanding the thing that is modelled, which the people writing the code are intimately familiar with, unlike you[1].
In my opinion, developing this modelling skill, in yourself, is much more important than watching the result of someone else exercising their modelling skill. A lot can be learned from observing someone else's solution, but this will always be secondary to learning how to craft your own.
[1] For example: try reading compiler code. People have been writing compilers for so long that reading and understanding this code isn't about understanding the actual code, but about understanding how a compiler is modelled (scanning, lexing, parsing).