dswalter

I think much of what people are objecting to is that, by virtue of its position as an _invite only_ paid service, it provides insight to only the employer party of a two-player game.

It is apparently purpose-built to allow only the employers to arbitrage that extra insight into hiring patterns.

Native emoji support, aesthetically pleasing front-ends, and clear product direction are some of the main positives I see, even if the combination of php on the backend and electron on the frontend aren't the most sophisticated technical components in history.

I prefer decentralized and open things, but a cohesive vision can sometimes provide a better user experience across a more restricted set of functionality than an army of hackers, each solving their own problems.

F-strings alone make the upgrade worth it.

Your idea is along the lines of 'rater reliability' in the field of educational measurement/psychometrics.

Indeed.

There is no mention of this in the document, but the timing suggests there may be a GPDR-related factor. It's hard to get consent from users that haven't touched the service for years.

I've edited my response, but I think you misunderstand the comic.

Bloom filters could do it. https://en.wikipedia.org/wiki/Bloom_filter

It's one of those difficult things. You have to restart and run all to make sure your code is working and your state hasn't gone fudgy, but you also don't want to re-run that cell that took 3 hours to run unless you have to.

My personal best practice is to 'restart and run all' to run the entire thing before I commit it to github. Jupyter git integration is a whole separate bag of worms, as the combination of presentation/code violates some core git assumptions.

Jupyterlab is here. I've been using it basically full-time since August, but it recently went to Beta, so it's ready for use.

The major downside is that it disables JS by default within notebooks, so if you're using Bokeh you'll have to install the jupyterlab extension, but the innovations around files, downloads, views on notebooks, etc. are worth the price of admission.

Is your list of things AWS is notorious for available on your blog somewhere? That's valuable information.

What you describe, buying followers to analyze them, is exactly what Erin Shellman did back in 2015.

http://www.erinshellman.com/bot-or-not/

I don't think it has to be anything more than inertia. They're a massive company that has millions of lines code running in production for a whole chunk of languages. Making a change from python2 to python3 probably seems like more worth than it's worth. It is also a fairly googley problem to think that the way Google does things is automatically superior in all cases. So, since googlers use py2, why shouldn't it be good enough for everyone else?

I appreciate the work that goes into carefully crafting a longform piece like this and usually prefer the full-course meal that this represents instead of the fast-food version you're asking for.

This post is by the author of the dask parallel computing framework, which is written in Python and getting some traction in astronomy circles.

You're looking for the linguistic term 'collocation,' and these are good examples of idiomatic usage of English. Further, words located in proximity with each other is a big part of the distributional hypothesis: "you shall know a word by the company it keeps". This is in turn a key component of how language models like word2vec or GloVe can be effective.

Please call it "Large, a screen-friendly view for Medium".

Michigan is a great location to test self driving cars, because the lake effect makes the temperature fluctuate around freezing. This means we go from icy to wet frequently. It also helps that we get a decent amount of snow, giving us a much wider range of driving conditions than the Bay Area.

It seems most of my comments these days are singing the praises of this book. It should be practically mandatory reading for anyone in the field. It ties concepts together and builds understanding in a way that doesn't rely on specific technologies. I wish it had been written and that I could have done a whole course on this in grad school.

I would argue this question is not really related, but we use PrestoDB (the technology AWS Athena is built using), and it is particularly great for when data becomes too large to fit in a "regular" database. PrestoDB and Apache Impala are the two major open-source surprisingly-fast-distributed-SQL-query-planning-engines. If you pair either of them with a columnar data storage format like Parquet or ORC, you can make analytical workloads work on inconveniently-sized data. AWS Athena abstracts the cluster management for you and runs PrestoDB on spare EC2 instances under the hood.

For anyone who is just passing by, the article attempts to verify some claims from recent VLDB and SIGMOD papers that claim decent* performance on graph algorithms in RDBMs. It's worth reading not only for the technical merits of the discussion, but also because the style of the article is ...feisty.

*for a given definition of decent.

One of the rules that goes with more expensive seeming menus is that you should pretend partial dollars don't exist. THIRTEEN is tolerable. NINE FIFTY is off-putting.

It's such a wonderful book.

Reading it pushed me from thinking in terms of what I had worked with to building systems based on what was needed.

I cannot recommend it highly enough, for pretty much anyone in {frontend, backend, data science, etc}.

This firmly points to his imminent appointment as the next CEO of Uber.

If AWS were to go to a per-minute billing cycle, they would be instantly more price-competitive with Google's offering. Or, to put it the other way around, those leftover minutes form a significant chunk of AWS's profit margin.

Even better than observing yourself is watching other people and trying to figure out what their problems are. If done with empathy, the side benefit is that you further develop abilities you will need if you ever have employees.

I'm of two minds on the use of scrolling as a method of interaction with the page. The term "scrolljacking" has been coined as the negative way to describe this particular style where the page itself is designed to render based on the scroll position. At the same time, I'm completely behind trying to find new and more effective ways of interacting with content.

To me, this page is mostly effective, but I'm on a Macbook Pro, which is probably the best-case viewing experience, but I can't imagine this working well on older mobile devices.

I'm a little surprised, but this seems like a good idea. HTML5 certainly has a brighter present and future than flash, and skipping the OCR stem should save quite a few CPU cycles.

It's a stark contrast from the protect-the-company-from-any-possible-contingency style most employment agreements are drafted in. Lawyers of the caliber Uber can afford don't make this sort of change accidentally.

Almost nobody has been paying as close attention to Uber and Travis Kalanick's goings-on as Sarah Lacy. This makes her "ton of words" a valuable addition to the national dialogue discussing the ramifications of his ouster.