Create Atomic Habits to Become a Better Developer #buildstuffconf

  • Habit Formation:
    • Describes the four stages of habit formation: cue, craving, response, reward.
    • Outlines four rules for building good habits, corresponding to each stage.
    • Uses the example of checking phone notifications as a habit to explain the rules.
  • Implementation of Habits:
    • Shares personal habits focused on becoming a better developer.
    • Emphasizes setting specific implementation intentions, stacking habits, and bundling new habits with desired activities.
    • Highlights the importance of reducing friction, making actions easy, and connecting actions immediately after completion.
    • Advocates for habit tracking as a gamification technique for maintaining streaks.
    • Two minute rule – always stay below the point where it feels like a work. Do at least one #coursera
    • Reduce friction – minimize actions you need to take ( have a bookmarked page, setted up enviroment)

  • Breaking Bad Habits:
    • Discusses strategies for making bad habits unattractive, difficult, and unsatisfying.
    • Stresses the value of an accountability partner and even publishing a habit contract to the world.
    • A commitment device A choice you make in the present tht controls your actions in the future
  • Results and Impact:
    • Reports personal success using these habits, including a job promotion and improved focus.
    • Encourages the audience to start working on tiny habits for personal development.
  • Q&A:
    • Addresses questions about the duration of using these techniques, adapting habits to circumstances, and the applicability of habits to developers at different career stages.
  • Key Takeaways:
    • Small, consistent changes lead to significant results.
    • Lifelong learning is crucial for personal and professional development.
    • Personal examples demonstrate the effectiveness of atomic habits.

#buildstuff2022

Official slides: https://www.slideshare.net/NatanSilnitsky/create-atomic-habits-to-become-a-better-developer

@NSilnitsky

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *