bgentry

Can’t imagine why anybody would want to leave.

Options at startups are basically worth nothing, unless/until the company becomes a breakout success. Even then you generally can’t sell them unless there is an IPO or you do a second market deal. These really are a lot like a lottery ticket.

I won’t get into all the ways options can be worthless even if the company does well enough to IPO, and you actually managed to exercise / keep the shares you vested.

Also, some later stage non-public startups issue RSUs instead of options. These too are closer to a lottery ticket.

Easier said than done in the Bay Area without 2 good salaries, especially for those with kids.

Bonuses are often structured as a % of your base salary based upon your rank. More senior engineers will get an extra 10-25% each year essentially automatically.

This is separate from RSUs, which vary a lot more widely. Their value is especially dependent upon company stock performance.

RSUs and bonuses at established companies will easily double your take home pay.

Even the salary figures themselves look low and are probably heavily skewed by an overrepresentation of underpaying startups. My base salary ~4 years ago was in the 90th percentile according to this. It’s unlikely I was among the 10% highest paid Bay Area engineers at that time.

Don’t settle for a mediocre salary in an area with absurdly high cost of living. Don’t be satisfied with these averages. Funded startups will pay more if they need to.

The amendment provides that certain employees who receive stock options or restricted stock units as compensation for the performance of services and later exercise such options or units may elect to defer recognition of income for up to 5 years, if the corporation’s stock is not publicly traded.

Perhaps the amendment itself makes this clear, but it sounds like this does not in any way affect option exercise timelines. It sounds like this just lets you defer recognition of the income resulting from an exercise.

http://bakerxchange.com/rv/ff0034eed7a7d447f644f491d94caddcb...

And because this screen has such a wide aspect ratio, in most cases you can zoom out and only have black bars on the notch side and opposite side (left & right when in landscape mode).

That being said, I do find the designs that “embrace the notch” (especially in landscape) repulsive. I’d much prefer if that area just stayed dark to blend in with the notch.

Excited to try out 2.0 soon!

Unfortunately it seems like the core API docs are still woefully out of date and full of broken links: http://dev.apollodata.com/core/

Despite that, my experience with Apollo in general has been good. I maintain the Ember addon for it, and I find I'm much happier and more productive with Apollo Client + GraphQL than I ever was using ember-data + JSON API.

https://github.com/bgentry/ember-apollo-client

Also, are there any downsides or missing features of the add-on version compared to the extension version?

There are plenty of cases where the LIMIT/OFFSET behavior is not great. More boring example: you’re displaying a paginated list of financial transactions and you don’t want duplicates to appear if the list gets updated. Or any kind of audit log. Or an event feed, or infinite scroll.

https://github.com/chanks/sequel-seek-pagination

I used it just this week to write a Relay Connection paginator for graphql-ruby and Sequel/Postgres. It uses keyset pagination to reliably avoid skipping items and maintain consistent query times.

Backwards pagination was a bit tricky since that’s not natively supported by sequel-seek-pagination. Basically I had to reverse the list order and then filter with the cursor values to get the last N items in a subquery, then reverse that list again to get back the desired sort order.

https://github.com/rmosolgo/graphql-ruby/pull/1014

Is that actually true? I’d heard that Apple had reversion instructions for those running the High Sierra beats on a system with a Fusion Drive, which they dropped support for in the final release.

Just be sure to run your enqueueing process as a singleton, or each worker would be redundantly enqueueing lots of jobs. This can be guarded with a session advisory lock or a redis lock.

Knowing that this easy transition exists makes me even more confident in just using Que and not adding another service dependency (like Redis) until it’s really needed.

Also, what an impressive project to have on the resume as a college intern. I don't think many interns get to tackle something so meaningful.

https://developer.apple.com/homekit/specification/

Edit: also confirmed this in the WWDC video at 28:20 https://developer.apple.com/videos/play/wwdc2017/705/?time=1...

And let's say you come up with a really cool prototype? And now, you want to develop a HomeKit accessory for commercial sale. You need to join the Apple MFi Program. You need to join the Apple MFi Program and go through self-certification before you can begin your manufacturing or sale of your accessories. And this is really exciting.

At WWDC in May, Apple quietly announced that it planned to relax some of those restrictions. The biggest change was the introduction of software-based authentication. In other words, you won’t have to replace your stuff to make it Apple-compatible going forward, and you’ll get HomeKit’s lauded security thrown in for free — provided the device maker actually goes in and implements it.

The linked HomeKit FAQ says that software authentication is only for non-commercial devices, and that commercial/shipping products are still required to use the hardware authentication chip. So Apple's own docs clearly refute the notion that non-HomeKit hardware can receive a software update to become HomeKit compatible.

Ikea Tradfri is an exception here. They plan to add HomeKit support via a software update, but they do in fact already ship their hardware with an MFI HomeKit authentication chip.

It is possible to add a software authenticated device to a HomeKit network, though you get warned when doing so. This is not new (though official support for it is). But it still sounds like commercial products can't just add HomeKit compatibility via software without breaking Apple's terms.

There are many examples of NSA and Five Eyes spying that have absolutely nothing to do with terrorism (though afaik none specific to copyright infringement). I linked to a handful in this other comment: https://news.ycombinator.com/item?id=14907667

Off the top of my head:

- NSA surveillance of the semi-public Brazilian oil company Petrobras: http://g1.globo.com/fantastico/noticia/2013/09/nsa-documents...

- NSA tapped the phone of German Chancellor Angela Merkel: http://www.spiegel.de/international/world/merkel-calls-obama...

- NSA spying of Indian diplomats to uncover details about their nuclear and space programs: http://www.thehindu.com/news/national/india-among-top-target...

This article is a decent compilation of Snowden-related stories from the first year after his leaks: http://www.businessinsider.com/snowden-leaks-timeline-2016-9

I know they spent a couple years getting to this point, but I can really appreciate the quick, well-designed iOS app, and the native, non-Chromium / non-Electron Mac app that only uses 35MB of RAM and has no noticeable idle CPU draw. It's such a stark contrast with Slack and most of today's pseudo-native apps.

Impressive launch!