habits

overview

habits are automatic behaviors that compound over time. building good habits and breaking bad ones is key to long-term success.

core principles

start small

• make new habits so easy you can't fail
• focus on consistency over intensity
• 2-minute rule: scale down to something doable in 2 minutes
• example: "read every day" → "read one page every day"

stack habits

• attach new habits to existing routines
• use current habits as triggers for new ones
• example: "after i pour my coffee, i will write in my journal"

environment design

• make good habits obvious and easy
• make bad habits invisible and hard
• optimize your environment for success
• remove friction from desired behaviors

identity-based habits

• focus on who you want to become, not what you want to achieve
• every action is a vote for the type of person you want to be
• "i am someone who writes" vs "i want to write a book"

habit formation cycle

cue (trigger)

• environmental trigger that initiates the behavior
• time, location, preceding event, emotional state, other people

routine (behavior)

• the actual habit or behavior itself
• should be simple and specific initially

reward (benefit)

• positive outcome that reinforces the behavior
• can be intrinsic (satisfaction) or extrinsic (external reward)

building good habits

daily practices

• morning routine: consistent start to the day
• evening routine: reflection and preparation
• regular exercise: physical and mental health
• continuous learning: reading, courses, experiments

productivity habits

• time blocking: dedicated time for focused work
• single-tasking: focus on one thing at a time
• regular breaks: prevent burnout and maintain focus
• weekly reviews: assess progress and adjust plans

technical habits

• daily code review: reading and understanding code
• documentation: writing down solutions and learnings
• version control: regular commits with clear messages
• backup routines: protecting important work

breaking bad habits

identification

• recognize triggers and patterns
• understand the reward the habit provides
• track occurrences to build awareness

replacement

• substitute bad habits with good ones
• address the underlying need the habit fulfills
• change the environment to reduce triggers

gradual reduction

• slowly decrease frequency rather than stopping abruptly
• use implementation intentions: "if x, then y"
• build accountability systems

tracking and measurement

habit tracking

• simple checkboxes or apps
• focus on consistency streaks
• celebrate small wins
• don't break the chain for more than one day

progress indicators

• leading indicators: process metrics
• lagging indicators: outcome metrics
• regular review and adjustment
• qualitative assessment alongside quantitative

habit stacking for developers

morning routine

• check system status and logs
• review daily tasks and priorities
• quick standup with team or self

development cycle

• write tests before code
• commit frequently with clear messages
• review code before pushing
• document decisions and learnings

learning routine

• read technical articles daily
• experiment with new tools regularly
• share knowledge through writing or teaching
• reflect on what worked and what didn't

common pitfalls

trying to change too much at once

• focus on one habit at a time
• wait until it's automatic before adding another
• be patient with the process

perfectionism

• progress over perfection
• missing one day doesn't break the habit
• get back on track immediately

lack of specificity

• vague goals lead to inconsistent execution
• be specific about when, where, and how
• use implementation intentions

related topics

• Philosophy - for systematic thinking about life
• Workflow - for integrating habits into work processes
• My Story - for personal context and development