I'm not blaming you personally, it was just some "side tech". If an org or situation puts people into positions outside of their specialty, bleep is likely. That's just the way it is.
Looks like a new entry is coming.
40 miles electric. 300 miles+ gas at 37MPG.
So you don't actually have an electric car. Bzzt! Disqualified!
Look on the bright side: if it were an F-35, the panel would have 13 nuts instead of 3, and all be different.
The poster was not the boss. The boss calls the final shots. The technician's job is to present the risks (trade-offs) as accurately and clearly as possible. If the boss(es) then choose to ignore the risk warnings, the blame falls on them. If you usurp their power, you are out the door (unless it's a legal matter).
Incidentally, I was in a somewhat similar situation where marketing planned to release about 30 websites for satellite offices all at once along with a press release about the new sites. I pointed out our "budget-oriented" infrastructure may not be able to handle such a sudden load, and suggested staggering the releases. Other technicians agreed with my warning, but the marketing chief was really disappointed, saying something like, "It's better P/R to have one big release. Staggering the releases takes the punch out of it."
I was tempted to respond, "30 crashed sites is not good P/R either", but smartly bit my tongue (based on prior experience with "reality" statements). He was a true P-H-B, always looking for a cheap short-sighted shortcut, but tried to blame us when his paper tigers got eaten. He drove one guy to retire early. Later he was under investigation for giving contracts to his buddies instead of basing them on merit. Not surprising, his buddies were also idiots.
Was it too late to re-inspect when mentioned in the meeting? You perhaps could have said, "I don't recognize that nut, but I'm willing to go in and look around."
Databases should be backed up with a text-dump (such as an SQL INSERT list), not the actual database file, because of the internal pointers that are fragile. A text-dump "flattens" the pointers. If you do use the actual database file as a backup, shut all DB writing off first, during the backup. And keep multiple generations.
I confessed, I worked on Slashdot Beta
With domain this makes sense because there is no real issues like with real estate. There is no one who is going to have to move to another country instead of staying close to their family, so there is no push for rent controls or bans on foreign ownership. So the actual issue of a domain name is purely a matter of arbitrary convenience.
This becomes more so as we expand the TLDs. And more so, as in this case, where the owner is just casually using a domain. It is no so much a matter of millions of dollars of good will, but of exploiting the resource period. I would also say that you do not buy a domain so much as rent it. This is why I suggest to my clients that they rent/buy the domain for the longest time possible.
I think this is question is a result of either a high level of paranoia or the realization by the poster that domain name squatting is not the business it used to be. If this is a typosquatted domain, and it is a primary email address, then get another email address. If it a serious domain, get some content on it.
"using its enormous data assets to make meaningful connections between people and facilitate organic engagement within a rich ecosystem"
Sounds like a drunken data orgy with the NSA.
I'm not a "troll", I'm an Agitation Engineer.
To be honest Google search now sucks and any actual consumer products are too expensive to provide any value. Like MS, google end user products are only affordable because the manufacturers take a hit on profits. This is why Apple has only a small share of the mobile phone market, but most of the profits.
So at the end of the day, all Google has is the apps. And the killer app, google docs, has not been updated in a long time. Maps has credible competitors. Bing under new owners could be a player, which it wasn't with MS because it was just a small cog in huge machine. Google can be forgiven because it provides descent products for no cost, even if those products are crappy. It is like broadcast TV. People will watch it, and maybe buy some of the stuff in the ads, because what else is there to do?
But Google without apps, with only search, is going to be highly vulnerable. At some point someone is going to figure a way to compete with Google, and if all Google has to back up ads is search, they are going to be easy pickings.
Crappiness can be done cheaper overseas.
Quick! Hide it before they use it to generate H-1B targeting resumes having impossible combo's of skills to filter away citizens.
Perhaps the whole idea of automatic tagging should be scrapped.