I kept convincing myself I was fine because tasks were still getting shipped but taking calls on weekends and working past dinner slowly drained all my energy.
I didn't need a long vacation I just needed to stop letting work leak into my evenings.
Taking a full step back and enforcing a hard no work rule after a specific hour made a massive difference in my sleep and overall focus within a month.
How do you keep small work exceptions from turning into permanent bad habits?
We spent months building custom requests to lower our cancellation rate, but it backfired. The product became so bloated that users started leaving us for basic single-purpose alternatives that were just easier to navigate.
It s scary to pause feature work, but simplifying our UI did way more for retention than adding another setting.
Have you ever dedicated a full dev cycle strictly to removing old features, and how did your active users react?
Run into an issue recently where AI wrote bad logic for a discount feature, but generated passing tests for it anyway because the model made the same wrong assumption in both places.
Now I review test files first to verify the assumptions before looking at the implementation.
Saved me a ton of review time this past week.
What workflow tweaks have helped you review model generated code faster?
