How about all the Dropbox competitors/clones such as OneDrive?

OneDrive fucking sucks. If they didn't advertise it constantly through Windows I don't think anyone would know it exists. Google Drive gets used sometimes, but only slightly more frequently than Dropbox.

In SOC2 compliant orgs it's really not very common to store your files with BigCorp. At least, it's one of the no-nos they try to impress on you pretty early.

> There is no combustion in a kettle either, why does it boil water? Axles and brakes don't combust either.

A kettle sits on top of a flame... which is combustion.

Axles should not be getting hot. You want to get your car checked.

Brakes are intentionally designed to cause as much friction as possible, the opposite of an electric rotor.

This would require open source projects to allow something like that, I can easily see an influx of low quality PRs with vetting burden put on the OSS community rather than the HR tech startup or the recruitment company.

Yes, from startup and Company employer angle it looks perfect. Communities - yes, the burden will rise, but they will benefit anyway: more commits, more developers involved, more new ideas, more popularity, etc.

You can:

https://sales.jetbrains.com/hc/en-gb/articles/207240855-Can-...

You can, if you paid for it yourself. As long as the employer doesn't "pay, reimburse, or in any way finance your personal license".

To elaborate, yes, Jetbrains allows for this, but the employer might not. At my company, personal licensed software are up for individual approval.

Billing by active users is quite common.

With close to zero OSS participation rate you can just pick a real living person and just keep in sync with their LinkedIn.

This only ensures the backdoors are coming from governments that issued the clearances, nothing more. I prefer more competition, at least there is incentive to detect those issues.

It will ensure that my OS doesn't have code from random Gmail accounts. If someone with U.S clearance submits a backdoor, they should either be charged in the U.S, or extradited to somewhere that will charge them. We have no idea who this person is, and even if we did we probably could not hold them accountable.

I have worked with people (well, consultants) hired based on the fact they breathe - I would much rather jump thorough some hoops than to have to work with them ever again.

In the 2022 thread it was mentioned the time limit was either 45min or an hour and not three hours, same as any standard coding interview.

That makes a lot more sense.

The OP, who had already done the task before, took more than an hour to complete it.

Ok, that doesn't bode well for the op.

Note, I haven't used C in 15 years, have never looked at memcached code and in fact the last time I used memcached was before redis even existed.

It took me ~26 mins which included reading the article, googling the memcached repo, downloading all dependencies, compiling a first build, grepping for references to incr and adding mult with support for negative arguments, refactoring the guts of incr into two functions to support the changes, compiling, fixing a few compiler bugs then testing, given a few more minutes I'd probably be able to get it PR ready with a full test suite.