Jago:
IN GENERAL
Jago was very experienced but was a little resistant to feedback. He was quite critical of the questions he'd been asked and I felt his level of knowledge was not as up to date as he felt it was. He as unaware of the role of Javascript in modern software development and was surprised when I pointed out it's recent advancements. Once I explained the reasoning behind the correct answers he generally accepted and agreed with it. I would focus on the area of manageability in the next stage. Despite that he has a full set of skills and would be an asset to any team. He was clearly an experienced and capable developer. So he was a yes.
JAVA & OBJECT ORIENTED PRINCIPLES
Jago had a good knowledge of object oriented principles, he has used spring extensively even effectively combining it with JEE. He spoke about micro-services and when questioned about the finer points he was able to have a cometant professional deiscussion. He is clearly competant in this area.
JAVASCRIPT
Jago has done a project using javascript some years ago, well before it developed into what it is today. he was surprised it can be used on the server side. This shouldn't present a problem for the training course. I'd say his knowledge of javascript is enough for a foundation for the course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jago understands test first methodology and TDD, he was questioned about it from all sorts of angles and it was clear that he genuinely did know what he was talking about and has used TDD extensively. In addition he has worked in environemnts that utilise all major forms of testing that he would need to understand.
AGILE METHODOLOGY
He is experienced with agile methodology, he was able to describe the ceremonies and the roles in a scrum team. We spoke about agile roles, epics, stories and it was clear his opinions on it were legitimate and defensible.
RESTFUL WEB SERVICES
He has coded up restful end points using spring boot, he understands verbs, he had only used xml, not the more modern json with this but that isn't a problem. It wasn't possible to catch him out here. He clearly knows this.
SOURCE CONTROL MANAGEMENT
Jago has used SVN and GIT and is confident talking about code streams and how they fit together. There shouldn't be an issue here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jago has used Jenkins extensively as part of his former role as an architecht. He understands the concepts in detail and has created jenkins jobs himself.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He uses gradle often and is familiar with maven. When questioned on the maven concepts he understood the concept of the multiple stage commit and had clearly used it.
CSS + HTML5
He has used early versions some time ago.
Jago was very experienced but was a little resistant to feedback. He was quite critical of the questions he'd been asked and I felt his level of knowledge was not as up to date as he felt it was. He as unaware of the role of Javascript in modern software development and was surprised when I pointed out it's recent advancements. Once I explained the reasoning behind the correct answers he generally accepted and agreed with it. I would focus on the area of manageability in the next stage. Despite that he has a full set of skills and would be an asset to any team. He was clearly an experienced and capable developer. So he was a yes.
JAVA & OBJECT ORIENTED PRINCIPLES
Jago had a good knowledge of object oriented principles, he has used spring extensively even effectively combining it with JEE. He spoke about micro-services and when questioned about the finer points he was able to have a cometant professional deiscussion. He is clearly competant in this area.
JAVASCRIPT
Jago has done a project using javascript some years ago, well before it developed into what it is today. he was surprised it can be used on the server side. This shouldn't present a problem for the training course. I'd say his knowledge of javascript is enough for a foundation for the course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
Jago understands test first methodology and TDD, he was questioned about it from all sorts of angles and it was clear that he genuinely did know what he was talking about and has used TDD extensively. In addition he has worked in environemnts that utilise all major forms of testing that he would need to understand.
AGILE METHODOLOGY
He is experienced with agile methodology, he was able to describe the ceremonies and the roles in a scrum team. We spoke about agile roles, epics, stories and it was clear his opinions on it were legitimate and defensible.
RESTFUL WEB SERVICES
He has coded up restful end points using spring boot, he understands verbs, he had only used xml, not the more modern json with this but that isn't a problem. It wasn't possible to catch him out here. He clearly knows this.
SOURCE CONTROL MANAGEMENT
Jago has used SVN and GIT and is confident talking about code streams and how they fit together. There shouldn't be an issue here.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
Jago has used Jenkins extensively as part of his former role as an architecht. He understands the concepts in detail and has created jenkins jobs himself.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He uses gradle often and is familiar with maven. When questioned on the maven concepts he understood the concept of the multiple stage commit and had clearly used it.
CSS + HTML5
He has used early versions some time ago.