vorador

This must depend on where you live in the city – just yesterday we had massive fog in the morning and at night in the sunset.

Yeah it feels like people forgot about the Sony Rootkit DRM (https://en.wikipedia.org/wiki/Sony_BMG_copy_protection_rootk...) that ended up exploited by malware.

They actually give you fine-grained permissions, down to the single repo access level – but only if you build a Github app. OAuth app don't offer that unfortunately and I assume are considered a bit "legacy".

Yeah, that makes sense!

How would you check that across accounts if you had per-user salts though?

Thank you! Basically, it gives you your own private GitHub repo to do the takehome. Once the time is up, you lose access to it and the reviewer is notified that it's ready to review.

Yeah that's fair! As a candidate I've enjoyed takehomes in the past because I was able to dip out easily if the project was clearly not doable in the alloted time. It's a bit harder to pull that off in an in-person interview.

Re: the takehomes that never take two hours, I think (but I'm a little biased) that Fairlane solves that – given there's a hard limit on how long the repo is available, a company that makes a takehome that takes way too much time would notice because very few of their candidates would complete it.

Hi Connor! Thank you! I haven't considered universities – to be honest I'm focusing on making the interviewing flow as smooth as possible and from what I've heard proctoring tools are pretty intrusive (they want you to install their app, have your camera on at all times, etc.) but I'd be happy to change my mind!

Thank you! To answer your question about building support for later stages – possibly? I chose to focus on what brought me the most value, screening candidates early in the process. I haven't heard of companies but basing their whole interview process on a takehome because usually they want to get to know the candidate but I'd be happy to change my mind!

Thank you for the kind words!

I think it depends. When I was a hiring manager I offered candidates the choice between takehomes and a regular interview and about 50% took the takehome.

The key to a good takehome was to not be too long and respect the candidates' time – just as it'd be for an in-person interview. I'm not too worried about people cheating, usually they get caught later in the process (e.g during the design interview).

Yeah that's a good point! At most of the companies I've worked at we came up with our own coding problem so we just needed the infrastructure to run the takehome. I'll take a note of this and see if it comes up in customer feedback!

Hi HN – I’m Karim, the creator of Fairlane. I built this because as a hiring manager I found out the hard way that take-home projects were way better than any other way to screen candidates.

I know some people here are very against take-home projects but believe me, lots of candidates love them because they remove the stress of having to code live in front of a stranger (me included!).

As a hiring manager, take-homes also let me take more chances on candidates since I didn’t have to convince one of my colleagues to give them a phone screen. The only issue with takehomes is that they’re pretty intensive logistically – there's a lot of emailing back and forth with the candidate to find an appropriate time, following up to ask for the source code, etc.

Please let me know if you have any questions – AMA here and you can also reach out by email at karim@fairlane.io!

Genuinely curious, what's so bad about the original code that it adds an attack vector?

Would love to hear a bit about what got you interested in journalism and in lambda school – thank you!

Genuine question, what do we get out of adopting IPv6? I remember being told for years that we'd run out of IP addresses (which hasn't happened thanks to NAT). What are the advantages of IPv6 from a practical standpoint?

Sorry, I'm using the OPs parlance here – by PWA I think he means "JS apps that use advanced browser APIs".

The typical concern is that a phisher will use to make a page that looks like Google's sign-in page and display it in fullscreen mode. This would let them collect credentials while mirroring the input in a real form that'd be filled in the background.

If you look at the features that Apple lags on adding support for, usually it's either because:

1. they can be abused (PWAs)

2. are complex to implement (WebRTC – for the longest time the recommendation in the WebRTC community if you wanted to build a C++ app was to bundle a good chunk of Chrome's libraries)

3. or could be bad for battery (web workers)

So yeah, it makes some developers' jobs harder but generally there's a good reason for punting features.

Nylas | https://nylas.com/ | San Francisco, CA (Soma) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 20K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts.

You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a small team

* We have a paid vacation policy & value personal responsibility and ownership.

Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too.

Apply at https://nylas.com/jobs or ping me directly (peter@nylas). We're a diverse team, and encourage applications from all backgrounds.

I made a "Show HN" post a while ago (https://news.ycombinator.com/item?id=6681238), found my current job thanks to it (https://nylas.com --- btw we're hiring) and moved to the US.

Definitely life changing and I'm very grateful for it.

Nylas | https://nylas.com/ | San Francisco, CA (Soma) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 16K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts.

You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1 We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a small team

* We have a paid vacation policy & value personal responsibility and ownership.

Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too.

Apply at https://nylas.com/jobs or ping me directly (karim@nylas). We're a diverse team, and encourage applications from all backgrounds.

Nylas | https://nylas.com/ | San Francisco, CA (Soma) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 16K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts.

You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a small team

* We have a paid vacation policy & value personal responsibility and ownership.

Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too.

Apply at https://nylas.com/jobs or ping me directly (karim@nylas). We're a diverse team, and encourage applications from all backgrounds.

Is it possible for a person under an H-1B visa to have a money-generating side-project? I've read that it was absolutely illegal but I'd like to have an actual lawyer's opinion.

Thanks!

Nylas | https://nylas.com/ | San Francisco, CA (Soma) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 16K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts. You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a small team

* We have a paid vacation policy & value personal responsibility and ownership.

Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too

Apply at https://nylas.com/jobs or ping me directly (karim@nylas). We're a diverse team, and encourage applications from all backgrounds.

As much as I'd like everybody to be using Python 3, the truth is there's not a lot of immediate benefits, which is why 85% of Python users are still using 2.x.

The next few months are going to be interesting.

Nylas | https://nylas.com/ | San Francisco, CA (Soma) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated over 16K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts. You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, we're for you. :)

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a small team * We have a paid vacation policy & value personal responsibility and ownership. Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too

Apply at https://nylas.com/jobs or ping me directly (karim@nylas). We're a diverse team, and encourage applications from all backgrounds.

But isn't one of Slack's main ideas that groupchat should be colorful and fun? Adding support for animated gifs and emoji is an important design choice.

Nylas | https://nylas.com/ | San Francisco, CA (Mission) | Frontend (JS), Backend (Systems+Ops)

Hi! We're Nylas. We build N1, the extensible, open source email client, and the infrastructure powering it. We're looking for fronted application engineers (React, Electron, JS), designers, backend systems engineers, & infrastructure/operations engineers.

We recently launched N1, have accumulated 15K stars on GitHub, and are looking for core application engineers to design an extensible platform around email, calendar, and contacts. You'll not only use modern web tech to build a better email experience, you'll design the developer platform to power the next generation of email apps. See more about N1 here: https://nylas.com/N1 & code: https://github.com/nylas/N1

We have more data for a single user than in most startups' entire database. We're scaling heavily and if you have experience with automated deployments, debugging running systems, release engineering, and on-call schedules, but are still comfortable writing code, we're for you. :)

We take pride in the diverse culture we've built and are looking for more than raw technical talent: https://www.youtube.com/watch?v=z7sHc4P4zPg

== We're particularly looking for folks who ==

* Take personal pride in their work and value autonomy and ownership

* Want the chance to step up and lead a team

* Put the work before ego. We've got each others' backs, and we want you to be with us on that

== A bit more about us ==

* Our backend is built on Python, Flask, gevent, nginx, MySQL, AWS, and Debian. We've been careful to keep our architecture componentized.

* N1 uses javascript (ES6), React, Flux, SQL for offline caching, Electron, and no jQuery

* Tons of our code is open source. Check it out: https://github.com/nylas

* We're a team of 20 (12 engineers, 3 engineering interns)

* We have a paid vacation policy & value personal responsibility and ownership. Benefits include free Lyft to & from the office, full health, dental, vision, and lunch every day. Some remote work / work-from-home is OK too

Apply at https://nylas.com/jobs or ping me directly (spang@nylas). I'm Christine, one of our co-founders. We're a diverse team, and encourage applications from all backgrounds.

It's a pretty simple idea actually --- tie your IoT device to a backend service and never worry about competitors stealing your UI/design.

Case in point: the Nest Dropcam uses backend services to do image detection and alerting, two things which require skills hardware manufacturers often don't have.

Interesting article but I think it has a critical flaw — not all startups are in the consumer space. Of course, there’s not going to be another Facebook for the next couple years at least, but another Stripe — maybe?