I live in Boulder, I bet you don't.
That'd be correct. I live a few states east of you.
I stop, check the road, make sure no cars are coming, and if it's clear, then I'll go
This is the stop sign maneuver, also used at a flashing red signal or a right turn at a steady red signal. At a stop sign, I make sure to slow enough to put weight on my foot before proceeding.
but only have waited twice what the usual time it takes for that light to change (yes, I keep track of that).
I too keep track of how many cycles have elapsed, and I report problematic intersections to the city's hotline once I do arrive. But in the 35 states without a dead red statute, even waiting an hour isn't good enough for the letter of the law. Until about a week ago, it was 36; Indiana's dead red statute took effect on July 1 of this year. Before that, there was one intersection on my way to work where I often had to wait over five cycles for some SUV to pull up behind my bicycle. Oncoming traffic kept getting green left turn arrows while I got an eight-minute steady red in the straight lane. I reported that one to the city and the state, which kept pointing fingers at each other.
But if you do all that, then they won't ever see you do it, and there will be no grounds for them to complain.
Treating a red light as a stop sign works unless there happens to be a police car parked in a nearby parking lot.
Nobody can avoid killing you if you don't even pretend to follow the rules of traffic.
I'm a cyclist, and I follow the rules of traffic to the extent that I can. But the metal rims of my bicycle don't have enough surface area to consistently trigger the vehicle-sensing induction loops at intersections. At some intersections in my home town, I've seen even a bicycle and a motorcycle put together fail to trip it. So in the 35 states that haven't passed dead red laws, I don't understand how to follow the law against crossing the street at a red light, other than by not traveling at all.
Their answer to an OS not properly doing something is "fix the OS".
How would someone go about fixing an operating system whose biggest problem is that it can't run many of the proprietary applications on which he relies? There are plenty of applications for Windows that aren't ported to any *BSD.
Do you go to homeless shelters and ask for donations from the homeless too?
If by "donations" you include donations of one's time, yes. Some homeless shelters expect those people who are able to perform some sort of work to do so.
That would require some target-identification, while this is just target-tracking. You point at a target and shoot, and the system makes sure the target is hit. Now it could avoid any target you try to shoot at, but that would be a bit silly: a good way to make sure all your bullets miss is to just not fire them!
If you're building services that still require "regular maintenance windows" in 2014, you're doing it wrong.
This is a really nice sentiment but is in fact somewhat disconnected from reality.
In the web world, building zero downtime services that don't require maintenance is doable. In many enterprise IT environments with legacy or bloated software (hospitals, education, government) it's a non-starter. The staff do not have the skill, the applications don't have the support, and the political will within the organization is not there. Database migrations alone can be a major source of downtime, and that's largely true even for web services.
Support for off-hour work is part of the job. Don't like it? Find another job where you don't have to do that. Can't find another job? Improve yourself so you can.
He might just need a better boss--it sounds like this one expects the guy to stay up all night for maintenance, then come in at 9am sharp, as if he didn't just do a full day's work in the middle of the night.
Rather than automating, he should be lobbying for the right to sleep on maintenance days by shifting his work schedule so that his "maintenance time" IS his workday. "Off-hour work" doesn't mean "Work all day Monday, all night Monday night Tuesday morning, and all day Tuesday." Or, at least, it shouldn't.