Effective habits for software engineers
Stop grinding 12-hour days. Boost engineering productivity with systems, not brute force. Optimize health and leverage to 2x your impact without burnout.
Get the free AI Agent Building Blocks ebook when you subscribe:
Most engineers fall into a trap. They think productivity means staring at a screen for 12 hours.
Real senior engineering is not about working longer. It is about quality. It is about leverage.
This post is not just about writing code. It is about optimizing your cognitive performance.
Productivity isn’t about discipline. It’s system design.
In this post, you’ll learn
How to optimize sleep and diet for cognitive performance
Methods to raise the quality of your technical work.
Techniques to document your impact for career advancement
Health
Consistency over intensity: You cannot catch up on sleep debt. A consistent schedule works better. This improves how your brain solves hard problems.
The “Sleep on it” debugging method: Spending two hours debugging on a Friday evening often yields nothing. Returning on Monday usually solves the problem in 15 minutes. Rest resets your context window.
Eat “Real” Food: Avoid the pizza and soda stereotype. Eat food found in nature, like vegetables, meat, or fish. This avoids glucose spikes that lead to afternoon brain fog.
Don’t Break the Chain of Exercise: Exercise is for mental clarity rather than muscles. It is better to do 20 minutes daily than to destroy yourself for 3 hours on Sunday.
Energy management: Track your energy levels. If you peak at 10 AM, then schedule deep work at that time. If you crash at 2 P,M use that time for low cognitive tasks like admin or email.
Environment Design: Working from a cramped kitchen builds resentment. Optimize your desk setup to induce a flow state. Create an environment that you enjoy being in while working.
Technical
Don’t be a human linter: Automate style checks. If a machine can catch it, then a human should not waste calories on it.
Focus on the “Hard” stuff: Spend code review energy on design patterns, bugs, and non-negotiable changes. Prioritize boring and maintainable code over shiny new tech.
Read before you write: Prevent spaghetti code by understanding existing patterns. Spending half an hour reading can save hours of refactoring.
Data Structure Driven Development: Do not start typing code. Start with the data. Define the structures and flows first. The code becomes a trivial implementation detail. Code should be simple enough that you can draw the high-level flows on a whiteboard.