Skip to content

Instantly share code, notes, and snippets.

@npdarrington
Created September 14, 2020 05:20
Show Gist options
  • Save npdarrington/41b308ce7339d59b5290ffe11efe7b88 to your computer and use it in GitHub Desktop.
Save npdarrington/41b308ce7339d59b5290ffe11efe7b88 to your computer and use it in GitHub Desktop.

Mod 2 Week 4: Building Habits to Become a Software Developer, Part III

Prepare for Job Experience: AEIOU

  • Activities: what was engaging to the person/people you met with?
    • How knowledgeable they all were in their respective fields. You could tell that they are all very practiced and very professional.
    • Their thoughts and answers were well formulated and carefully thought over. They had the patience to listen to the question, ask for clarification if needed, and answer thoughtfully with the most value. Garvan was very open and asked for feedback on how to become better after his presentation. You could tell that he is a student of life and pursues progress in everything he does. It felt something that was very practiced and natural for him. It was very inspiring to me.
  • Environment: what did you notice about how they talked about the culture and environment of this company?
    • These particular companies had a very positive and interactive culture. Most companies are simply "show up and do your job". These companies had daily and weekly meetings that were built through communication and trust between each other.
    • These companies were very open to their own culture, norms and always seeking out new ways to improve it. Multiple times Garvan (in particular he was the only one I noticed), would compliment another company's spokesperson for something they said and would talk about what he learned from it.
  • Interactions: what did you notice about your interactions with this person/people?
    • Listed a lot of it above. Very open to answer questions and learning from us as well.
  • Objects: what did you learn about their approach to code and/or product development?
    • A lot of Garvan's code was formulated to how it would benefit the end user rather than being stuck in the weeds as a programmer. Having that end focus in mind made it really easy to understand why he is such a passionate programmer and pushed for some major companies like he did.
  • Users: what did you learn about their approach to their users?
    • Aside from the above mentioned bullet, Garvan never spoke too much about the users. There is naturally a large focus on it for him on his users, you could tell from how he structured his code, however we did not focus our questions in this direction.
  • What are your main takeaways from the shadow? How will you use this information to help you with your job search strategy?
    • Really dive in to learn more about companies, the benefits I can bring to the company and what benefits they will bring to me.
    • It is completely okay to focus on my benefits are a person applying for a company as well. If they are as invested in me and I am in their company, and do not push it to far, both of us will naturally benefit.
    • During my time at Turing, I will learn to become a git hub and git master. Most companies can get people with programming skills and capabilities, most companies dearly want someone who can control the flow of a project very well and articulate very well their approach and deliverable to a project.

Ideas below are adapted from Atomic Habits by James Clear

  1. Assess your habits from week 3: how did you spend your time this past week? What was effective in your habits? What could be more effective? What steps will you take to make that happen?
  • My habits this week suffered quite a bit. There has been so many projects, mid mods, final preparations, group project, final solo projects... During the group project, I have felt like there has been a lot that I have had to help and pick up with and this has made me focus a lot less on myseld during the week.
  • Almost no exercise or stretching at all this week. Basically all of my time was focused on planning out the project, keeping up with our progress to make sure that the group hasn't fallen too far behind while allowing them time to learn. It has been a very difficult balance and unfortuntely my habits suffered quite a bit from it;
  • Overall professional progress, my understanding of JS has increased tremendously! Learning so many technologies at the same time, while seeking out help from other upper mod members, the best donut meeting that I have had since almost quitting the donut experience last week due to a strange experience and meeting with the company representatives has really accelerated my learning and professional experience this week.
  1. Implement a reiforcement strategy: to make one of your habits more satisfying, what is a reward you can give yourself immediately after completing the habit? How will this reward encourage you to continue completing that habit?
  • I'm not entirely sure if I have to think of a reward for myself immediately after completing a habit. Generally, just performing the action is in itself enough for me. However, when I have decided that there are other things that take precedence over them, I will naturally move it to the back of my list.
  • This is definitely something that I will have to discover more with.
  1. “Don’t Break the Chain”: Use a habit tracker
  • What is a habit that you want to make sure to do every day? How could you visually cue yourself to complete it (i.e., moving a paper clip)? How can you visually track it each time you’ve completed it? Could you automate the tracking? How will you do that?

  • I really want to make sure that when I wake up in the morning and take some time to relax and wake up, is doing my Qigong routine. I think that this would help me stay focused and be more relaxed in the middle of the day.

  • One habit that I have been doing really well all of Mod 2 that I want to continue during these harder times is my mindset. During Mod 2, even though the Mod has been much harder than Mod 1, it has been the most relaxed that I have been in all of my years of programming. This is because rather than always being 'worried' about whether I will pick the material up or not, I have a process in place that helps me learn the content and I trust my work ethic. This has been the single reason why I have made such great progress and been much more relaxed, which in turn has helped me keep the mod under control.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment