Jan:
IN GENERAL
Jan took a long time to answer any of the questions. There were many pauses and a lot of thinking time. He does not seem 100% confident or sharp in any of the areas, but in most of the fundamental areas he does seem to remember the answers eventually. He seemed unwilling to say when he didn't know somehting, prefering to take the conversation off on a tangent for a while. Communication was difficult fuzzy with him. He was none-comittal and exceptionally time consuming. In the end I'd give him 50 50 due to the level of inconsistency in his answers (see the Source Control Management section), with hind sight, looing back at he notes, that may have been generous .
JAVA & OBJECT ORIENTED PRINCIPLES
Hi knowledge of OO concepts is generally good. He seems compatent in this area. He undersands wheat a .war file is and how it fits in also the purpose of a framework. In general he did well here although as in all of the sections there was an unusually high amount of thinking time.
JAVASCRIPT
He is familiar with Javascript and has used javascript frameworks including JQuery and the lesser known, dojo. This is an excellent basis for the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
We spent some time on TDD, Jan needed a lot of thinking time, he got there in the end. he may not be familiar with all of the terminology but he seems to understand the basics of this and seemingly has used it in the past.
AGILE METHODOLOGY
He didn't know agile. He mentioned cost cutting and talked about "integration", but they are not related concepts. He felt documentation ws very important in agile. This is incorrect. Also he went off on other tangents here. He was however aware of what happens at a stand up and seemingly has worked in an agile environemnt. He would do well to refamiliarise himself with true agile concepts, although it is probable he could work well in an agile environment.
RESTFUL WEB SERVICES
Jan said he had "maybe" heard of verbs, a central concept of rest. When questioned he was unable to answer correctly. I think he would struggle with Restful web services.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jan had used continuous integration, in particular , Jenkins and was able to describe how that fits in, but was confused about some of the guiding concepts. He has never created a CI job but that should not hinder him in his role.
SOURCE CONTROL MANAGEMENT
He was no too familiar at first with this and went off on some tangents. He adminted that he had never heard of the concept of a Branch, which is a central concept to source control managment. After a few minutes he remembered what branches were and gave an excellent explanation.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has not used a build tool recently, he just uses his IDE, he would struggle with this aspect.
CSS + HTML5
Jan admitted he was not too familiar with this.
Jan took a long time to answer any of the questions. There were many pauses and a lot of thinking time. He does not seem 100% confident or sharp in any of the areas, but in most of the fundamental areas he does seem to remember the answers eventually. He seemed unwilling to say when he didn't know somehting, prefering to take the conversation off on a tangent for a while. Communication was difficult fuzzy with him. He was none-comittal and exceptionally time consuming. In the end I'd give him 50 50 due to the level of inconsistency in his answers (see the Source Control Management section), with hind sight, looing back at he notes, that may have been generous .
JAVA & OBJECT ORIENTED PRINCIPLES
Hi knowledge of OO concepts is generally good. He seems compatent in this area. He undersands wheat a .war file is and how it fits in also the purpose of a framework. In general he did well here although as in all of the sections there was an unusually high amount of thinking time.
JAVASCRIPT
He is familiar with Javascript and has used javascript frameworks including JQuery and the lesser known, dojo. This is an excellent basis for the MEAN course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
We spent some time on TDD, Jan needed a lot of thinking time, he got there in the end. he may not be familiar with all of the terminology but he seems to understand the basics of this and seemingly has used it in the past.
AGILE METHODOLOGY
He didn't know agile. He mentioned cost cutting and talked about "integration", but they are not related concepts. He felt documentation ws very important in agile. This is incorrect. Also he went off on other tangents here. He was however aware of what happens at a stand up and seemingly has worked in an agile environemnt. He would do well to refamiliarise himself with true agile concepts, although it is probable he could work well in an agile environment.
RESTFUL WEB SERVICES
Jan said he had "maybe" heard of verbs, a central concept of rest. When questioned he was unable to answer correctly. I think he would struggle with Restful web services.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jan had used continuous integration, in particular , Jenkins and was able to describe how that fits in, but was confused about some of the guiding concepts. He has never created a CI job but that should not hinder him in his role.
SOURCE CONTROL MANAGEMENT
He was no too familiar at first with this and went off on some tangents. He adminted that he had never heard of the concept of a Branch, which is a central concept to source control managment. After a few minutes he remembered what branches were and gave an excellent explanation.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has not used a build tool recently, he just uses his IDE, he would struggle with this aspect.
CSS + HTML5
Jan admitted he was not too familiar with this.