The official statement doesn't mention "IT"...

We would like to apologize once again to our customers, suppliers, and related parties for any inconvenience caused by the suspension of our domestic plants as a result of the malfunction in our production order system at the end of last month.

The system malfunction was caused by the unavailability of some multiple servers that process parts orders. As for the circumstances, regular maintenance work was performed on August 27, the day before the malfunction occurred. During the maintenance procedure, data that had accumulated in the database was deleted and organized, and an error occurred due to insufficient disk space, causing the system to stop. Since these servers were running on the same system, a similar failure occurred in the backup function, and a switchover could not be made. This led to the suspension of domestic plant operations. The system was restored after the data was transferred to a server with a larger capacity on August 29, and the plants resumed operation on the following day. We would like to report that we have identified the above as the true cause. Countermeasures have also been put in place by replicating and verifying the situation.

We would also like to reaffirm that the system malfunction was not caused by a cyberattack, and apologize to all parties for any concern this may have caused.

Going forward, we will review our maintenance procedures and strengthen our efforts to prevent a recurrence, so that we can deliver as many vehicles to our customers as soon as possible.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fglobal.toyota%2Fen%2Fnewsroom%2Fcorporate%2F39732568.html

Right, but the solution isn't to just follow the policy and work the extra hours, thus produce less hoping someone will fix it - that just hurts everyone (the developer most in reduced bonus/pay increment/whatever). They will not fix the problems because as far as they are concerned they just have a bad developer. The developer then gets a bad rep and becomes completely apathetic to the organisation due to bad performance gradings etc, but by then the organisation probably does have a bad developer and grounds (and evidence) to fire them.

How is that a solution? Nobody wins in that scenario, let alone the developer.

Yeah! Too right. And because people are still getting murdered in Iraq we should stop trying to address deaths from obesity in the West! Focus!!

I was seriously considering moving to a Windows 10 environment with my next hardware change. Seeing the Edge tooltips popup over the Chrome icon in my Windows 10 VM has changed that. I'll now change professions and pick grapes in France rather than continue in this field. Apple have killed the Mac as a serious platform by not releasing pro level hardware since 2010-2011, MS made leaps with Windows 10 and then killed it, and there is still little viable software for *professional* collaboration with non nerds on Linux (yes, I mean the Photoshop / Office / UML / yadda yadda stuff - sure, it works at a basic level but ultimately you need the real thing in a Windows or OSX VM to be compatible at a level that doesn't annoy everyone). Apple used to almost fill the "I need a Unix workstation with compatibility with the big commercial apps" space with OSX and the Macbook Pro and Mac Pro lines, but there's nothing now - Windows and docker/vagrant seems to be the way forward, and with more and more native Unixy support on Windows I suspect things are likely to change yet again. Lesson: don't invest in any particular platform in any significant depth - learn to read properly.

One of these browsers, given it's history, is most likely optimised for X over other screen rendering platforms. Sure, the benchmarks concentrate on JavaScript, but ultimately this is going to result in manipulation of the DOM in any real world test and therefore re-rendering... Does this therefore boil down to how well these browsers optimise their performance on X, as opposed to anything else? Given the changing landscape (Wayland and alternatives) does this have much relevance?

Nah, clearly owning and using (daily) a 30 year old keyboard is something every geek should be aiming to achieve. Just think - it will probably become sentient in a few more years and eclipse whatever supposedly 'ground breaking' AI project the owner is working on. Perhaps someone should come up with a better solution than those HP washable things - a great idea in principle but no geek is going to use it because it isn't built like a tank and doesn't deafen everyone around them, and let's face it, only geeks are going to go for something like that as everyone else wants whatever the latest keys are, then wireless, then bluetooth, so will never keep hold of it for any length of time. Sad times. The planet is doomed.

https://ancillary-proxy.atarimworker.io?url=https%3A%2F%2Fwww.gov.uk%2Fgovernment%2F... (which links to the actual guidelines and consultation documents).

No, neither is acceptable in those cases, but the topic is audio playback in an audiophile environment, so data on a gigabyte network doesn't have to travel at 48kbit/sec - it can fully saturate the buffer almost instantly if necessary before playback starts as the whole listening experience was probably started only after several hours of procrastination and cleaning of equipment took place. The system would have enough time to transfer the whole FLAC 192kbs album before playback needed to start! For a video game and many applications, sure, the latency is usually acceptable (I'm a semi-pro musician and make use of soft synths, so I'm fully aware of the effects that even 30ms of latency vs 10ms can have, let alone the 500ms or so that pipe organs can sometimes exhibit).

Only if the data was sent at 48ksamples per second. I would hope that on a gigabit network the data was sent to saturate the buffers as fast as possible and playback can start as soon as the buffer is full.

You need a new monitor - your current one clearly doesn't have a suitable the resolution and/or physical size for the dice goodness.

The PowerMac line ended in 2006, almost a decade ago. The fact you could use one as a flower vase proves the superior design - there aren't many computers that can be reused in such a way once they become obsolete!

On a $2000 laptop for a $800+ device - both of which need to be regularly refreshed too (and you probably need to own multiple devices for testing the different form factors). The $99 subscription pails into insignificance on just those things, let alone everything else associated with development (server hosting, SSL certificates, business taxes, coffee, expensive german cars, etc)

In a word, no. "A lubricating liquid is sprayed onto the porous surface, filling the tiny gaps. The liquid is held in place by capillary forces and creates a slippery surface for food or other liquids."

OK, I was a little off according to this study - http://citeseerx.ist.psu.edu/v... - 1.1 to 1.2 seconds is the average there, but there are other studies that had higher times, and other sources quote much longer, eg http://copradar.com/redlight/f.... Presumably it takes most people significant time to realise what's happening, not panic, then move your right foot from the accelerator to the brake and the left onto the clutch and press down hard.