Uber is worldwide - I’ve used it on 4 continents. I actually signed up for it when in South Africa.
Considering they sold their business to Grab, I think you could safely say Uber+Grab are as close to a global service as you can get, and probably represents a significant fraction (though maybe not 50%+) of the global market
I've been thinking a lot about this one, and it gets a ton of help in the fact that Bill Hader is actually good at facial impressions, and that's what really sells it.
For my fiancée, she deleted her facebook a long time ago, and she never paid attention to the username. We just made a best attempt at guessing the “user name”
I'd like to see an MFA-version of Kerberos/kinit, and a PAM module that checks for ticket revocation on login.
That's not so different from BeyondCorp and Uber's model.
Alternatively, some kind of OpenID Connect init (oidcinit) to get a JWT and then a PAM module like the kerberos one (which also checks the JWT's Key Id for revocation on authentication)
If you are just running a web app, then this is the correct answer. If your business is in your database, you employ data analysts and want to gleam some additional insights from your database, then it might be worth a look, though most people who chose MySQL did so because they were building a web applications and don't employ analysts.
A workflow language is only as good as it’s engine.
Nextflow was mentioned. I think what most people want is probably closer to Airflow, although it takes some
time getting it up to production in a cloud environment (there is astronomer.io and a GCP product).
HTCondor via DAGMan has existed a long time, and there’s even engines built on that (Pegasus, Wings).
There’s Swift (http://swift-lang.org/main/) and it’s successor Parsl. Cray has Chapel. These are a bit different, in that they are more like a distributed computer program. Of course, so is Julia, but built into these languages is the assumption you can be using unreliable, in some way, computing. Makeflow and GNU Parallel are closer to this category too.
Then there’s Beam, but that’s dataflow.
The crappy thing about this is it’s hard to understand when to use a solution and when to not use a solution. Why are there so many solutions? Because there’s a ton of different needs, and a lot
of these focus on a few in particular:
Latency
Scalability or workers
Dynamic Scalability of workers
Throughput
Polyglot
Integration with existing Schedulers
Workflow Code Management (container support)
Maintainability of very large DAGs
Testability of DAGs/Development support
Execution Management support/Web APIs
Error recovery (especially for long running workflows)
Sites hosted behind cloudflare have been down for me for 8 days now. It seems like there’s something up with TLS connections.
As a user, there is no easy recourse. I had to create an account on dash.cloudflare.com, which I was able to do after SSH tunneling to another server and doing a SOCKS proxy. This because they don’t accept emails to [email protected] unless you have created an account.
Once you open a ticket, you are doing so from a free account, because you are not the user. You are not prioritized.
I have no idea why I can’t access tons of sites right now, but it’s fucking frustrating. I’m in Chile and all the VPNs I can use are in the US so that makes for a terrible browsing experience.
This has really slowed me down this week. If I didn’t have a VPN, like most people in Chile, I’m sure a small part of the internet just be broken.
Most my adult life I’ve used Ivory (usually bars), or Dr Bronners (liquid) with a handful of other things at random. The only wash I like besides those would be the Kiehl’s Musk wash, but I’m slightly interested in abandoning soap altogether except for the nasty bits.
Certainly it's not fair to the employees. Certainly they probably didn't expect to get 10 men and 0 women in their current makeup. There may be no intentional guilt, but it's also not possible to know how they ended up with the makeup they have, 10 to 0, though it was probably incremental and without reflection on the makeup of the team along the way. Assuredly it probably wasn't malicious, but it's also like the people doing the hiring didn't reflect along the way - "hey, we've got 9 engineers and we need 10 and we are going to hire _another_ man for this role".
It's clear they (in this case the company) want to fix this in some way, as instructions "from on high" came down. Again company may or may not know how they got there. The company may also be failing to attract clients who want to vote with their dollars for a diverse company - so there could be a valid business case for this. Or not, maybe they just don't want a company with all dudes.
The original post was pointing out an unfair hiring practice due to this policy. I'm pointing out there is an alternative equitable hiring practice which actually leads to a fairer hiring practice for men and doesn't necessarily involve affirmative action, but that involves starting from scratch again (nobody said you'd necessarily lose your job - they could also easily make those positions available). Obviously this is not a tenable thought experiment, especially in academia thanks to tenure, so that's why we have these systems which, on the surface, may appear to discriminate against men. That said, many people interview for their current jobs in corporate restructurings all the time. That's probably not fair either, but it's accepted practice in the US.
they could always admit their ratios are way off, fire everybody, and create 10 new backend job applications - 5 of which will go to men and 5 to women, so that way their hiring is more fair to both men and women.
I’ve spent some time in Western Oklahoma on and off the last 10 years. 10 years ago there was almost nothing. 5 years ago they started popping up, 2 years ago it started to just be everywhere. In other communities that are traditionally dependent on the oil industry the economies have been touch and go, but in places with wind (like western Oklahoma and Texas), it’s almost the ultimate hedge.