Jader:
IN GENERAL
Jader is a fine and experienced developer. He has a few weaknesses that we identified together but nothing of major concern. He is experienced and has used these types of technology many times before. We discussed software development practices and Jader was able to offer detailed and legitimate opinions. He could do with brushing up on REST a bit. No big problems. A definite recommendation from me for Jader.
JAVA & OBJECT ORIENTED PRINCIPLES
He was aware of what .war files are and what to do with them. He offered a succinct definition as to what software development frameworks, pointing out that they aid software development, allow programmers to code more quickly and remove boiler plate concerns from the developer. He has recent experience of Spring, having used it for the last 6 months. We discussed design patterns and Jader struggled a little with being able to explain polymorphism and code reuse and at one point was confused about "overloading". He was able to correct himself quickly and I think these were momentary lapses given his wider knowledge. He was aware of singletons, producer / consumer / factory patterns and was able to discuss them in detail.
JAVASCRIPT
He has used Javascript and is able to get code working quickly and efficiently. He has not written anything complex from scratch and has heavily relied on the javascript framework JQuery. This is a good basis for the course. He is keen to learn more here.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Although Jader got this question wrong in the tests, in hind sight he got it right straight away and was able to give a good explanation. He hasn't used this method of development, but he was very well aware of testing in general. Hi s knowledge and experience in unit and integration testing was good. He has used mocking frameworks like mockito. This level of experience is fine.
AGILE METHODOLOGY
He has worked in teams that have been agile but not to a purist degree. He recognises that although his team does regular stand ups and planning sessions, it should be improved to take on the wider principles of agile methodology. He is keen to join a team where agile is practiced in a way consistent with his very good knowledge of the subject. He was aware of the concept of MVP in detail (which was why his answer to the Agile question was correct and perfectly explained.) No problems at all with Jader on this.
RESTFUL WEB SERVICES
He was aware of the verbs and was able to explain what they were and name them. He struggled when describing what each verb represents, indicating that although he has some experience here it would in the early stages be an open book exercise. In general he speaks the language of the industry, but this was a relatively weak area for Jader. This should not discount him given strengths in other areas.
SOURCE CONTROL MANAGEMENT
he is very well aware of source control management and uses it regularly. He is aware of how it link in with build tools and CI. No problems.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used Jenkins at his previous place of work (Volvo). He understands it's purpose very well. He has never set up a job (which isn't a problem) but has operated in a CI environment regularly and is very familiar with it.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has used Maven but not ant. He is very well aware of convention over configuration and through our discussion of the subject answered all of the questions before they were asked. No problems at all here.
CSS + HTML5
He has used only the basics of HTML and he does not have any HTML 5.
Jader is a fine and experienced developer. He has a few weaknesses that we identified together but nothing of major concern. He is experienced and has used these types of technology many times before. We discussed software development practices and Jader was able to offer detailed and legitimate opinions. He could do with brushing up on REST a bit. No big problems. A definite recommendation from me for Jader.
JAVA & OBJECT ORIENTED PRINCIPLES
He was aware of what .war files are and what to do with them. He offered a succinct definition as to what software development frameworks, pointing out that they aid software development, allow programmers to code more quickly and remove boiler plate concerns from the developer. He has recent experience of Spring, having used it for the last 6 months. We discussed design patterns and Jader struggled a little with being able to explain polymorphism and code reuse and at one point was confused about "overloading". He was able to correct himself quickly and I think these were momentary lapses given his wider knowledge. He was aware of singletons, producer / consumer / factory patterns and was able to discuss them in detail.
JAVASCRIPT
He has used Javascript and is able to get code working quickly and efficiently. He has not written anything complex from scratch and has heavily relied on the javascript framework JQuery. This is a good basis for the course. He is keen to learn more here.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Although Jader got this question wrong in the tests, in hind sight he got it right straight away and was able to give a good explanation. He hasn't used this method of development, but he was very well aware of testing in general. Hi s knowledge and experience in unit and integration testing was good. He has used mocking frameworks like mockito. This level of experience is fine.
AGILE METHODOLOGY
He has worked in teams that have been agile but not to a purist degree. He recognises that although his team does regular stand ups and planning sessions, it should be improved to take on the wider principles of agile methodology. He is keen to join a team where agile is practiced in a way consistent with his very good knowledge of the subject. He was aware of the concept of MVP in detail (which was why his answer to the Agile question was correct and perfectly explained.) No problems at all with Jader on this.
RESTFUL WEB SERVICES
He was aware of the verbs and was able to explain what they were and name them. He struggled when describing what each verb represents, indicating that although he has some experience here it would in the early stages be an open book exercise. In general he speaks the language of the industry, but this was a relatively weak area for Jader. This should not discount him given strengths in other areas.
SOURCE CONTROL MANAGEMENT
he is very well aware of source control management and uses it regularly. He is aware of how it link in with build tools and CI. No problems.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used Jenkins at his previous place of work (Volvo). He understands it's purpose very well. He has never set up a job (which isn't a problem) but has operated in a CI environment regularly and is very familiar with it.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has used Maven but not ant. He is very well aware of convention over configuration and through our discussion of the subject answered all of the questions before they were asked. No problems at all here.
CSS + HTML5
He has used only the basics of HTML and he does not have any HTML 5.