For software engineers, your lazy version wants you to do the opposite of what's listed here.
1. Stop just doom-scrolling tech Twitter, Reddit, and release notes all day. It fries your attention and gives you anxiety and zero skills.
2. Stop shipping half-done work and calling it learning. Finish things. Closure builds confidence.
3. Treat sleep as the most important activity. Broken sleep equals buggy thinking.
4. Lift weights or do some hard physical activity. Your job is sedentary; your body needs resistance, not just more coffee.
5. Eat real food, not just junk calories. Garbage inputs lead to garbage focus.
6. Walk every day. Long walks solve more design problems than staring at a screen. Believe me fr.
7. Plan tomorrow before logging off today. Engineers with a plan beat engineers with talent. And i have seen this so many times.
8. Limit stimulants. You want to have consistent output, not simply spikes followed by crashes.
9. Write things down. Design docs, notes, decisions.
10. Build one thing deeply instead of touching ten things shallowly. Depth compounds faster than breadth.
11. Say no to low-leverage work, pointless meetings, and energy-draining people.
12. Separate identity from job titles. You are a builder, not just a Jira ticket machine.
13. Learn systems, not just frameworks. Frameworks expire. Systems thinking is the moat.
14. Take breaks without guilt. Burnt-out engineers don’t become seniors; they quit.
When your career feels stuck, unfocused, or empty, don’t blame the market.
Check your habits. Check your inputs. Check your daily systems.
Good code (and coder) starts with a disciplined life.
@bigslam_ @yehhmisi Imagine you have a search bar that shows results as someone types. If you fire an API request on every single keystroke, you’ll end up making lots of unnecessary calls. With debounce, you delay the request until the user pauses typing so you only query when input has settled.