Jaedon:
IN GENERAL
Jaedon was a decent junior developer. He had touched on all of the important and relevant areas but lacked depth in the majority of them. Overall I'd say he needs more experience to reach a the level of an intermediate developer that could hold his own in a team such as the one at DWP or HMRC. His Agile knowledge and experience was mixed, but in the other areas he generally didn't have enough understanding to be independently effective. In general he was able to maintain things that had been started for him but lacked the experience and knowledge to be able to create things for himself outside of the specifics of his home projects. In his own word, at this stage, he has "just learned enough to get by". Regrettably Jaedon would be a no from me.
JAVA & OBJECT ORIENTED PRINCIPLES
He seemed confused about what a .war file was and how it could be used. He knew it was a java artifact but said it could be used as a dependency in other projects like a jar can and seemed unsure where it would be deployed. he hasn't used any enterprise class frameworks, only a desktop framework that would have limited relevance to the role. he has used hibernate, but not from scratch. He has only maintained existing projects here. He has some experience of design patterns provided for him, but hasn't written any himself.
JAVASCRIPT
He has used Javascript for small jobs of limited complexity as part of his Jsp projects. This could be an okay basis for the course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
he hasn't done much. he is aware of it. He said it was test centric but was quite vague. he did know it was test first. He admitted a vague knowledge only.
AGILE METHODOLOGY
His current project focuses on this. He did however think there was an element of "future proofing" involved with agile, which is quite wrong. His answer to the Agile pre -screening question revealed this when he was asked to explain. he was not familiar with MVP but he was familiar with the fundamentals of Agile. He explained XP and scrum, he explained all of the agile ceremonies also. His sprints last 6 weeks, which is very unusual indeed. he has never been to a planning session. His knowledge and experience of Agile is therefore incomplete.
RESTFUL WEB SERVICES
He has done Rest extensively. He has also worked with Google Cloud. he understands the verbs, could name and explain them all.
SOURCE CONTROL MANAGEMENT
He said he has used GIT but he didn't know how it worked. He thought it was file-based like SVN and spoke about checking in and pushing files. We spoke extensively around the subject and he was asked to clarify many times. He was unaware that there is a local repository in git or anything about it's specifics. He has possibly learned just enough to get by or used a pre-set up version and been told what to type.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used Jenkins and has created a jenkins job with guidance from another staff member. He knows what it is for and has clearly worked in this type on environment, no problems here.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has not used this very much. He was quick to say he does not know this well. He was unaware of the standard directory structure in Maven or gradle. This level of knowledge a problem.
CSS + HTML5
He said he had done this including HTML5 but seemed confused about the advantages of HTML5 over the earlier HTML4.
Jaedon was a decent junior developer. He had touched on all of the important and relevant areas but lacked depth in the majority of them. Overall I'd say he needs more experience to reach a the level of an intermediate developer that could hold his own in a team such as the one at DWP or HMRC. His Agile knowledge and experience was mixed, but in the other areas he generally didn't have enough understanding to be independently effective. In general he was able to maintain things that had been started for him but lacked the experience and knowledge to be able to create things for himself outside of the specifics of his home projects. In his own word, at this stage, he has "just learned enough to get by". Regrettably Jaedon would be a no from me.
JAVA & OBJECT ORIENTED PRINCIPLES
He seemed confused about what a .war file was and how it could be used. He knew it was a java artifact but said it could be used as a dependency in other projects like a jar can and seemed unsure where it would be deployed. he hasn't used any enterprise class frameworks, only a desktop framework that would have limited relevance to the role. he has used hibernate, but not from scratch. He has only maintained existing projects here. He has some experience of design patterns provided for him, but hasn't written any himself.
JAVASCRIPT
He has used Javascript for small jobs of limited complexity as part of his Jsp projects. This could be an okay basis for the course.
BASIC TEST DRIVEN DEVELOPMENT (TDD)
he hasn't done much. he is aware of it. He said it was test centric but was quite vague. he did know it was test first. He admitted a vague knowledge only.
AGILE METHODOLOGY
His current project focuses on this. He did however think there was an element of "future proofing" involved with agile, which is quite wrong. His answer to the Agile pre -screening question revealed this when he was asked to explain. he was not familiar with MVP but he was familiar with the fundamentals of Agile. He explained XP and scrum, he explained all of the agile ceremonies also. His sprints last 6 weeks, which is very unusual indeed. he has never been to a planning session. His knowledge and experience of Agile is therefore incomplete.
RESTFUL WEB SERVICES
He has done Rest extensively. He has also worked with Google Cloud. he understands the verbs, could name and explain them all.
SOURCE CONTROL MANAGEMENT
He said he has used GIT but he didn't know how it worked. He thought it was file-based like SVN and spoke about checking in and pushing files. We spoke extensively around the subject and he was asked to clarify many times. He was unaware that there is a local repository in git or anything about it's specifics. He has possibly learned just enough to get by or used a pre-set up version and been told what to type.
CONTINUOUS INTEGRATION (JENKINS OR EQUIVALENT TOOL)
He has used Jenkins and has created a jenkins job with guidance from another staff member. He knows what it is for and has clearly worked in this type on environment, no problems here.
BUILD AUTOMATION (ANT, MAVEN, GRADLE)
He has not used this very much. He was quick to say he does not know this well. He was unaware of the standard directory structure in Maven or gradle. This level of knowledge a problem.
CSS + HTML5
He said he had done this including HTML5 but seemed confused about the advantages of HTML5 over the earlier HTML4.