This right here cannot be overstated. Internet blogs are not a uniformly distributed sampling of the population.
Manufacturing Consent applies to more than just mainstream news media.
Sometimes, weekend work with a team is some of the most engaging work one can perform in a salaried role. I have fond memories of the cycle of scrambling before a launch, the catharsis of the launch, and then the ensuing vacation.
The key thing is committing to the whole cycle - crunch is sometimes a necessary evil but must be followed by equal and opposite rest. Any group that doesn't respect this yin-yang is undeserving of your labor.
If looking at a potential employer I find out they expect weekend work and don't treat it like overtime, I assume they are bad employers and move on.
Typical pushback is a lecture about the importance of being a "team player" and pressure to cancel or reschedule things to make the boss look good.
"Sorry, no." Done. Either it's a shitty enough work environment that they'll fire you, in which case they would have gotten around to it any way, or it's not, and they won't, and nothing happens.
This pushed three of us (out of 5) to quit in the next couple of months (after getting another job sorted).
Assuming you are working a standard Mon - Fri, the correct amount of weekends to be working is 0.
There is some tradeoff point if you make overtime and you need the money. If you are salaried, then just say no.
I occasionally get asked to work a late night or a weekend. It's never a real emergency - nobody is blocked, it isn't software that impacts live users, etc. It's just scheduling fails by some middle manager somewhere. My answer is always the same:
"Oh, sorry, I can't. Already scheduled."