I went down this exact path and the one thing I'd warn about is how easy it is to quietly stop once life gets busy. The system has to survive a bad week. How do you handle the off days?
I'll be honest, I was skeptical reading the title, but the reasoning holds up. The bit about cutting what you can't explain in a sentence is the part I needed. What's something you cut that you don't miss?
This lines up with what I've seen, but the part that took me longest was knowing when to stop tweaking and just commit. I burned months optimizing before I'd validated the basics. Did it click early for you, or was there a stretch you almost bailed?
Marco Reed· 1 week ago
Adding a data point: I've run this for two years and it's held up through a job change and a move, which is the real test. The trick was making it small enough that it never felt optional. How small did you start?
I went down this exact path and the one thing I'd warn about is how easy it is to quietly stop once life gets busy. The system has to survive a bad week. How do you handle the off days?
Underrated reply — this is the actual answer people scroll for. The headline gets the clicks but this is the substance.
I'll be honest, I was skeptical reading the title, but the reasoning holds up. The bit about cutting what you can't explain in a sentence is the part I needed. What's something you cut that you don't miss?
This lines up with what I've seen, but the part that took me longest was knowing when to stop tweaking and just commit. I burned months optimizing before I'd validated the basics. Did it click early for you, or was there a stretch you almost bailed?
Adding a data point: I've run this for two years and it's held up through a job change and a move, which is the real test. The trick was making it small enough that it never felt optional. How small did you start?