|
|
|
|
|
by luckydude
3943 days ago
|
|
What are these weekends of which you speak? :) Just kidding, I'm in an 18 year old company so my weekends are pretty sweet. Driving tractors and stuff. But when we started, and even now, it is rare that more than 6 hours go by and we haven't checked email. We are weird, we do pretty great support so people check emails on weekends to see if there is a big problem. If there isn't, off we go to some fun. If there is, rally the troops and get it fixed. We're in the enterprise software space so it's sort of expected that we have some coverage on weekends. All that said, if we do our job right, weekends are pretty boring. Which is why we peer review everything and regression test everything. Even with that some stuff slips through but not very often. We did a .0 release 6 weeks ago, found one bug, about to push a .0.1 release out the door. Boring. Which is how I like it. |
|
There generally should never any need to do any work on weekends unless it's an unusual situation. You're just reducing your overall productivity if you work too much. Having said that, sometimes I do work on problems over the weekend just for the fun of it.