I often split my big projects into smaller deployable pieces (e.g., rather than 1 large feature launch, "silently" deploy backend changes first, then expose in the UI).
This approach also helps in debugging: deploy and fix each piece incrementally.
The only times I've burned out are when working on a massive update without any visible progress. When I finally deployed, I would be overwhelmed with a huge number of bugs to fix.
Comments
I often split my big projects into smaller deployable pieces (e.g., rather than 1 large feature launch, "silently" deploy backend changes first, then expose in the UI).
This approach also helps in debugging: deploy and fix each piece incrementally.
The only times I've burned out are when working on a massive update without any visible progress. When I finally deployed, I would be overwhelmed with a huge number of bugs to fix.