Ideas here are adapted from Atomic Habits by James Clear
Habits of a Software Developer
What do you think are the traits of a good software developer? What are they like in the workplace? What would you as a co-worker think of this person?
- They are open to collaboration, and approach issues with a growth mindset. They are logical when solving a problem and think "what can I learn form this issue?" They are helpful and kind in the workplace, and as a coworker they are helpful and enjoyable to work with.
What are the habits that this person demonstrates to embody the identity of a software developer?
- This person is always learning, they take time out of their day to ensure that they are learning new information to grow in their professsional journey. They likely have good habits to get excercise to keep a healthy brain, and they set aside time to focus on side projects that they can also learn from.
Who do you want to be as a software developer? What kind of behaviors do you already have in place to be that person? What behaviors would you need to put into place? How will you do that?
- I want to be approachable and kind. I want people to be surprised at how easy it is to connect with me, and feel comfortable going to me for assistance in the future because they had such a great experience working with me. I have gotten similar feedback in my previous role about approachability, so I am hoping to keep growing that behavior, and be helpful to my team. I will do that by getting feedback from people who work with me and finding ways to constantly imrpove.
Working on the 1st Law of Behavior Change: Make it Obvious
Bring self-awareness to your current habits by making a Habits Scorecard. Make a list of your daily habits (examples: wake up, turn off alarm, check phone, etc.) as a way to bring awareness to what you do. Then, decide how effective that habit is for you and your goal of becoming a software developer. Put a + next to habits that are effective; put a - next to habits that are not effective; put a = next to habits that are neutral.
- Wake Up around 6am.
- Get up and take my dog for a walk.
- Come home and prepare for my day (brush teeth, floss etc).
- Get on my computer, and try to find something productive that I can do before class.
Pick 1 new habit you’d like to build and create an implementation intention following this template: “I will [BEHAVIOR] at [TIME] in [LOCATION].” Then, stack the habit onto something you already do: “After [CURRENT HABIT], I will [NEW HABIT].” (Hint: make this highly specific and immediately actionable)
- I will complete Ruby exercises at 7am in my living room.
- "After taking my dog out in the morning and getting ready, I will work on Ruby exercises.
Design your environment for success: what changes could you make in your space to better implement your habit? How could you remove any triggers for bad habits? How will you implement these changes?
- I could prepare in the evening for what practice I want to do the next morning, and hold myself to it.
Respond after a few days of this implementation: What are your results? How do you feel about this method? How will you move forward with this habit?
Additional Optional Reading: The Five Triggers That Make New Habits Stick
Great reflections on the habits that you want to develop in yourself to become your idea of a great developer! I love the thought of people being surprised by how easy it is to work with you. I appreciate the thought you put into developing a new habit that will help you become this developer. Can't wait to see your evaluation of how this goes over the next few days.