Link to reflection on agile practices/project management used in projects (What project management strategies did you use in your projects this module? What went well? What would you do differently next time?):
Date of feedback conversation:
- September 5, 2017
How did you prepare for the conversation?
- I reflected on our project and workflow. I took note of successes and challenges and how we worked together.
How did the conversation go for you? What was easy about the conversation? What was more difficult?
- It felt easy to share feedback with Nick because we have maintained a great working relationship throughout the two projects we've been paired on. We both reflected on getting caught up on tasks and not taking enough breaks - leading to burnout. We both pushed each other to improve in that area!
What principles of feedback did you use in the conversation?
Date of feedback conversation:
- September 5, 2017
How did you prepare for the conversation?
- I reflected on our project and workflow. I took note of successes and challenges and how we worked together.
How did the conversation go for you? What was easy about the conversation? What was more difficult?
- It felt easy to share feedback with Nick because we have maintained a great working relationship throughout the two projects we've been paired on. We both reflected on getting caught up on tasks and not taking enough breaks - leading to burnout. We both pushed each other to improve in that area!
What principles of feedback did you use in the conversation?
I really enjoyed learning about agile practices this mod, and working with my partners to use agile practices. During our session, Jeff said, "build half a thing, not a half-assed thing" and that really stuck with me. I think I am drawn to this becuase I see the value in early and frequent user testing. One thing I would like to do differently/improve on as I move forward is TDD.
I appreciated the purpose of the session and thought it was well planned.
When I shared some things about my experience, I was told by the males in my smalll group...
- No, your partner didn't actually roll his eyes and complain to his friend when he learned you were paired
- There's no way someone in our cohort would speak about a woman that way
- There's no way people form our class would interrupt you
When they finally believed me that these things were indeed part of my experience, I was told...
- Well you just shouldn't get your feelings hurt
You are so close! You've spent the last 7 months working towards this -- graduation and finding your new dream job! This plan is meant to help you streamline your goals and get on the path to employment as a software developer during the first 30 days after graduation. Please fill out the plan by copying this template into a gist to submit in your portfolio.
As you fill out this plan, consider how your first job search will set the tone for your career trajectory in the software industry. After all, your first developer job should align with those goals as well so that you're on track for a longterm successful career.
Note: If you have already secured a job prior to graduation, skip to the second part of the plan below.
Design a 40-hour "work week" that provides time for:
Fill out this part only if you have already secured a job prior to graduation.
As a member of the Turing community, your support in the job search makes a big difference for your peers as they pursue their first position. Complete the following action steps to
Action Step #1:
- Francy
- Mimi
Each student will be asked a variety of technical questions during the Mock Interview in a one-on-one setting with an instructor who will be acting as the interviewer.
Topics may include the following:
- Testing
- Object Oriented Programming
- Ruby and JavaScript Fundamentals
- Debugging Techniques