kevincennis

They also used the term "subfield".

I forget who it was (maybe George Hotz) that said something to the effect of "All bad drivers are bad in different ways, but all good drivers are good in the same way".

The point being made was basically that in the aggregate you can more or less generalize to something like "the tall part of the bell curve is good driving and everything on the tails should be ignored".

Since learning happens in aggregate (individual cars don't learn – they simply feed data back to the mothership), your example of a single car errantly turning the wheel to adjust the radio would fall into the "bad in different ways" bucket and it would be ignored.

Starry Internet | Software Engineer (Node.js) | Boston, MA | Full-Time | REMOTE Marketing blurb:

We love the internet, but not the complicated plans, bloated bundles, and poor service. So we reinvented it from top to bottom. Starry is a different kind of internet service. We use next-generation technology to beam nothing but lightning-fast internet. And we’ve designed everything around the simple goal of making your internet life happier.

Less Marketing-y blurb:

The Cloud Services team works on our share of standard JS/Node stuff, like REST APIs. But we also do a ton of interesting work in areas like distributed systems, network monitoring and observability, geocoding, etc. Stack is mostly Node + Mongo on AWS, but we also have some Redis, Elasticsearch, Dynamo, etc.

Job Link:

https://starry.com/careers/5615602002

If Node isn't your thing, we're hiring for a ton of other roles as well: https://starry.com/careers

Starry Internet | Backend Engineer (Node.js) | Boston, MA | Full-time | REMOTE

Marketing blurb:

We love the internet, but not the complicated plans, bloated bundles, and poor service. So we reinvented it from top to bottom. Starry is a different kind of internet service. We use next-generation technology to beam nothing but lightning-fast internet. And we’ve designed everything around the simple goal of making your internet life happier.

Less Marketing-y blurb:

The Cloud Services team works on our share of standard JS/Node stuff, like REST APIs. But we also do a ton of interesting work in areas like distributed systems, network monitoring and observability, geocoding, etc. Stack is mostly Node + Mongo on AWS, but we also have some Redis, Elasticsearch, Dynamo, etc.

Job Link:

https://starry.com/careers/5198297002

Can you expand on this?

Starry Internet | Software Engineers | Boston, MA | Full-time | ONSITE

Marketing blurb:

We love the internet, but not the complicated plans, bloated bundles, and poor service. So we reinvented it from top to bottom. Starry is a different kind of internet service. We use next-generation technology to beam nothing but lightning-fast internet. And we’ve designed everything around the simple goal of making your internet life happier.

Roles:

We're hiring for a ton of different software roles. Node.js, Rust, Swift, C++, and Python – across teams focused on cloud, firmware, mobile, testing, etc. Check out https://starry.com/careers or shoot me an email at kevin@starry.com.

I'm a little surprised to have not seen any mention of the Speech Synthesis API (https://caniuse.com/#feat=speech-synthesis).

It's supported almost everywhere that the Web Audio API is.

I used to work at Aereo.

I fully expect Locast to lose, but this truly is an A+ troll. Really warms my heart.

Want a sandbox that's big enough to use as an actual integration/staging environment rather than just a little toy "Developer Hub"? 15% of your annual contract.

The problem with this is that it requires really successful artists to work for far less than the value they create, which they won't – because they know they could make far more money independently.

And without the top performers subsidizing the salaries of everyone else, the whole thing falls apart.

No worries. When we first launched we were only in NYC, so for a while it was just one facility. But we kept adding them in each new market.

We definitely did have our antennas in the same market (DMA) as our subscribers, and went to great lengths to prevent customers from streaming when outside of their home market, as we felt that approach best complied with existing law.

Former Aereo employee here. A couple things:

1. Getting sued actually isn't as fun as it sounds

2. I love this so much

Locast is trolling in the best possible sense of the word.

We used these at Aereo:

https://en.wikipedia.org/wiki/Electrically_small_antenna

I've actually had decent luck getting Stripe to un-blacklist subscribers that they incorrectly identified as fraudsters.

But it takes a ton of back-and-forth with support reps who generally don't even know or believe you that blacklisting exists (sometimes just an email address, not a specific card, was blocked) – and in one case we didn't get a resolution until the customer got the CA Attorney General to write Stripe's general counsel.

As a New England resident with a very old detached garage, I, too, wish my Tesla was not so wide. Every single time I park in my garage (which can only be accomplished in reverse, while turning about 30°) it's mildly terrifying.

That's true, of course. But it's much harder to actively cancel higher frequencies. This is why noise cancelling works brilliantly on an airplane (relatively low frequency background noise) but it does almost nothing to filter out the sounds of conversations around you.

> Autonomy means the data scientists own that code as well. All the way into production.

This does not strike me as a great idea.

    Test.prototype.fail = Test.prototype.pass

Dying.

I have a little 6-speed BMW right now that’s so fun to drive around, but I think my next car will probably be a Model 3.

Shifting is fun when the roads aren’t a disaster, but between traffic and the fact that ICEs are pretty much untenable in the long-term, it’s hard to justify buying another manual. Plus, the options for new stick shift cars seem to be dwindling every year anyway.

I’d like to be able to continue driving a standard, but it just makes less and less sense (for me, at least).

The 2018 numbers are YTD though. Both cities seem like they're on track to do as well or better than they did in 2017 assuming that funding doesn't tend to be significantly front-loaded toward the beginning of the year (which might be the case – I honestly don't know).

Mapbox also offers geocoding and navigation, which are quite a bit more difficult than just setting up a server that can host OSM tiles. Obviously, if all you need are maps, that's fine. But if you need maps with search, which I suspect most people do, rolling your own is tougher (though projects like pelias are pretty good).

That’s literally true, but on balance it’s way easier to use curl for GET requests to a REST API than it is to use curl for GraphQL queries. At least if we’re talking about “let me curl that route real quick to see what the data looks like”.

I still have a handful of the antennas in a closet somewhere. They really were about the size of a dime.

A bunch of us started a new company called Starry after the Aereo decision, and we're still doing some crazy RF stuff (although this time around, it's as a WISP rather than TV).

SCOTUS is weird.

I was an early employee of Aereo (the case mentioned in the article where Breyer went on about phonograph record stores), and I worked there when we were sued and ultimately won the appeal in the 2nd circuit, when we won in 1st circuit, when SCOTUS granted cert, and ultimately when we lost.

One of the strangest parts is that you have no idea when they'll issue your decision. They give a certain amount of advance notice that they'll be issuing decisions on certain days, but you don't actually know which decisions.

For a couple months after oral arguments, we had probably half a dozen mornings on pins and needles while we'd wait to find out if they're going to decide our case. It was really, really hard to concentrate on getting anything done.

Another fun fact: Clarence Thomas has only asked 1 question during oral arguments in something like 10 years.

Can you explain what you mean by "pretty much all the modern web development is basically PHP-like"?

I'm not necessarily disagreeing. I just don't really get what you mean by that.

Proxies can also be really helpful for unit tests.

Obviously you have things like sinon for stubbing out methods, but they do have to modify the original object, which I don’t think anybody loves.

But you can also wrap your object in a Proxy with handlers that stub certain methods.

You can also use proxies to implement validation and observability on objects. Here’s a very minimal example of a sort of Backbone-esque Model class with proxies: https://gist.github.com/kevincennis/25ba31b2e9f9c8b7a34047ba...

Yeah, agreed. I think I run into more issues in Safari than anywhere else these days.

It's always some weird rendering bug that mysteriously vanishes with the old null transform trick.

I honestly wonder if this is real, or the whole story.

How many websites are actually doing things that require a meaningful amount of extra effort to support Firefox if it already works in Chrome/Safari?

For most websites, cross-browser testing is almost an afterthought these days.