Long press on remote. Magic follows.

âoeJust change the law to put the reactor back onlineâ. Guess what? A few populist politicians have been claiming that exactly the past three months. No laws were passed. The decommissioning of the power plant started 4 years ago, when the contract to procure nuclear fuel was stopped. Because a nuclear power plant just doesnâ(TM)t turn itself on or off â" a gas power plant can do that though ðY. Donâ(TM)t get me wrong: I am pro nuclear power. But the people crying âoethe f*ck you idiots closing the plant??!!â just donâ(TM)t seem to understand that this takes years of planning in advance, that you donâ(TM)t take nuclear safety in one of the most densily populated countries in Europe that lightly. So this process which takes another 3 years to inverse if we would even want to, was started long ago. Long before there were high gas & electricity prices. Oh and guess what. The plant was operational âtill last Friday. No sudden increase of prices happened & it being open didnâ(TM)t prevent high prices from happening either. Electricity prices on EU market are mainly dependent on the gas prices (for good reasons). And yes. Of gas there might be shortage. Not in Belgium though, âcoz we never bought into the cheap Russian gas myth.

Iâ(TM)ll make you a deal: you share some electricity, and weâ(TM)ll share some much more hard to get by liquid gas that is flowing in in abundance in Zeebrugge? Or: there might be more going on than some blind closing of a nuclear power plant.

This usage of location data grossly violates every GDPR aspect so is forbidden by law in EU, unless the user gave consent. So, did the spies and military personnel give their consent?

His former colleague Thomas Hertog managed to include it in a Big Bang exposition in Louvain, dedicated to Georges Lemaitre (a Belgian priest-physicist who was amongst the first to introduce the big bang idea whilst at the Louvain university). Krijtbord van wereldberoemde wetenschapper Stephen Hawking te zien op KNAL! Festival in Leuven Press coverage: https://www.vrt.be/vrtnws/nl/2... Ahhhh⦠those silly marketing departments trying to sell of lies :)

Exactly! Would somebody please think of the wasted electrons!!!!

Oh please, the textbook âoelook for spelling errors to identify phishing mailsâ. Welcome to 2021 where also scammers have access to spellchecking tools. Have you seen an elaborate phishing attempt? Except for some clever URLâ(TM)s, itâ(TM)s indistinguishable from the real thing.

This exactly. The concept was proposed by Planck and Einstein 120 years ago. What interests me (without RTFA) if this is an attempt at reconciliation of GR and QM.

So it is not a button. Great, we got that settled.

Totally agree with this! Best is to introduce a classification of patches, e.g. "minor", "significant", "major" and "emergency" patches. Agree that you get the "minor" patches pre-approved (those with minor risk & impact, "minor" to be defined in agreement with the CAB). Other patches like service packs (significant?) and OS upgrades (major) should really go through a CAB, even if it is just to inform the other IT staff members about what you are doing (and to give them a chance to point out that application X or Y can break). Finally, also agree up front who you can call at night to get a "carte blance" in case an emergency patch needs to be deployed to fix some 0-day expl0it.

First ask yourself what the priority of your CEO is. Does he really care about the IT department, does he see it merely as a cost or as adding value to the company? My experience is that in manufacturing, this is mostly not the case (as opposed e.g. to the financial services vertical). Furthermore, are there real problems with IT being exposed to senior management, e.g. was there a big loss of data that caused the entire factory to come to a grinding halt? Or do you guys do a good job, make sure that everything keeps running (with the necessary overtime, stress, cursing, ...) with just some occasional failure that never even surfaces because it has hardly a financial impact? Unless you will be able to convince the CEO that either his business will increase because of an additional FTE on IT, or that a huge risk of production loss (= financial loss) can be mitigated using additional staff, your chances to convincing him will be nearly zero. I suppose your IT manager has gone over this exercise a few times as well... Tip of the day: don't tell the CEO about your nitty gritty techy projects you want to do, like "creating the solid infrastructure you want to have". They couldn't possibly care less about what you want, they care only about the benefit for the company (which in turn after the yearly numbers have been published, turns into a benefit for them personally).

As usual, the only correct comment -- with the rectification (yes, you kids can all laugh now), is somewhere buried between the outrageous comments. Does anybody at slashdot even bother to do proper research before posting a week old news item?

The French automotive society is selling breathalyzer tests for single use for 1 euro (say: 1 US dollar) per piece. It suffices to carry two of those in the car.

Disclaimer: no expert in this area! I remember hearing stories that for electricity generating companies, the highway lighting was one way of consuming the excess production of electricity at night (knowing that a nuclear power plant does not have a big red control lever to lower electricity generation at night). Where will this electricity go now, just in the earth (all non-used electricity is wasted!) ? And who will pay for this, the UK consumers who will see a raise in their electricity bills for more wasted electricity at night?

And I don't understand why you get insightful for your comment :). There is a big difference between a traditional approach to IT, which involves fileservers, SAN, mailboxes, ... and a "private cloud" approach. What most techies do not comprehend, is that cloud computing is not a technology, but *a delivery model* for ICT services. Any existing service can be wrapped in a cloud coating, if that service is delivered in another way, to adhere to some fundamental characteristics of cloud computing (see for example the NIST definition). That is: you need to deliver your service anywhere, anytime, from any device (ubiquitous access), it needs to be in a self-service form, it needs to scale elastically (without waiting weeks for new servers to be delivered, ...), etc. Those are service characteristics that in the end will of course use technologies such as a SAN or fileserver or mailserver to deliver that service. It's just one logical layer higher than the technological layer. People who claim that cloud computing is "old stuff", have not understood what cloud computing is about.