Here at FB, a lot of day to day coordination takes place via FB products. But production and release engineering communication happens over IRC, especially during major outages. The fallback factor in critical to keeping the plane in the air.
378 karma · joined July 9, 2014
Here at FB, a lot of day to day coordination takes place via FB products. But production and release engineering communication happens over IRC, especially during major outages. The fallback factor in critical to keeping the plane in the air.
This "hypothetically" begs the question and assumes that some three-letter acronym plotted to kill JFK.
> but also in extreme incompetence, no?
You contradict yourself. If the supposed plotters were so incompetent, how could they have pulled this off and kept the supposed cover-up alive for so long?
What does this have to do with anything? Reality isn't a democracy.
It's absolutely possible the shot came from Oswald. Tastelessness aside, try playing JFK Reloaded (https://en.wikipedia.org/wiki/JFK_Reloaded). Claiming the ballistics don't make sense is as debunked as claiming jet fuel can't melt steel beams.
In case it's not clear, I really doubt that Twitter being an also ran has to do with a culture of laziness. If anything my impression was that they overengineered without making any real product changes.
It sounds like you think if Twitter engineers worked harder Twitter would be doing better. Besides your anecdotal observation about laid back engineers, is it not plausable that the company doesn't have a vision that contributes to monster growth?
The OP on the Gentoo thread seems more than competent enough to know how to fix permissions issues though, so I agree it's a headscratcher.
This is not at all correct. SQL has well defined semantics that are standardized around the relational model and ACID guarantees. A nosql datastore is one that intentionally makes tradeoffs that force it to deviate from that model. The name makes sense if you understand that SQL was the first broadly adopted language that targeted the relational model.
I'm not very familiar with the systems you mention other than Presto. But if they do not provide relational guarantees then even if they have SQL-like syntax the semantics are sufficiently different for them to not be implementing a true SQL. Hence, nosql.
That said, Chinese academia has a massive credibility problem for a good reason. I know a PhD working in materials science and organic chemistry, and after being burned multiple times by unreproducible papers that PhD doesn't even bother to spend time trying out methods reported by Chinese researchers. Yes, this is anecdotal but it correlates strongly with the wider reporting on the issue. I'm sure there are many good researchers in China - part of the problem is that their work won't be disseminated because it will be written off.
I'm sure OP knows this, I'm just being pedantic.
A functional programming diehard could assert that iteration is a code smell, because recursion is the preferred solution. But there is nothing inherently wrong with using iteration to implement a solution in Java.