skysight-inc/HackerNews huggingface dataset:
Interesting. NEVS is what is left of Saab Automobile is called (nevs.com)
Probably a lot on bare metal, but we are a special case here. It really brings down the latency to respond to network events. A single context switch is in the range of 100K-1M CPU cycles.

The reason why is because we avoid all the indirect cost of context switching, which is all the various caches that has to be flushed. And also the context switching itself, of course.

However, you can still do a lot on Linux to equalize things if you really want to get down to it. For anything but special cases Linux really does a good job with scheduling. After all, you are likely not running much else other than your intended service.

That said, for me this thread was a slight wakeup-call that made me look more into fibers and co-routines. I have been wanting to use these for a long time for some things.
I like your suggestion about understanding data and where it came from. You are right that there are more interesting and complex questions than knowledge base questions, and I have no doubt that many people here agree with you. Knowledge questions in interviews seem to be a popular punching bag these days.

Let me offer a few thoughts to maybe soften the extreme point of view that knowledge questions are any kind of negative signal.

First, please don’t assume that the existence of knowledge questions means that the interview process of the author is based on them or primarily about them. Most, if not all, companies have multiple interview modalities, and basic knowledge questions is just one of them.

Given that there are multiple phases for an interview, the most important thing a candidate should do is avoid being rejected for something simple. It’s a gauntlet, and if you only think about the boss stage and forget to do really basic things like spell check your resume or choke on how to summarize what gradient descent is, you might not even make it to the hard interview questions.

From experience, it certainly is tempting to think that because you can look up knowlegde questions that people will just game it and ace them, but that’s not what happens in practice at all. In reality, people who don’t have a background in the subject might be able to recite something they’re heard or read, but have a very hard time answering any followup questions, dealing with terminology they haven’t heard, or connecting topics together. It’s very easy as an interviewer to detect BS by asking very straightforward followup questions, by having a conversation. Plus there’s a much bigger risk in trying to memorize answers to things you don’t know; when it’s quickly discovered you were trying to fake it, that is grounds for being quickly rejected.

Knowledge is part of the background you need to get to the interview, and while it might seem like you don’t use it directly on the job, it’s part of a foundation of exposure to the topics that connect the pieces together. There’s nothing wrong with exploring bounds of a candidate’s knowledge to get a sense of how much they covered in school, how much they exercised during internships or other jobs, how much they’ve thought about it on their own.

It’s perfectly okay for there to be easy interview questions (you’d be surprised how many get answered incorrectly!), and for there to be questions that are broader in scope than things you’ll do day-to-day. Keep in mind, it’s a conversation where you’re trying to convince the employer that you’re already trained in the subject, and also well-rounded and have the potential to grow.
Getting to VP level at a "top startup" has little to do with data science, and everything to do with your ability to play the networking game. Depending on the size of the company, VP level jobs are more about management skills than technical proficiency.
I agree. I wanted to make sure it was clear why people might have the misunderstanding that the project development isn’t continuing. I think it’s worth directly correcting that perspective.
Environmental activist Shannon Dosemagen joins FSF conference keynote lineup
I think that's more like, "The estates of former E-scooter owners are dangerous to the finances of SUV owners."
*BND, from Bundesnachrichtendienst
Obvious in hind sight.

Fowler's Event Sourcing [2005] https://martinfowler.com/eaaDev/EventSourcing.html

