OpenAI jumped the gun before *the closing party* - didn't even let the kids celebrate their winning properly before stealing the spotlight
Also in the article
> In response to the controversy, OpenAI research scientist Noam Brown posted on X, "We weren't in touch with IMO. I spoke with one organizer before the post to let him know. He requested we wait until after the closing ceremony ends to respect the kids, and we did."
> However, an IMO coordinator told X user Mikhail Samin that OpenAI actually announced before the closing ceremony, contradicting Brown's claim. The coordinator called OpenAI's actions "rude and inappropriate," noting that OpenAI "wasn't one of the AI companies that cooperated with the IMO on testing their models."
AWS really strongly focuses on gaining customer trust, and they will only lower price, and never increase price. They won't turn off things until the last customer stops using it (they might stop new customers from onboarding)
I did not enjoy working for AWS so I left pretty fast, but some of the customer obsession there really impressed me.
Internally we treat customer names and email addresses as the second highest data classification. The highest one is credit card/financial/password data.
What does it mean? It means that there are a bunch of requirements that a software team must fulfill and pass (reviewed by an SDE trained in the process outside the team). This makes accessing this sort of data a PITA for a lot of people, and I can see why they why they would send out notifications when a breach like this happen. Amazon takes security very seriously, and it in fact creates quite a bit of friction to many engineers. However, I'd rather than than the break things and ask for forgiveness model like some other companies (not going to name names here)
I've seen 5 segfaults over the last week in our system. Unfortunately we don't enable core dump in our system (yet) so we haven't really had a good sense of what might cause the system. We've been seeing about 30 SIGSEV's over the last three months, but we haven't been able to root cause it yet.
The next line reads: "As a result of these factors using the filesystem and relying on pagecache is superior to maintaining an in-memory cache or other structure—we at least double the available cache..."
And if you don't know about pagecache, it's an in-memory cache managed by the OS and has nothing to do with JVM's memory at all.
And you forgot that C++ isn't the easiest language when it comes to designing a distributed system. Scala, as I mentioned, offers many other features that suit the needs of the team. Of course if you're a good engineer you'll know that there are trade-offs such as compiling time, but that's the same for every engineering decision.
http://research.microsoft.com/en-us/um/people/srikanth/netdb...
Not sure on what basis you claim the choice of language to be "questionable", but keep in mind that Scala's type-safety and many other features are much more difficult to achieve in C/C++. Cleaner code is sometimes more important than some tiny gain in performance.
Also in terms of scaling, Kafka cleverly takes advantage of many aspects in their design to ensure low-latency high-throughput.
* Little random I/O
* Relying heavily on the OS pagecache for data storage
Performance-wise, Kafka can outshine some of the in-memory message storing message queues.
Source: http://kafka.apache.org/documentation.html#design
http://research.microsoft.com/en-us/um/people/srikanth/netdb...
I am interviewing with LinkedIn and the only sources I could find about the company were glassdoor and their engineering blog. However, when I search for further information about the company on Hacker News and Reddit, it's mostly about people using the service itself rather than about the work environment there.So does anyone have any experience with LinkedIn? They told me they had a lot of...
We use "friend/friends" (we don't distinguish between plural and singular) for a generic "you". Otherwise, in social situation, we have to figure out the relative social order to address the other person, i.e. calling them by titles/roles such as aunt/uncle/mom/dad etc.
It's a big headache cause it can be very awkward to use one pronoun (for example, calling a woman was "younger sis") and she turns out to be older - it can be impolite, but then some women will be offended if you call them as "older sister" right away, because, ugh, you consider them older. God, it's a convoluted mess of pronouns :(
Just chiming in, Google actually has plan to work with TV makers to integrate Chromecast technology into future smart TVs, and hopefully other peripheral devices too.