Skip to content

Instantly share code, notes, and snippets.

@alexthompson207
Last active February 5, 2021 01:11
Show Gist options
  • Save alexthompson207/b618da6df3376d2ff92e7f210b1ce1bf to your computer and use it in GitHub Desktop.
Save alexthompson207/b618da6df3376d2ff92e7f210b1ce1bf to your computer and use it in GitHub Desktop.

Week 1 Journal Reflections

Mod 2 Week 1: Building Habits to Become a Software Developer, Part II

Ideas here are adapted from Atomic Habits by James Clear

  1. Reflect on your habits from last module. What behaviors and activities were helpful for you? What activities and behaviors could be more effective for you? What processes would you like to try differently this module to become more effective at your work and as a software developer?

The times I set a POM timer and took breaks proved to be super helpful for me in the learning process. Also limiting my procrastination when starting projects, homeworks, and journaling was super helpful in being successful in mod 1. I could do a better job at scheduling out my time for when I'm working, and what I'm working on. I often create a mental note of what I need to work on but don't actually physically write it in a schedule. I would like to start keeping a better schedule that I keep up to date on the times I'm working on what, and the times I couldn't be working. Furthermore I would like to be more diligent about setting POM timers, and taking breaks when the timer is up.

  1. Setting intentions for this module: who do I want to be this module? What specific habits would help me get there? How are those habits tied to the identity of a software developer?

I would to like to develop a better system for getting unstuck when I can't seem to progress on a project. I need to set a timer when I get stuck and then reachout to my cohort/rock/mentor and explain to them what the problem is, what I have tried, and any relevant screen shots/code. I need to be better about reaching out after 20-40 minutes of being stuck, rather than getting frustrated and continuing to google things I can't find the answer to. This ties in with how a successful software developer would reachout to peers when they are stuck, rather than wasting time and money trying to get unstuck on their own. Using peers knowledge is a great skill to have, and having the work culture to be able to reach out to peers is an essential skill.

  1. Incorporate temptation bundling to create a new habit by using this template:
  • After my first cup of morning coffee, I will pre-teach lesson/do codewar problems/JS Fun.
  • After pre-teach lesson/do codewar problems/JS Fun, I will listen to a podcast and drink coffee and eat breakfast.
  1. How to enjoy “hard” habits: Reframe your habits to consider their benefits rather than their drawbacks; name 3 habits that you have to do and explain the benefits of them. How do they further your goals longterm? How will they add to your processes as a successful developer? At the end of the day, how do they add to your life?
  • Schedule out blocks of time to work, and what to work on. The benefits of this is to make sure I have time to work on everything I need to work on - projects, practice problems, pre-teach lessons, etc. and that no work is getting pushed to the bottom, so that I can become a better software developer and my learning can grow. This will add to my life, because if something is one my schedule, I will have more self accountability.
  • Get exercise in some form everyday. This helps me reduce stress, gets my mind off everything I need to do for the day/week, and allows me to mentally refresh. This will help me become a better sofeware developer by being able to stay focused on my work, and be more sharp mentally. This will add to my life in that I will have a better mindset, and hopefully have a less stressed filled life.
  • Getting work done early in the morning. The benefits of getting work done early in the morning is that brain is functioning at its best in the morning, and I am able to think more clearly. This will help me as a software developer in that I will be writing my best code when my brain is working the best in the morning. This will allow me to write better code and avoid writing sloppy code -- such as coding late at night. This will add to my life in that I will get my work done in the mornings, and late at night I don't need to focus as much on work, and can enjoy my personal life more.
  1. Environment design (optional 5-min. additional reading: Motivation is Overvalued. Environment Often Matters More): how does your environment set-up currently help you with your habits? How could it be improved to make it easier for you to follow through on your habits?

My environment set-up currently helps me in some of my habits in that, there is no commute for me to take at the moment, my set-up is about one foot away from my bed. Furthermore, my living situation is great in that I have minimal distractions during the day. However, I live with three other people, so sometimes it's noisy and I can get easily distracted. I think I would benefit from living in a house/apartment where I had a separate room to devote to working and wasn't my bedroom. Furthermore I would also benefit from living alone, so that I am not distracted by the people I live with.

  1. “When you start a new habit, it should take less than two minutes to do.” Read this 4-min article on how to stop procrastinating. Apply the 2-minute rule to reframe 2-3 of your habits by scaling them down into the 2-minute version. How does this reframing help you think about shaping your new identity as a software developer?

I will start a POM timer when I start working. I will schedule one thing a day. I will write the vocab down in the morning before the lesson begins.

This reframing helps me get a clearer picture of the identity I want to build as a software developer by turning my habits into easier steps, that will eventually become reinforced. Once I do these habits in there easy reframed versions, I am much more likely to continue doing these habits and it will reinforce the identity I want to build.

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