aucontraire

Not true that there is any sort of official rule to this effect. I've slept in a lot of crew hotels that had only semi-decent curtains.

It is true that well-behaved airlines, who take an active interest in fatigue prevention, do try to book hotel rooms with blackout curtains and good sound proofing. This is however not a universal behaviour and not all destinations where layover is necessary have any hotels with these qualities.

Where should one go now to get gory details in layman terms of new CPU:s?

Ian is my favourite CPU journalist. That insistence on reminding everyone, all the time, that he has a doctorate is seriously awkward, though.

These are classified as "agricultural equipment", and as such they of course have access to most of the road network (not major highways) and do not need to go fast. Only "unnecessary obstruction" of traffic is illegal, "obstruction for reasonable cause" is perfectly fine.

The thing that annoys me is that there is not even cursory control that these cars are used in connection with agriculture. It was fine in the past, because it was relatively rare that the regulation was abused. After a recent change in the law that made it cheap/easy to convert regular cars, it has become a menace.

Maybe back in 2011 when that was posted, if the swap was for a second hand engine out of a crashed donor car that happened to be on-hand at the independent workshop where the job was carried out.

I'd wager a guess that you'd be looking at well north of $30k for putting in a brand new engine in a Tesla-bracket BMW of semi-recent vintage.

You are entitled to 5 minutes (paid) break per hour worked in a shift, which the employer has the right to consolidate in various (but not endless) ways. This is on top the right to a lunch break which has separate rules. I think that both of these are is in the labour law and not allowed to substantially re-negotiated. (Many things across the various labour laws are explicitly allowed to be overridden by CBA).

Such a lovely vehicle!

As a fellow swede, I don't feel any compelling need to switch languages for discussing CS topics. On the contrary I'm rather sick of speaking other peoples languages after many years abroad and in international organizations. I try to use Swedish translation of concepts, when there are natural and intelligible ones available.

If there isn't a good direct translation available, just force a bit of swedish morphology onto the english root and everything flows. In some ways this makes our language richer and more specific than the one we borrow from. For us "mejl" is unambigous, whereas "mail" in english is not.

As a bonus, given an appropriate context, version control in Swedish is a cornucopia of innuendo.

Or maybe you do want to take the pill at 5am, since your are only there for a few days and it is critical that you maintain an exact 24 hour interval between doses.

As an assembly worker in the timestamp-wrapper-class factory, I am not in a position to try being clever about it. :-)

There is indeed no contract that datetimes without tzinfo are UTC. But there is a contract that they don't have a builtin timezone or DST concept and that you must define handle that separately.

I agree that python datetime objects are problematic, but for the opposite reason. It is tzinfo that is the sneaky disaster, the plain datetimes are fine.

Transparent timezone awareness always fail, unless you are 100% certain that a tzaware datetime object will remain uncoverted from the very top to the very bottom of the stack and all the way up again no matter who is reading and what they are doing.

For longterm minimization of pain, bugs and effort, you convert datetimes to UTC as early as possible and take them back to some localized version as late as possible (in the frontend, for a webapp, so that the backend never needs to know there is such a thing as timezones (except for separate validation and correction routines, since timezone definitions always end up being incorrect to some degree when you use them at scale)).

If the localization of the datetime is an essential aspect (such as the departure time of a ship leaving port), you store a UTC value together with a record of the location. Only at the latest possible moment of processing, should you do a lookup on the location data to make a local time.

Obviously, there will be exceptions to this rule. If you batch process billions of timestamps under a tight deadline and must do calculations in local time, it might make sense to have the values persisted localized.