499 karma · joined September 17, 2013
From a business perspective its better to keep your high performers as long as you can - pay them what they are worth since someone else will any ways.
My gut says quiet spaces are a boon to productivity - but why not prove it instead of a research methodology with holes so large I could drive a truck through them.
Most of the time though they have a buyout component after a certain period of time and they sometimes allow part of the lease payments to apply to the final payment price.
It really just depends. More leverage for the terms on do.com vs say "Ilovewebsiteswithorangeheaders.com"
Who wants to work for someone that cheap?
My company bills 1m a day through our online site, if my logins to our domain registrar were exposed then yes. .00001 is worth it, in the case someone would gain access and change our dns or do something else nefarious.
Like wise if my login to this site was disclosed, I can live with cleaning that up should it get out.
What shouldn't happen is the companies who were affected or the company who caused this (cloudflare) to say "no big deal"
At the very least they should say if you potentially used a serious service during this time and that service was using cloudflare then you might consider changing for reasons X,Y,Z.
Whats offensive here is if you take security seriously, then if there is a .01% chance of a disclosure - you tell people to change thier passwords,tokens,etc. That is taking security seriously.
Regarding Why - ICANN runs on a multi stakeholder model, meaning governments and legal entities get a seat at the table too.
They have an interest in knowing who is behind a domain - its that simple.
Also whois privacy is not the protection everyone thinks it is. Its a lock on a door. It keeps casual looks out - spammers, scammers, etc.
If a government or police organization wants that information and they have legitimate need to do so, they will get it.
The process overall is not great, but ICANN's process didn't fail this customer. The customer needs to keep contact information up to date. If you own 100+ domains you should be very familiar and have your own process for managing this.
Its been this way since 2013.
The process to shut down a site is quite thorough in that many attempts at contact need to be made.
I'm a little surprised a phone call wasn't generated. By the time we've emailed you 3 times - we are making a phone call - we don't want to shut down a site if its at all avoidable.
This "24-48" hours stuff is nonsense - The suspension/un-suspension of a domain can be done almost immediately.
It remains to be seen but NameCheaps only potential issue here is whether they failed to renew the WHOIS privacy service.
Best of luck though and kudos for the transparency!
Good engineers don't necessarily make good managers. So they hire MBA's to be managers, but a MBA doesn't correlate to being a good manager either, in fact there is a chance that they may be a worse manager - because they don't do anything in particular (related to products that is).
So really when it comes down to it, hire managers who are good at managing people/processes and have some kind of real experience in your product or service. And in lieu of that hire a good manager who is smart and can pick it up, way down the line is hire a manager by their degree - if thats all they have going for them you are probably in for a painful ride.
Also a MBA is great if you pair it with a engineering background, but also be concerned about executives (CEO,etc) that can't sniff out people in their organization who would be a good manager regardless of background - some people have knack for management, like any other natural talent.
I think this also has some interesting implications for real estate long term - if every mcdonalds needs 50% of the space they currently occupy over time that real estate will be put back in the market, multiply that by every organization doing that and it has some follow in implications that I can't forsee but find very interesting.
I finally had to call my rep at AWS and said - you are putting your business with us in jeopardy (On other accounts that we spend significant money on) because its taken me so long to resolve this. Got it unlocked in 24 hours, but the whole thing left a sour taste in my mouth.
I suspect Google WILL have this issue as well, it has the potential to be a huge issue for your business.
Alternatively never had this issue when I've COLO'd - food for thought.
Whats more egregious is the short time span given to fix things. Either the NFL needs to open that up, or have a whole ops team who does it for the teams and has a SLA related to making it work.
If I'm dealing with the pressure to perform that goes with running a NFL team, networking and communications infrastructure is about the last thing I'd want to worry about. Belichick is being quite restrained if he's only throwing the tablets. I'd probably crack it over my knee!