Atomic Habits will drive you to that next level

The post uses Atomic Habits to show how small changes add up over time. It focuses on the four laws from the book and adapts them to coding practice, with examples based on cues, routine, repetition, and feedback.

Reading notes

#

• Making a habit list helps identify current behaviors before judging them as good or bad.
• A habit can be marked as positive, negative, or neutral depending on the goal.
• The post recommends setting specific plans with templates like “I will [behavior] at [time] in [location].”
• Another template is “After [current habit], I will [new habit].”
• Specificity is presented as important for turning a plan into progress.
• The cue starts the habit loop, followed by craving, response, and reward.
• The author says the cue can be the whole situation, not just one isolated detail.
• To drop a habit, the post suggests making it invisible by moving, deleting, or unplugging what triggers it.
• Habit stacking is presented as doing habits back to back so a new habit can be added more easily.
• The post says habits become easier when friction is low.
• Small daily repetitions are preferred over long, irregular sessions for building consistency.
• The author recommends starting with a small, maintainable amount of effort and increasing later.
• Making habits satisfying is linked to rewards, social groups, sharing work, and positive feedback from others.
• The post connects these ideas to programming, coding practice, and learning in public.