Published after I stumbled onto my solution.
I agree. The article smells of confirmation bias.
AirBnB is probably not the best example given that the cost of last minute cancellations is mostly borne by the people renting out their places (some of which are admittedly full-time businesses) rather than AirBnB itself.
Preemptive disclaimer: I don't want to belittle the work the authors did here in any way, and are actually excited especially about the reversible, lossless jpeg<->brunsli coding and that google's buy in and network effects will most likely mean this comes to a viewer/editing software near you in the not so distant future (unlike lepton, which never got out of it's tiny niche).

But seeing the 22% improvement figure reminded me that the typical JPEG file on the internet is rather unoptimized even on write-once-read-many services like imgur or i.reddit.com which transform files (stripping meta data etc) and do not preserve the original files.
Just using the regular vanilla libjpeg encoder you can usually save 5%-10% just by lossless recoding of the coeffs and the better-yet-more-computionally-intense mozjpeg coder can even get you a bit further than that.

Then again, the imgur single image view page (desktop) I just randomly opened by randomly clicking an item on their homepage transfers 2.9MiB of data with ads blocked (3.9MiB deflated), 385KiB of which was the actual image, and that image can be lossless recoded by mozjpeg to 361KiB (24KiB difference, a 6.2% reduction), so the 24KiB (0.8%) reduction out of 2.9MiB of cruft hardly matters to them I suppose and may be cheaper in bandwidth and storage cost to them than the compute cost (and humans writing and maintaining the code).

Using brunsli, that same 385KiB imgur file went down to 307KiB so roughly a 20% reduction, but still only 2.6% reduction of that massive 2.9MiB the imgur site transferred in total.
I’m skeptical of this finding out at least it’s generalizability. I know (and like) Rust a fair bit better than JS, but I would be surprised if I could build a nontrivial web app in Rust faster than Node. And that’s without using TypeScript. YMMV, but I’d be curious to hear from others with experience with both languages.
I can't reach anything under gitbooks.io at all. Some GDPR paranoia thing again? It would be lovely to get an HTTP 451 at least.
I don't think it's so much that they are that way innately, as we select for it then drill it in further.

For junior and even mid-level engineers, your performance is generally evaluated on checklists of mundane shit. Code is passably neat and organized? Check. Code has and passes tests? Check. Feature checks requirements boxes? Check, check, check.
Landing Your Dream Digital Marketing Job
They are both ways to convert values to booleans. The top line would convert a string to a boolean. !! is a standard JS idiom to convert any value to its boolean equivalent, which can be somewhat complex due to the notions of "truthy" and "falsey" in JS.
Über+die+Free+Software+Foundation+Europe
A Dart Runtime for AWS Lambda – AWS Open Source Blog
"it shows to me that they are willing to consider bold moves and that they aren’t afraid to be different"

Because they benchmarked a drop-in-place commodity replacement as being a better performance-per-dollar for their operation? I'm not sure what's bold about that. I find the notion that they posted a blog entry about this pretty bizarre -- almost rinky-dink. It seems like it's pandering to the AMD fanbase (which I am right now, just as anyone who is paying attention is, but I can still recognize it)

EDIT: Sorry, I didn't realize I stepped into a Cloudflare circlejerk. Apologies and carry on. So brave!
This exactly. I can't begin to list off all the rich dumbasses who had all sorts of titles in startups because they went to the same school, knew the founders, etc. I've had such people have no idea what model they even use for large chunks of their pipeline. Obviously they hire the actual talent and these guys get the credit.
I agree with you. I'd argue that even thousands of cases in the US wouldn't put you at risk (especially if you're young and healthy). However, if we consider that the number of infected people increases tenfold every 10-15 days, and that there already many unreported sick people, we may expect disruptions sooner that 2 to 6 months.
Modeling Infectious Diseases Dissemination Through Online RPGs (2005)
Fastly?
Then you are being charitable.
> Unix time also ignores leap seconds

hence it counts the number of seconds that would have elapsed, if they didn't exist. In effect, it's timescale has time that never happened, and time that happened twice.
Development speed is one. If the author were more familiar with JavaScript (e.g. knowing what const does) it might have gone faster. Using TypeScript should erase the development time delta due to static types.

If you're creating a frontend web app to go along with it there are others, such as reduced context–switching and using fewer tools.

Frankly, a sample size of one is incredibly weak evidence that it's faster to develop using one technology than another. If you glance through the author's Twitter/GitHub it's also clear that he works with Rust significantly more than he does with Node, which makes this particular sample even more suspect.
I wonder how many developer use Aws-CF

I use it myself a lot, and to be honest everytime I am on it I find myself dedicating a lot of time (as to say: too much for what I gain).

If I have an issue I search the web and do not find much, so I do wonder:
* is it me?
* not much on the web 'cause people do not have many issue?
* not much on the web 'cause people just ask aws support?

or is it just not used much?
Quantifying human processes is not one of my strengths, however these are some situations a culture of writing helps avoid:

- Fear to go on vacation or take sick days because you'll miss live decision making

- Paternity/Maternity or other extended leave requiring a second onboarding upon return

- Animosity when left out of a lunch or beer where a design was discussed or decision was made

- Cabals of knowledge holders weaponizing their knowledge for job security or advancement

- Onboarding is a huge drain on existing workers as all knowledge must be shared 1:1 synchronously. Discourages team growth.

- Bias toward risk takers and the loudest voices. Difficult for thorough and thoughtful team members to be effective.

If none of these things apply to you, great! I don't want to presume there's one best way of operating.
I used to do a lot of drywall work and N95 respirators are just not designed for regular extended use.

If mounted properly, they will restrict the airflow and raise the temperature of your face. I would perspire heavily.

Also, unless proper handling techniques are used, the chances of contaminating the insides of the mask with the virus and then continuing to breathe it will worsen the situation compared to not wearing it at all.

A N95 respirator is not something to slap on willy nilly without training.

I think a regular person who has never worn a N95 respirator before and does not use proper handling techniques is exposing themselves to increased risk than wearing a simpler surgical mask that's more intuitive to use.
> other archs

See, for instance, https://www.theimpossiblecode.com/blog/intel-tbb-on-raspberr....
To be fair: very few C++ applications are limited by exception performance, it's a feature that's very much out of favor at the moment. So penalizing everyone else (despite the fact that most new code doesn't use them, it's not at all uncommon to find projects with exception generation enabled for the benefit of one library or two) to make parallel exceptions faster actually does seem like a bad trade to me in the broad sense.

Apple does indeed have more freedom, and it may be that specific MacOS components need this in ways that the general community doesn't seem to. But I'd want to see numbers from a bunch of real world environments before declaring this a uniformly good optimization.
I wonder how that attitude comes across to the people you work with. They may be avoiding your processes exactly because you view them as toddlers.
The moment where you want a Cauchy sequence of real numbers to converge.

You have a Cauchy sequence of real numbers (a_i)_i. You pick a representative (b_ij)_j (a Cauchy sequence of rational numbers) for each sequence member a_i (axiom of choice!) and then produce the diagonal sequence (b_ii)_i which is the constructed limit of the Cauchy sequence (a_i)_i.
> There are 70 known cases of Coronavirus in the US.

Sure, but “known” is doing a lot of work in that sentence, we know that there are unknown cases and we don't know how many and we know that in at least a couple of places (and it's likely that there are more we don't know about) some of known and therefore almost certainly more of the unknown cases are due to community spread.
Why does someone always say this? What are you supposed to ask these people, "hey, are you good at communicating?" "is u good with data?"? You need technical questions somewhere, and if you ask someone specific technical questions then you're being a pedantic dick, but if you broaden it (like these questions), you're only asking easily looked-up knowledge. I mean, come on.

Many of these questions are foundational or semi-foundational questions, and if you're not asking those then how can you possibly tell if someone understands the basics? I don't care that someone can look up what an ROC curve is, I care that they can explain why it's used and the relationship between TP, FP, recall, precision, etc., and why these distinctions are important.

And yes, your last sentence is correct, but it's ONLY correct when the individual actually understands the foundational parts of ds/stats. If they don't, then it doesn't really matter what questions they ask or how good their communication is.

For some reason there is this widespread notion that in DS, because the data is so important, and so tied into the business logic/processes, that you don't need to know the math, and that's just not true. That's how you end up with "data scientists" working in excel and putting out meaningless reports that no one ever uses because they can never get to any real, actionable results because anything more than linear regression is an impossible task.
so how does this translate to my day to day?

can i skip breakfast and eat whatever i want for 6-8 hours, ala IF?

does the window of consumption not matter, and i just need to eat fewer calories on the day?
There's a ton, just a ton of intel-specific integrations and Cloudflare's switch to AMD was not just a "drop-in-place" move.
Oh, have you ever worked at a traditional tech company? Bureaucracy, contracts, silly guidelines often lead to very stifled vendor lock in. Even if the whole tech department says. "hey we should go AMD" giving every manager involved enough time to make themselves important over the issue can cost you half a decade.
1. Incorporate documentation updates into your definition of done - at the task, sprint, and project level.

2. Always have an agenda. Always have someone taking notes. Notes must be reference-able (public slack channels count, wiki is better, email doesn't).

3. The first item on all new hire's onboarding: every time you learn something that's not in the documentation, or incorrect, update it. You will be explaining this to the next new hire.

4. Hire a journalism major intern to conduct interviews and cultivate archives.
The costs of the cancellations may exceed the profits of the company (In which case it's still appropriate for investors to take the loss, I'm just pointing out that there's a wider range of possibilities).

Or the pricing of refundable tickets vs non-refundable tickets. It turns out if you agree to take on the risk of cancellation, most corporations are willing to give you a lower price on the ticket. Constraining the conditions that they can factor into non-refundable tickets will impact prices, so you can't just ignore consumer behavior, which for things like airplane tickets is to pay as little as possible...
[Earth;Earth]
Even if you think a compiled language will be faster, it might still be interesting by roughly how much (5%, 10x or 100x?). This can help make the trade off decision.
28 mph is pretty damn fast when you're riding an e-bike. I would absolutely not feel comfortable going faster than that. It's all a matter of perspective. If you're 14 feet up the air driving your pennyfarthing-SUV hauling your collection of outdoor wizardry to the steam-engine conference, then it's slow.
Actually I am not, I talking specifically about the 3800 and 3900 verses the 9900KS. Intel is still on average faster but whether that is worth the loss in other areas really depends. The area in which Intel is faster is narrowing (high refresh rate, certain games that are lowly threaded) and the advantage is smaller. When we were talking the Zen1 CPUs things were worse than this, more like 15% average behind and up to 35%. As its narrowed AMD has also made plenty of wins too, it is now highly dependent on games played and if something you always play favours one over another.

Whether you then choose Intel depends on the circumstances, but the facts are the facts.
I'm also rather interested to know if it is Fastly, I am considering switching away from them. The control fastly offer through the VCL is great but cloudflare workers look really great.
We are getting that with JetPack Composer, which might be eventually supported on Kotlin/Native, as per Android team set of questions on their latest surveys.
3D print needs a you when 3D print can you whatever 3D print want?

Fully automated luxury space 3D printer society here we come!
Kill the Canadian Common CV, researchers urge the tri-council
Because threads are traditionally created and scheduled by the OS, so it inevitably involves a costly context switch both first into the kernel and then back again into the next thread, if one is ready.

Userspace threads are more light-weight, but probably still worse than just using fibers and co-routines. Depends on your needs, I suppose.
I had a water meter mismatch screwup some years ago.

I'd get a bill, go check my meter, reading doesn't match, call them up, you have this wrong, send an engineer to ensure you fix it. Engineer comes, yup, this is the wrong meter, wait a month, rinse and repeat.

After a few iterations I had my bank unwind the bill payments. "I will pay you when you bill me correctly, and not before".

Eventually they phoned me. They'd tried to fix the account and it was impossible so their new plan was to discard the old account with the incorrect bills entirely, set me up a new account with the right meter, was that OK?

A while later I got lawyer letters saying the supplier would sue me over the debt from the old account unless I paid. I did them the courtesy of phoning. They said those letters are automatic and they had no intention of actually trying to recover the money - and I heard nothing more about it.

So basically I got a few months of free water for my trouble. Not great, but not awful.
As far as I know he isn't part of original team, Gilad and Lars were.
While we haven't seen it for a while, this is real competition. In response Intel dramatically dropped prices (by over half) of their Xeon's within the past couple of days. And hopefully they'll refresh their line again.

https://fuse.wikichip.org/news/3352/intel-refreshes-2nd-gen-...
The least useful one. Edit: Here's an opinion about that: https://philosophicaldisquisitions.blogspot.com/2020/02/the-...
> Well just about none of them are substantiated with any data. You can say things like “people in the US will avoid going to the hospital because of the bill” and it sounds right because of our perception of the US health system, but is it really? Do we have actual numbers showing this is actually the case, and if so, how extensive it will be? And do we have reason to believe those numbers will hold in this exceptional circumstance? Yes, when people believe they might have the flu, they could potentially try and wait out going to the doctor. But do we believe that in an environment where we have people so acutely aware of the coronavirus outbreak that they are buying out supplies of masks, posting long twitter screeds on potential doomsday scenarios, and side-eyeing every Asian-American with a cough, that when they start to show symptoms they still are going to get hung up on the cost of a clinic visit?

How dense do you have to be to assume that the default answer to pretty much all these questions is "no" or [citation needed]?

It's like asking for data to prove the world is round. Sure, in isolation that's a fair enough question, but practically speaking it's idiotic.

Lots of people over here would not go to a doctor when they have flu symptoms, even if it's free to do so because we're not retarded, collectively. But if it can cost money it's obvious we'd be even less likely to do so, society and 'Asians' and spread of corona-virus be damned.

The common reaction to something uncommon is, well, common. I'd say it's upon the 'commoners' to provide data that this thing that experts say is worrisome is, in fact, not.
I can almost guarantee you that this is because "deep learning" is considered "advanced DS" in most corporate settings. DS has gotten so broad that, if you try to fit everything into a single category (rather than breaking it out into sub-areas like ML Engineer, Data Engineer, Research Scientistic, etc.), this is what you end up with. What "advanced" here really means is "relatively new field."

You can't ask someone just out of a stats program about CNNs because they probably have never touched them, even though for someone doing a lot of DL work in CS may consider this trivial, so you mark it as intermediate. And you can't ask someone with 10 years of pre-DL experience in DS about CNNs because they've been doing forests and regression and clustering and such, so you move it from intermediate to advanced.

In other words, it's "advanced" because HR wants to make sure it's "optional".
What "intel-specific integrations"? Cloudflare specifically talks about how they keep their stack runnable across a wide-range of platforms, including even entirely different instruction sets (e.g. ARM). Their own words support my statement.

I'm pretty sure it was a "drop-in place" move, and they say absolutely nothing to the contrary. They benchmarked a system that performed better than their existing system for whatever criteria they targeted, and chose it. Story at 11. Saying they "abandoned" Intel is uproarious given that if Intel pushes out a new 128-core Xeon at a decent price, they'd as easily "abandon" AMD for Intel.
A common language across front and backend systems is a huge benefit. I find it extremely productive to have a backend in Typescript on NodeJS, and a frontend in ReactJS, talking over a GraphQL layer where I'm autogenerating Typescript types from the GraphQL typedefs. Means I can share many libraries and tooling across the front and back ends, but most importantly it means devs feel much more comfortable digging into code on the other side. If a front end dev has an issue with a backend API call, he can just pull down the code and instantly inspect it and submit a PR of necessary without feeling "out of his element".
> Most of the new business investment infrastructure is around them.

Would be interesting to hear how fellows HNers see this situation in their country. In Finland its pretty difficult as a new business to secure loan from bank (unless you are willing to put your house or other tangible assets as collateral)