In countries south of the 49th parallel, DST is just a PITA. In countries north thereof, it's a way to enjoy the little winter daylight while not being woken by the dawn chorus (that's birdsong for you city-dwellers - birds are pesky things that fly but aren't jets).
As for saying programmers don't understand DST, that's about as true as programmers not understanding leap years and the millenium. Programmers get this stuff; it's management who say it's too hard. E.g. MS DOS got it wrong 'cos they were afraid it would spook end users if their system clock wasn't in local time. Unix got it right 'cos it was written by programmers.
I hope that when Bill Gates dies, it's in the hour that the clocks go back:-)
Software development managers like to appear to be in control. All methodologies are merely a way for them to give themselves that appearance. Developers come, as is well-known, in two sorts - those who can, and therefore don't need any of this stuff, and those who can't. Those who can't won't be any better for any of these techniques, but it gives them something to hide under.
The big benefit of these techniques is they stop your boss playing with critical path/PERT tools. That really screws development.
Last time I was in the US, about 15 years ago, there were lots of yellow buses carrying school kids. Assuming they're still there, don't they count as Mass Transit?
Patents in the US are "first to invent" ultimately as discovered by examining the inventor's notebooks. Almost everywhere else, it's "first to file", i.e. when the patent office receives the application. Which means US patents can claim to precede valid earlier patents elsewhere. That was "sort of" OK when the two patent systems didn't overlap - a US company gets an EU patent when its application is received by Albert Einstein or similar. But extending US patent jurisdiction outside the US can lead to a conflict over validity.
There's a historical precedent here - AFAIK my father was awarded a patent during WW-II, but wasn't allowed to publish it then because of national security. After the war, a US partner patented the same idea, and claimed damages from the UK company for its production during the war.
Slashdot Mirror
In countries south of the 49th parallel, DST is just a PITA. In countries north thereof, it's a way to enjoy the little winter daylight while not being woken by the dawn chorus (that's birdsong for you city-dwellers - birds are pesky things that fly but aren't jets). As for saying programmers don't understand DST, that's about as true as programmers not understanding leap years and the millenium. Programmers get this stuff; it's management who say it's too hard. E.g. MS DOS got it wrong 'cos they were afraid it would spook end users if their system clock wasn't in local time. Unix got it right 'cos it was written by programmers. I hope that when Bill Gates dies, it's in the hour that the clocks go back :-)
Software development managers like to appear to be in control. All methodologies are merely a way for them to give themselves that appearance. Developers come, as is well-known, in two sorts - those who can, and therefore don't need any of this stuff, and those who can't. Those who can't won't be any better for any of these techniques, but it gives them something to hide under. The big benefit of these techniques is they stop your boss playing with critical path/PERT tools. That really screws development.
It's now much easier to be vulnerable to both Windows and Linux attacks.
Shorten the working week by 25% means 20% of the old week is paid overtime at time-and-a-half rates, i.e a 10% pay rise. You do the math.
Last time I was in the US, about 15 years ago, there were lots of yellow buses carrying school kids. Assuming they're still there, don't they count as Mass Transit?
Accountants are also obsessed with maths. Get real, who needs skill in the Post Truth age?
What's it for?
DARPA have different requirements for chips than the rest of us. For example, they might not want separate "systems management" circuits.
Patents in the US are "first to invent" ultimately as discovered by examining the inventor's notebooks. Almost everywhere else, it's "first to file", i.e. when the patent office receives the application. Which means US patents can claim to precede valid earlier patents elsewhere. That was "sort of" OK when the two patent systems didn't overlap - a US company gets an EU patent when its application is received by Albert Einstein or similar. But extending US patent jurisdiction outside the US can lead to a conflict over validity. There's a historical precedent here - AFAIK my father was awarded a patent during WW-II, but wasn't allowed to publish it then because of national security. After the war, a US partner patented the same idea, and claimed damages from the UK company for its production during the war.