Bad habits we get when coding and how to break them

The post groups several habits that show up in coding life and says they often reinforce each other. It points to long periods of sitting, irregular eating, weak work structure, poor eye care, disorganized workspaces, little exercise, bad posture, and taking on too much work.

Reading notes

#

• The author says these habits came from time spent gaming before programming and became more visible during college work.
• He describes trying to change many habits at once and finding that the results did not last.
• He argues that a more strategic approach is better than trial and error.
• He says self-assessment is the first step, because awareness comes before change.
• He recommends starting with a work structure as the first major improvement.
• He explains the Pomodoro Technique as 25 minutes of work followed by a 5 minute break, repeated four times, with a longer final break.
• He says he later found 50 to 55 minutes of work with 8 to 10 minute breaks more effective for him.
• He says a work structure also made it easier to change eating times and take eye breaks.
• He suggests blue-light blocking glasses for screen use, especially before bed.
• He says standing more often, including using a standing desk, helped with sitting time and posture.
• He says exercise is the hardest habit to build, and should be part of a system instead of relying on willpower.
• He cites habit stacking as doing a new habit after an existing one is finished.
• He gives examples such as changing into exercise clothes after waking up or after finishing work.
• He says bodyweight exercises done slowly can work when a gym is not available.
• He closes by saying habits shape identity and that change is about becoming a better person, not just reaching goals.