Intesab Husain

Twelve-hour days, meals at the desk, sleep debt worn as a badge. I tracked my own numbers for six months while building my app and the trend line was genuinely alarming,resting heart rate creeping up, sleep consistency in pieces, and I only noticed because I happened to be writing a tracker at the time. Otherwise it would have just been a normal year.

The advice everyone gives is a list: water, eight hours, meals. I've read it, I've ignored it, and so has everyone I know who ships alone.

So instead of the ideal version - what's the one habit that actually survived a launch for you? Not the one you know you should have. The one that's still standing

These are the five tools currently doing most of the heavy lifting in my SaaS and automation workflow:

Claude system architecture, deep product research, complex technical planning, debugging difficult problems, comparing implementation approaches, and turning unclear ideas into detailed execution plans.

Codex working directly across large codebases, building complete features, refactoring existing systems, fixing production issues, writing tests, handling migrations, and completing changes that touch multiple files and services.

Awish building automations and connecting the apps I use without spending hours on APIs, OAuth setup, or complicated integration steps. I use it when data, notifications, approvals, and actions need to move reliably between different tools.