Re: You really need a plan B.
That's why so many apps have their own notification/communication methods now. You control both sides of the channel, can monitor delivery, where/when it's been read etc.
515 publicly visible posts • joined 12 Jun 2013
I appreciate that, but who declares their "peak" hours to be 24/7/365? That's not what peak means.
If we assume 40 hour week, 52 weeks per year (divided by 12) then we've got 173 hours per month. That puts you at €271.36 for Microsoft and €1052.28 for "other".
Still roughly the same ratios, but more believable numbers.
Definitely an area that can be improved. Someone cancels their appointment, offer it to someone else automatically. Then offer the appointment that they had to someone else (or even back to the original canceller so they don't end up at the back of the queue, just a straight swap) etc.
No staff interaction needed, and people get to move up the queue.
Sadly they're also convenient. I used to feel exactly the same: raspberry pi under the TV, IR sensor wired in etc. Then the SD card died and we used the functionality of the (relatively cheap) TV "just until I fix it"... And we've never looked back.
It supports all the free and paid for streaming services, has a dlna browser on it, and supports screen mirroring.
It may well be hacking everyone, but it gets unplugged when not in use so can't be doing that much damage...!
If it can save someone on £30k/year 2 hours per month it's paid for itself.
If it will read, summarise, and prioritise my emails then it will probably pay for itself too.
Then again, if half the company are using it to write emails and the other half are using it to read emails, we could save ourselves a lot of time by just buggering off home!
Whole grid capacity is 80gw/hour. Current use right now is 40.35gw/hour. Overnight (from 11pm to 6am) looks like it's about 28gw/hour. So there's 7 hours worth of 12gw available (to make night match day). That's 12 million hours (or 300 million miles) worth of home charging available every night. Not everyone will need to charge every night, and there's already tech out there that balances when people charge. If there was enough generation to run flat out then your overnight capacity jumps up to 52gw/hour, which is 1300 million miles of charging capacity.
That's based on current numbers, not what it's going to look like in 11 years. According to https://roadtraffic.dft.gov.uk/summary we need about 700 million miles of capacity per day to cover every car out there.
They didn't decompile it, they just installed it and noticed that if you didn't follow all of the steps then it still worked but was insecure.
Microsoft software also used to be like this, and then they started making things locked down out of the box. It's not a bad thing that they're helping others learn from Microsoft's mistakes of the past.
You use other signals to determine if the sign in is legitimate, combined with reauthentication to perform privileged operations.
For example you can require that users only sign in on devices that have been registered with IT. This installs a certificate which is used as another factor.
Sadly some of these features are only available on the more expensive tiers.
My partner had the same problem. Took about 2 days but I managed to recover her stuff.
1. Uninstall Google Drive.
2. Install an old version of Google Drive (there's a version 82/83 floating around on the internet).
3. Disable the 2 Google Update services (they won't be running, but they still need to be disabled).
4. Disable the Google Update scheduled tasks (2 of them).
5. Make sure Google Drive is not running.
6. In the User Data folder, go into Google > DriveFS > the folder with a long number.
7. In that folder there's a folder called backups, which has another folder with a couple of long numbers. Move all of the files from the "Backup" folder into the main folder (from step 6).
8. Start Google Drive.
9. Go into your G Drive (or wherever it is) and copy _absolutely everything_ somewhere else outside of Google Drive.
Due to the way that Google caches stuff, what you have locally will be your latest files. The problem looks to be that things weren't being uploaded properly.
10. If you want to carry on using Google Drive (!!!), re-enable the update services and wait for Google Drive to update. It will then sign you out and reset your local state to what it had in the cloud.
11. Use a tool like robocopy to overwrite the contents of your G Drive with what you had copied elsewhere.
When we asked FEMA for comment on the matter its response was succinct: "The posts you're citing are false," the agency told us.
I know obviously you have to ask, but
A) If it was a cover up would they turn round and say "yeah you got us, prepare for brainwashing"
B) How many people would lose their excrement if the person responding had a sense of humour and replied "yeah you got us, prepare for brainwashing"
Depends on your definition of working really. You've spent 25% of the existing project, assumed that you don't need to pay the £10m per month subscription fee, and you've solved the problem for stationary officers that are in their cars and have line of sight to the sky.
If we're talking about only solving part of the problem then equip them all with dual SIM phones that the car kit hot spots off. 2x unlimited SIMs on different networks.
Significantly cheaper and technically more reliable and useful than Starlink. Not to mention not having to deal with a CEO who has a history of disconnecting people he doesn't agree with.
Both of these plans fall down in actual emergencies though
Getting requirements nailed down is always good, but outsourced projects fail more than in house ones in that scenario. Partially because you're over a barrel at that point with your current supplier, where you either get the wrong thing delivered for (maybe) the original cost, nothing delivered if you can walk away and lose what you've already paid, or pay a premium to change the spec.
The NHS is paying £77m per year (as of 2018) to EMIS and TPP just for patient records systems that probably don't even cover the whole of the NHS. Could build quite a team with that budget!
It's not about saving disk space, it's about build performance: I have a referenced NuGet package. So it's one on my disk where it was downloaded. Then when project A is built it gets copied to that folder. Project B references project A so takes a copy when that gets built etc. Multiply that by tens or hundreds of dependencies, tens or hundreds of projects, and hundreds of builds per day and those savings add up.
I don't need multiple copies of something that was downloaded for me automatically from the Internet
Yes, because letting founders have a say in their own company is definitely a bad idea...
Also, some things are 1 person 1 vote (as opposed to 1 share 1 vote) so it's possible that the number of people not called Larry in agreement is closer to 67%. I haven't checked whether this is one of those scenarios
"37 Signals ops team remains the same size"
If your Ops team can handle your on-prem load, then they were either over-spec'd for cloud or you were doing cloud not quite in the way it was intended. We don't have an Ops team. No one is racking and stacking, installing OSs, running updates, or doing anything related to server IT. Then again, that's the distinction between PaaS and IaaS.
Your car comparison is a good one: look up the Naruse pedal. A potential way to decrease the number of accidents made by using the wrong pedal, but 0% chance of being implemented because it'll be a break to the "standard".
We've already standardised electric chargers in the UK (type 2 and CCS). A new standard will most likely have to be agreed when power requirements exceed the current connectors.
The international sockets is a good example too, because it's the existing standards that are out there that prevent the "innovation" of being able to unify the world on to one standard.
My point (in a very clumsy way) is that standards discourage innovation. That's fine if there's no innovation left to make, or if you've got a standards body (like USB) which can handle the innovation
So is this the end of innovation for physical phone connectors now? If no one is allowed to choose what kind of connector we can use then we're stuck with (the many variants of) USB-C. Don't get me wrong, I'm all for standardising things, but if this decision had been made 10 years ago then the standard would have been micro-USB and we wouldn't have reversable cables or "power delivery".
I barely have a working knowledge of electricity, but I always thought amps were "drawn" rather than pushed. I've been told (for example) that adaptors need to match voltage, and need to have an equal or higher amp value than the device you're powering.
"Did I mention that public charging points will be far more expensive to use than overnight charging at home?"
I would imagine that a market will appear for cheap overnight public charging. In the same way that Tesco etc list their car parks on apps for cheap long term parking, something similar will come along for charge points too. At the end of the day they've paid for the infrastructure so as long as they get a mark up on the electricity it's worth doing.
If overnight costs them 10p/kWh then they're better off selling it at 15p/kWh than not selling it at 40p/kWh
The problem isn't just the sending, but the receiving too. You need your 999 service to be able to receive a text message and link it to the ongoing call. Like E911 or E112 do. Now you just need to make it a globally recognised and implemented standard, and hope that wherever you're calling from has enough connectivity to maintain a data connection as well as a phone call.
The bit you're suggesting is the easy bit, and has (rather unsurprisingly) already been done.