- Improve CSS Skills
- Improve JS fundamentals/Algorithmic skills
- Learn a little of either Ruby || Python || Java || Golang
- Be at Turing every weekday until I move to offer Mentoring/project help
In a practice interview session I made the mistake of saying something I wasn't sure was correct. As soon as I said it I knew it was wrong and it was extremely embarrassing. I need to be more confident in saying "I don't know, but I think X". In practicing I seemed to excel at looking at problems from the users perspective. I also noticed a lack of understanding in my CSS knowledge that I must sharpen up on pronto. I think I'm ok at whiteboard questions, but I have some difficulty with verbal knowledge questions so I need to practice with others or work with the lower mods. If I want to succeed I need to sharpen those areas.
# Template: Module 4 Action Plan | |
*This is your deliverable from the [Job Search Strategies I session](https://github.com/turingschool/career-development-curriculum/blob/master/module_three/job_search_strategies_i.md)* | |
## Module 4 Goals | |
*List your longterm goal(s) of what you want to accomplish by the end of module 4* | |
Interview twice. Have opportunities and a game plan on where I'm going to live/work. | |
### Strategy To Achieve Goals: | |
In this section, break down your longterm goal into smaller goals that you want to work on each week and/or day |
1. Favorite People to Work With | |
Energetic, easy to communicate with, responsive, constantly seeking improvement. | |
2. My Values and Goals | |
Make interesting technologies that solve difficult personal/business/or societal problems. | |
3. Prefered Places to Live: |
I'm working hard, communicating well, and persevering through difficult situations.
I stay in almost constant contact which enables us to quickly troubleshoot things if one of us is stuck.
I sat and thought of what would be most important to him going forward. I also tried to ensure I was receptive to feedback.
It went ok. He pointed an interesting note about my behavior that never thought I had, but is something I dislike in my father.
I found Agile interesting because throughout my time at Turing thus far I've been using a modified version of Agile. And it works. In essense my project partners and I have chosen to select important tasks together at the start of every day. We work together on each issue, usually testing, then creating, then improving the design. We stay late, then before we part ways we would outline tasks we wanted to try that night using Github issues. Every morning we regroup, prioritize, get feedback on things we aren't certain about, and repeat the cycle.
Communication. Deciding which parts of the project to accomplish next. Getting outside feedback from more advanced students/instructors. Getting user feedback. My last project had a cool feature that took 3-5 seconds to load once clicked. My friends in the Backend pointed out that they had no idea if anything was happening and would click multiple times. To fix this we added a loading animation and no one has since clicked the button more tha
We met at Turing later that week and he gave me advice on the Game-Time project. I've since contacted him for advice on React (he's a React developer). We're meeting up for drinks in the next couple of days.
I feel like he's a great person to bounce idea's off of. And will lead to a better understanding of technologies/CS concepts.
[Challenge 2] (http://codepen.io/DBULL7/pen/apEYdW)
[Challenge 3] (http://codepen.io/DBULL7/pen/zNRZmm)