Jordy:
IN GENERAL
Jordy had a lot of work to do to get up to speed. He seemed to have a significant gap in his experience during recent years and had a home project. He lacked modern experience working in teams but he had clearly been very senior and capable in the past. He had too many gaps in his experience to be able to recommend. He would fit in just fine as a junior developer, no doubt he would make very quick progress and be able to mentor the other staff in time. He has significant old style experience and academic knowledge to build on and was clearly willing to learn. There were too many areas he lacked experience in. As feedback for Jordy, I'd recommend he approaches his home projects as if they were fully agile enterprise grade team projects, incorporating CI and other technologies relevant to modern development team working. This should help him in the areas where he is currently lacking.
JAVA & OBJECT ORIENTED PRINCIPLES
Jordy identified the use of frameworks in removing boiler plate code. He has used GWT, Soap and Jsp. His experience here fits the 'old fashioned' category. He does understand the purpose of war files and what to do with them. He had a limited understanding of Annotations, describing them as compiler directives, which is only one minor aspect of what they are - his answer was indicative of limited modern framework use. He was able to describe interfaces well and mentioned polymorphism, an important aspect of their use. He was unfamiliar with design patterns at all and was unable to describe the purpose of a singleton. This indicates very limited object oriented understanding. He painted out that he may have used some design patterns without knowing it. This is possible.
JAVASCRIPT
He has no modern Js experience. He does have experience of a related technology GWT, that uses Javascript, so he has some knowledge of javascript.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jordy has a good knowledge of TDD and we discussed the principles at length. He mentioned Martin Fowler and Kent beck, two relevant figures in the subject area. In addition he has a good knowledge of testing generally, was able to describe the different types of testing but he has not used mocking frameworks. This is indicative of a good knowledge, there shouldn't be many problems here, but the lack of Mockito / jmock experience is possibly, indicative of an old fashioned understanding.
AGILE METHODOLOGY
Jordy has researched this subject at length and was on the cusp of introducing it in his position at his previous place of work. However, he was unclear on some of the agile ceremonies, although he is aware of the stand up. He described the concept of an MVP without using the term, so there is definitely some relevant understanding of the aims and philosophy of agile.
RESTFUL WEB SERVICES
He understands this at an academic high level, but has not done this himself. He seemed a little confused about how it all fits together. This could represent a problem.
SOURCE CONTROL MANAGEMENT
He has been a Perforce administrator for some years and is good with subversion, there should be no issues here. HE was able to answer all of the questions with relevant points and a clear understanding.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has some experience of this as a user but has never created a Jenkins job himself.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has some experience of Ant and some of Maven. When asked questions surrounding Maven, he seemed to understand the basics only but none of the detail. It is possible he does not have a lot of experience in this area. He has created ant scripts and understands how these work though. No big issues here.
CSS + HTML5
He has used a little HTML with GWT, but none directly and no HTML5.
Jordy had a lot of work to do to get up to speed. He seemed to have a significant gap in his experience during recent years and had a home project. He lacked modern experience working in teams but he had clearly been very senior and capable in the past. He had too many gaps in his experience to be able to recommend. He would fit in just fine as a junior developer, no doubt he would make very quick progress and be able to mentor the other staff in time. He has significant old style experience and academic knowledge to build on and was clearly willing to learn. There were too many areas he lacked experience in. As feedback for Jordy, I'd recommend he approaches his home projects as if they were fully agile enterprise grade team projects, incorporating CI and other technologies relevant to modern development team working. This should help him in the areas where he is currently lacking.
JAVA & OBJECT ORIENTED PRINCIPLES
Jordy identified the use of frameworks in removing boiler plate code. He has used GWT, Soap and Jsp. His experience here fits the 'old fashioned' category. He does understand the purpose of war files and what to do with them. He had a limited understanding of Annotations, describing them as compiler directives, which is only one minor aspect of what they are - his answer was indicative of limited modern framework use. He was able to describe interfaces well and mentioned polymorphism, an important aspect of their use. He was unfamiliar with design patterns at all and was unable to describe the purpose of a singleton. This indicates very limited object oriented understanding. He painted out that he may have used some design patterns without knowing it. This is possible.
JAVASCRIPT
He has no modern Js experience. He does have experience of a related technology GWT, that uses Javascript, so he has some knowledge of javascript.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jordy has a good knowledge of TDD and we discussed the principles at length. He mentioned Martin Fowler and Kent beck, two relevant figures in the subject area. In addition he has a good knowledge of testing generally, was able to describe the different types of testing but he has not used mocking frameworks. This is indicative of a good knowledge, there shouldn't be many problems here, but the lack of Mockito / jmock experience is possibly, indicative of an old fashioned understanding.
AGILE METHODOLOGY
Jordy has researched this subject at length and was on the cusp of introducing it in his position at his previous place of work. However, he was unclear on some of the agile ceremonies, although he is aware of the stand up. He described the concept of an MVP without using the term, so there is definitely some relevant understanding of the aims and philosophy of agile.
RESTFUL WEB SERVICES
He understands this at an academic high level, but has not done this himself. He seemed a little confused about how it all fits together. This could represent a problem.
SOURCE CONTROL MANAGEMENT
He has been a Perforce administrator for some years and is good with subversion, there should be no issues here. HE was able to answer all of the questions with relevant points and a clear understanding.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has some experience of this as a user but has never created a Jenkins job himself.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has some experience of Ant and some of Maven. When asked questions surrounding Maven, he seemed to understand the basics only but none of the detail. It is possible he does not have a lot of experience in this area. He has created ant scripts and understands how these work though. No big issues here.
CSS + HTML5
He has used a little HTML with GWT, but none directly and no HTML5.