4 ms·
I'm guessing here but it seems this is in India, right? I have worked with a number of Indian developers, e.g. WiPro and Infosys. They are often fairly new deve
by abdulhaq 18y ago
I'm guessing here but it seems this is in India, right? I have worked with a number of Indian developers, e.g. WiPro and Infosys. They are often fairly new developers (< 5 yrs) and very clever. There are some cultural issues that apply here. From what I have seen most of your team will not have had much formal training but will have learnt on the job. This means they have probably done a lot of 'hacking' without paying much attention to testing, and now the project needs refactoring to smooth out the recent features that have been bolted on. However, this is probably too difficult to do because the code base is too disorganised.
I recommend you get in a senior developer with experience of TDD and large systems. Have a fresh start and boost morale by showing how a new approach can help clean up the code. It will need your support to give them the time to add the tests, refactor and clean up the code. Progress will appear to stop for a while, but it is well worth it. You will end up with a much better product.
- abhishekdesai 18y agoyou guessed it right, this is India. developers have <5 years of exp and they are without formal training. however as you said they are clever and have not done bad coding. i.e. they have not done messy code which can not be understood by other developers or not according to the standard. infact that is where cakephp helped us a lot. it does not allow you to take too much room while developing so you have to try hard to do bad coding in there. Your suggestion is well taken but I am not sure whether there is a need to rewrite the code.
- abdulhaq 18y agoOK, fair enough. Have you asked them what they think is the best thing to do?
- abhishekdesai 18y agoWell not in this typical sense but yes I have always given them freedom to complete tasks on their own.