Review your habit tracker: how did you monitor your habit(s)? What does this tell you about your overall progress becoming the person you want to be? In general, how satisfied are you with how you spent your time this module? What could be improved next module?
- My habit tracker has been slighly less effective this past week due to the final assessment and final solo project focus. I understand how the habit can help me in those aspects, but I had to prioritize my tasks.
- I was able to get coding in each day so I achieved that habit.
- I think I am making progress in understanding the JS language better, but I need more practice writing code that can be implemented in a project.
- This is a step in the right direction for me because it will eventually help me become the developer I want to be. In order to do this, I need to restructure my habits to include organization and planning because that is what hurts me the most when it comes to projects.
Mind Maps:
i. Engagement. What did you reflect on last week in regards to when you’re engaged in your work at Turing? Pull out an idea that resonates with you most (e.g., “Talking through a problem with a partner,” “The moment when I solve a problem that I previously didn’t know how to do,” “Setting up a successful project management process for my team”) and break that idea down into parts and make a list. (what are all the steps that go into that moment? When do you get to use your strengths? What is fun about this?).
- I realized that I'm most engaged during group/project work, doing the logical JS code and solving a problem that has troubled us.
- In order to achieve this, I need to discuss the problem with my group, analyze the outcome and what we already know, and brainstorm how to achieve that outcome
- I get to use my strengths when I am able to talk about the problem with someone and bounce ideas off them while trying all the different solutions.
- I enjoy seeing what works and what doesn't work because I see it as an opportunity to learn for future projects. It can be reference in the future as well.
- This is enjoyable because I get a sense of satisfaction and surge of adrenaline when I solve a complicated problem. The sense of accomplishment is something I chase when it comes to coding.
ii. Energy. What did you reflect on last week in regards to when you feel most energized in your work at Turing? Pull out an idea that resonates with you most and break that idea down into parts and make a list (what are all the steps that go into that moment? When do you get to use your strengths? What is fun about this?).
- I feel most energized on my work when I know there is structure provided and when the task is familiar but still foreign.
- When I know the expectations and how to reach them, I feel like the task is achievable and that gives me the energy/desire to work on it.
- I get to use my strengths when I dont have to worry about the exact steps to reach the goal. If I already know the steps, I can cross them off as I go and that checklist gives me the energy to keep moving forward. When the structure is more abstract, is when I struggle.
- It's fun to know work is broken down into manageable sprints because it gives me a sense of accomplishment and I can plan on how to do the next task. I enjoy structure when it comes to the unknown.
iii. Flow. When have you had an experience recently in which you were in a state of flow? You can also think about this as “joy” or “play.” Pull out an idea that resonates with you most and break that idea down into parts and make a list (what are all the steps that go into that moment? When do you get to use your strengths? What is fun about this?).
- I get a sense of flow when I work on JSFun or IronFE.
- They bring me joy because I like the sense of instant gratification or error. If I can solve a problem and see the correct result I get motivated to tackle the next one. If I get an error, then I become motivated to see why and see how I can be successful.
- I often lose track of time when I'm working on these because I'm so zeroed in on them.
Prototype your mind maps: what do these mind maps tell you about what’s important to you as a software developer? What questions do they bring up about what you still want to learn about this career?
- I find that structure/organization and expectations are important for me as a software developer. I come from a profession where the expectations were always laid out, even if they were subjective. That helped me establish my goals as a teacher and I think that can be transferable to software development.
- I would still like to see more about the day to day life of a developer because I know it varies depending on the company they work for.
- That being said, I guess I need to continue to do more research on the type of company I would like to work for in the future because that will determine my level of satisfaction.
- I don't want to work for a company that is unorganized and unwilling to accept input from their employees.
Prototype your outreach: (Be prepared to share this in your small group discussion)
Who comes to mind as a person you can reach out to? Why that person? What questions would you ask them? Come up with 2-3 people here to serve as prototypes
- I would like to reach out to my friend who has been in the business for 5+ years.
- I chose this person because I know he will give me the facts without sugar coating it. He will provide me with the positives and negatives in an honest way and that can help direct me towards companies I would possibly enjoy working for.
- I would also like to reach out to someone from a company that I am interested in. Possibly someone who works on applications/programs in education because I come from that background and I see the future becoming more and more technological.
- I think this person can help me identify if it is actually a area of focus that I would be interested in.
- If they can explain their role, how they impact education, and their work environment, then I can get a clearer picture.
How would this outreach help you further your job search strategy?
- It would help point me in the right direction of where I would like to work.
- the more I know about the different applications of software development, then I can make an assessment of where and how I can use my skills.
Outreach & Networking Plan: Based on your reflections above, create a concrete plan for your outreach:
Who is the right person for you to reach out to?
- Besides my friend, I need to find and reachout to an employee at an education centered company.
How will you find them? How do you know they’re the right person?
- Education my main area of focus at the moment, but if I find that it isn't the right fit for me, then I can assess that now instead of later when it might be too late.
- I'm hoping who I reach out to can shine a light on the industry with its pros and cons.
How will you reach out?
- I intend on reaching out via LinkedIn or possibly email if I do extra research on companies.
What questions do you need to ask them?
- How did you get started in this field?
- Do you have any recommendations as a new developer?
- What are the pros and cons to the business you're in
- What do you do on an average day?
- Overall, do you enjoy the work you do/its impact it has?
How will you use this information to further your solution?
- The answers to those questions will help me evaluate the field I would like to go in.
How will you follow up?
- After discussing with the person, I intend on applying or following up with recruitment at the company
Execute your plan:
Reach out to your contact THIS WEEK. If possible, reach out to more than one person OR find a meetup to attend also. What happened? What other next steps should you take? If this is a person connected to a company you’re interested in, be sure to add it to your Huntr card.