Just after finishing my last post, I received an email from Udacity advising that project 2 had been reviewed, but they were going to do a followup interview before marking it complete. Only one week from submission to completion - definitely better than the first project.
The result of the evaluation was...
I was so happy to see that on the evaluation, because I really did try to get the extra "make it yours" touch into the project.
The exit interview for the project was interesting. I was scheduled to be interviewed by Dimka, one of the Udacity coaches. She was nice to talk to, and supportive of the project and the program as a whole. I found the questions to be a bit more generic than I expected, but I assume that is a requirement on Udacity's part, as their students range from non-technical, first time developers to veterans in the field looking for certification of their skills.
There were quite a few questions on my opinions on the project. I think the interview is really two fold - the coach gets to check and make sure you know the material, and they request feedback on the project itself: what you liked, what you didn't like, what could be improved. I found that to be the hardest part of the interview, as I had prepared to review my code, and didn't really consider how to rate the course that teach the project, from my view as a student.
The whole interview took about 15 minutes, and shortly after, an email arrived with my code to enter in the Udacity site, to mark the project complete. So, two down, and a few more to go!
Link to project 2: resume on Github Pages
The result of the evaluation was...
I was so happy to see that on the evaluation, because I really did try to get the extra "make it yours" touch into the project.
The exit interview for the project was interesting. I was scheduled to be interviewed by Dimka, one of the Udacity coaches. She was nice to talk to, and supportive of the project and the program as a whole. I found the questions to be a bit more generic than I expected, but I assume that is a requirement on Udacity's part, as their students range from non-technical, first time developers to veterans in the field looking for certification of their skills.
There were quite a few questions on my opinions on the project. I think the interview is really two fold - the coach gets to check and make sure you know the material, and they request feedback on the project itself: what you liked, what you didn't like, what could be improved. I found that to be the hardest part of the interview, as I had prepared to review my code, and didn't really consider how to rate the course that teach the project, from my view as a student.
The whole interview took about 15 minutes, and shortly after, an email arrived with my code to enter in the Udacity site, to mark the project complete. So, two down, and a few more to go!
Link to project 2: resume on Github Pages
No comments:
Post a Comment