“Atomic Habits” and Learning to Code: Identity and Beliefs.
After the positive feedback on last weeks post here is another productivity post based on knowledge obtained from "Atomic Habits". Please feel free to reach out with any ideas, questions or banter!
Last week I wrote a post about how programmers can optimise productivty by utilising some of the tips and techniques from James Clear’s “Atomic Habits”. It turned out to be my most successful newsletter to date even though I barely scratched the surface of what the book had to offer.
“Atomic Habits” provides practical insight and strategies for building effective habits and breaking unproductive ones. It is emphasised that small, incremental changes, or “atomic habits,” can lead to significant improvements over time.
There is a more in depth analysis the book mentioned in my previous post so it may be worth checking that out before proceeding, although it’s certainly not imperative for getting something out of this post.
Last week the concepts covered were ‘The Plateau of Latent Potential’, ‘The Two Minute Rule’ and ‘The “Goldilocks” Rule’, this week I will unpack ideas on “Identity and Beliefs” from the book and discuss how they can be utilised when learning to code.
Identity and Beliefs
In “Atomic Habits,” James Clear delves into the influence of identity and beliefs on habits. He illustrates this with an example of a person trying to quit smoking. When offered a cigarette, individuals who responded with “I don’t smoke” as opposed to “I’m trying to quit”, transform their belief system and have greater success of remaining smoke free.
This change in self-perception makes quitting feel congruent with their identity, making it more likely to stick. This concept also applies to productivity. If you identify as someone who finishes tasks promptly, you’re more inclined to act in alignment with that identity. By recognizing the deep link between identity and habits, you can consciously shape your beliefs to reinforce positive behaviors, enhancing productivity and success.
Impostor Syndrome
“Impostor syndrome” is a term often associated with learning to become a developer. Many programmers develop feelings of inadequacy or self-doubt when they encounter a problem and don’t know how to solve it. They doubt their abilities and feel like a fraud. These factors contribute to impostor syndrome and many highly skilled developers are unable to shake off this feeling.
The ideas on identity and belief outlined in “Atomic Habits” suggest this is a hindrance to productivity and progress when learning to code. This proposes that the ability to clearly identify as a capable developer despite setbacks and difficulties is a positive habit for increased knowledge and success in becoming a bettter developer.
Identity Shift & Belief Transformation
Start by identifying yourself as a programmer or coder. Embrace this identity even if you’re just starting out. The more you view yourself as a coder, the more your actions will align with that identity.
Cultivate the belief that you can improve your coding skills over time through consistent practice. Understand that challenges and mistakes are opportunities for growth, not signs of failure. This belief will drive you to persistently learn and refine your coding abilities.
Consistency
Make coding a regular part of your routine. Set aside dedicated time each day or week to code. Over time, this consistent practice reinforces your coder identity and improves your skills.
“Atomic Habits” outlines that by consistently engaging in habits that align with the identity we wish to adopt, we gradually transform ourselves into that desired identity. In other words, our habits aren’t just actions; they are a reflection of who we are aiming to become.
The length of time required in maintaining habits is not clearly defined, however, It would be hard to argue that someone who codes daily for a significant amount of time cannot be identified as a coder (whether they are payed is another matter!).
Learning Mindset / Goal Setting
Approach coding with a growth mindset. Embrace challenges as opportunities to learn rather than reasons to give up. This mindset shift aligns with your coder identity and encourages persistent learning.
Before learning to code, I didn’t appreciate the richness that a learning mindset brings to life. I now identify as a lifelong learner and am committed to developing knowledge in multiple fields. Over time, this committment to learning taps into a sense of fulfillment and a new identity optimised for achievement.
Set specific coding goals for yourself. These goals should align with your coder identity and contribute to your skill development. Achieving these goals reinforces your belief in your capabilities.
Community
Surround yourself with fellow coders, whether it’s through online forums, coding groups, or local meetups. Engaging with a community of like-minded individuals reinforces your identity and provides support during challenging times.
Attending meetups and sharing my struggles with fellow developers was the best thing I ever did in relation to boosting my progress in coding. It allowed me to create contacts, gain real world advice and most importantly feel part of the programming community.
The software development community is particularly rich with an infrastructure that promotes learning (think of all the free content online!), the sharing of ideas, and collaboration. Most other industries do not offer such open privileges so get out there and make the most of it!
Remember that developing coding skills is a journey, and your identity and beliefs play a significant role in shaping your progress. By aligning your mindset with the principles outlined in “Atomic Habits,” you can cultivate effective habits, enhance your productivity, and become a more proficient and confident coder.