Jayesh:
IN GENERAL
Jayesh was a really nice guy and very bright. I think he'd be great in a team, but his background is in Live Services. i.e. not in primarily in developing software: His expertise is in maintaining it, and the surrounding infrastructure. For that reason he lacks knowledge in key areas. He is a subject matter expert on the domain he works with (i.e. not transferable), not in the generic technology he works with. He hasn't worked in a modern development team and although he is clearly bright and capable he is unaware of how development teams operate and is unaware of the kinds of technology that modern development teams use (he has been defaulting to using shell scripts where build tools should be used). It would help him enormously to have a dev project at home to get him up to speed on all of the below categories. Intellectually he seems very adaptable and capable. For that reason although Jayesh is a "no", he might be good for a live support role that might lead to him learning "proper" modern development practices.
JAVA & OBJECT ORIENTED PRINCIPLES
He knows how to deploy java artifacts and knows what a .war file is. He has not used any modern frameworks and is aware of that as a limitation. He was however aware of the basic object oriented principles and some design patterns, he understood the singleton and factory patterns.
JAVASCRIPT
He has no javascript experience. This is not therefore, a good basis for understanding the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jayesh doesn't know TDD at all. he does have experience of unit testing however and none functional testing such as load testing. These skills are useful in modern development teams. His experience of testing generally was adequate, just.
AGILE METHODOLOGY
Jayesh understood some of the theory, but did not appreciate how different Agile is from the traditional approach. He does not work in a true Agile environment. He mentioned daily meetings (stand ups) and a show and tell when asked about the agile ceremonies (and was able to describe them), so he does know some. He knows some agile but has some of the principles confused with traditional waterfall practices.
RESTFUL WEB SERVICES
He has not done any REST, only a related technology SOAP. Although SOAP seeks to provide a similar functionality to REST, the approach is quite different. This will not help Jayesh. He would struggle without REST.
SOURCE CONTROL MANAGEMENT
He has used SVN and pcvs. He is aware of the concepts. He has sufficient knowledge of this aspect but is by no means an expert. He has only used a GUI for operating svn and is unaware of any commands used on the command line, however this should not present a problem to his operation in a modern team.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jayesh knows what it is but hasn't used it. They have a seperate team for it. This would present a problem. Jayesh would have worked closer with CI (or the CI team) if he was on a proper dev team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Unusually, Jayesh has only used shell scripts for building software. This is indicative of him being unaware of modern development practices. This is an archaic and idiosynchratic way of doing this. The team he is working in does not at all seem up to date.
CSS + HTML5
He has not used HTML in any way but has speculated that he can do it. This would be a big probem.
Jayesh was a really nice guy and very bright. I think he'd be great in a team, but his background is in Live Services. i.e. not in primarily in developing software: His expertise is in maintaining it, and the surrounding infrastructure. For that reason he lacks knowledge in key areas. He is a subject matter expert on the domain he works with (i.e. not transferable), not in the generic technology he works with. He hasn't worked in a modern development team and although he is clearly bright and capable he is unaware of how development teams operate and is unaware of the kinds of technology that modern development teams use (he has been defaulting to using shell scripts where build tools should be used). It would help him enormously to have a dev project at home to get him up to speed on all of the below categories. Intellectually he seems very adaptable and capable. For that reason although Jayesh is a "no", he might be good for a live support role that might lead to him learning "proper" modern development practices.
JAVA & OBJECT ORIENTED PRINCIPLES
He knows how to deploy java artifacts and knows what a .war file is. He has not used any modern frameworks and is aware of that as a limitation. He was however aware of the basic object oriented principles and some design patterns, he understood the singleton and factory patterns.
JAVASCRIPT
He has no javascript experience. This is not therefore, a good basis for understanding the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jayesh doesn't know TDD at all. he does have experience of unit testing however and none functional testing such as load testing. These skills are useful in modern development teams. His experience of testing generally was adequate, just.
AGILE METHODOLOGY
Jayesh understood some of the theory, but did not appreciate how different Agile is from the traditional approach. He does not work in a true Agile environment. He mentioned daily meetings (stand ups) and a show and tell when asked about the agile ceremonies (and was able to describe them), so he does know some. He knows some agile but has some of the principles confused with traditional waterfall practices.
RESTFUL WEB SERVICES
He has not done any REST, only a related technology SOAP. Although SOAP seeks to provide a similar functionality to REST, the approach is quite different. This will not help Jayesh. He would struggle without REST.
SOURCE CONTROL MANAGEMENT
He has used SVN and pcvs. He is aware of the concepts. He has sufficient knowledge of this aspect but is by no means an expert. He has only used a GUI for operating svn and is unaware of any commands used on the command line, however this should not present a problem to his operation in a modern team.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jayesh knows what it is but hasn't used it. They have a seperate team for it. This would present a problem. Jayesh would have worked closer with CI (or the CI team) if he was on a proper dev team.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
Unusually, Jayesh has only used shell scripts for building software. This is indicative of him being unaware of modern development practices. This is an archaic and idiosynchratic way of doing this. The team he is working in does not at all seem up to date.
CSS + HTML5
He has not used HTML in any way but has speculated that he can do it. This would be a big probem.