burnout1540

Sounds interesting. Is retail the target customer? Where do you source your data from?

There are only about 45,000 coal miners in the entire US. That's a tiny number.

If ICE arrested you, would it be fair for them to deport you before you were able to present evidence that you're a citizen?

Due process doesn't mean a full trial. At its most fundamental level, it simply means having a fair process. Of course there's a whole set of case law behind determining what is fair, and a lot of that depends on the type and severity of the case.

But what happens if all that fairness and case law is ignored? Without due process (such as a hearing with a judge), how do you prove you're a citizen? Who do you even present your evidence to? How can you even gather your evidence if you're locked away in a cell?

When people argue for due process (which is a constitutional right), this is what they're arguing for. They're arguing that a single government employee should not be able to deport them without a fair process. Which is a constitutional right for all people (not just citizens), per the 14th amendment.

Check out gosimplelab.com

HelloSign (https://www.hellosign.com) | San Francisco, CA | Full-time | Onsite

We're hiring front-end, full-stack, and back-end developers of all experience levels to work on our two flagship products, HelloSign and HelloWorks. Our mission is to reduce the friction associated with contracts and complex document workflows.

HelloSign is built with Symfony PHP and HelloWorks is built in Elixir. Both primarily leverage React on the front-end.

Our typical hiring process is quick, involving a phone screen and one on-site interview.

More info about the just launched HelloWorks (Elixir & React/Redux) here: * https://www.hellosign.com/products/helloworks https://www.hellosign.com/blog/the-new-web-elixir-phoenix-ch...

We're also hiring Data Engineers, Sales Engineers, and more. Job listings: https://jobs.lever.co/hellosign

HelloSign (https://www.hellosign.com) | San Francisco, CA | Full-time | Onsite

We're hiring front-end, full-stack, and back-end developers of all experience levels to work on our two flagship products, HelloSign and HelloWorks. Our mission is to reduce the friction associated with contracts and complex document workflows.

HelloSign is built with Symfony PHP and HelloWorks is built in Elixir. Both primarily leverage React on the front-end.

Our typical hiring process is quick, involving a phone screen and one on-site interview.

More info about the just launched HelloWorks (Elixir & React/Redux) here: * https://www.hellosign.com/products/helloworks * http://blog.hellosign.com/the-new-web-elixir-phoenix-channel....

We're also hiring Data Engineers, QA Automation Engineers, and more.

Job listings: https://jobs.lever.co/hellosign

HelloSign (https://www.hellosign.com) | San Francisco, CA | Full-time | Onsite

We're hiring developers of all experience levels to work on our two flagship products, HelloSign and HelloWorks. Our mission is to reduce the friction associated with contracts and complex document workflows.

HelloSign is built with Symfony PHP and HelloWorks is built in Elixir. Both primarily leverage React on the front-end.

Our typical hiring process is quick, involving a phone screen and one on-site interview.

More info about the just launched HelloWorks (Elixir & React/Redux) here: * https://www.hellosign.com/products/helloworks * http://blog.hellosign.com/the-new-web-elixir-phoenix-channel....

Job listings: https://jobs.lever.co/hellosign

HelloSign (https://www.hellosign.com) | San Francisco, CA | Full-time | Onsite

We're hiring experienced developers to work on our two flagship products, HelloSign and HelloWorks. We have open front-end and full-stack positions (PHP or Elixir).

Our typical hiring process is quick, involving a phone screen and one on-site interview.

More info about the just launched HelloWorks (Elixir & React/Redux) here: * https://www.hellosign.com/products/helloworks

* http://blog.hellosign.com/the-new-web-elixir-phoenix-channel...

Job listings: https://jobs.lever.co/hellosign

HelloSign (https://www.hellosign.com) | San Francisco, CA | Full-time | Onsite

We're hiring experienced developers to work on our two flagship products, HelloSign and HelloWorks. We have open front-end and full-stack positions (PHP or Elixir).

Our typical hiring process is quick, involving a phone screen and two on-site interviews.

More info about the just launched HelloWorks (Elixir & React/Redux) here: * https://www.hellosign.com/products/helloworks * http://blog.hellosign.com/the-new-web-elixir-phoenix-channel...

Job listings: https://jobs.lever.co/hellosign

Are you using DynamoDB Streams at all? I've been toying the idea of using DynamoDB as an event store and having other services listen to a table's stream, allowing them to update caches/views (the read-side of CQRS), report analytics, perform asynchronous tasks, etc.

HelloSign (YC W11) | San Francisco (Market St.) | ONSITE

HelloSign is a leading provider of eSignatures, allowing users to sign documents when, where, and how they want. HelloSign has seen tremendous growth over the past two years, primarily through word-of-mouth, and we are now focusing on building the future of legal agreements. We are funded by some of the top investors in the valley, including Y Combinator, Greylock, Google Ventures, and US Venture Partners.

We're currently hiring for the following positions:

Elixir Engineer - http://grnh.se/igt6y8 Sr. Security Engineer - http://grnh.se/uimyt2 Security & Compliance Program Manager - http://grnh.se/g4l3to

HelloSign (YC W11) | San Francisco (Market St.) | ONSITE

HelloSign is a leading provider of eSignatures, allowing users to sign documents when, where, and how they want. We’ve seen tremendous growth and now we're taking it to the next level by launching a fully featured API that allows clients to integrate our eSignature functionality directly into their own website. We've got a great culture focused around active transparency, collaboration, and building product that makes our users awesome.

We're currently hiring for the following positions:

API Product Manager - http://grnh.se/bay1rw

Director of Information Security - http://grnh.se/7fsvmy

API Tech Support Rep - http://grnh.se/yvks5l

Full-Stack Engineer - http://grnh.se/4y7gbh (we're also looking for a more Sr. back-end developer but haven't posted the job yet, please apply through this same link)

How much of this could be accomplished using something like Mixpanel? Honestly curious.

I know a true ETL solution like this will be more powerful and flexible, but how do you decide when it's worth the investment? Are there key use-cases or reports that only this type of solution can provide? Is the main issue with external analytics (like Mixpanel) that you need to know what data to collect before you can report on it?

HelloSign - https://www.hellosign.com - San Francisco, CA

=============

HelloSign is a leading provider of eSignatures, allowing users to sign documents when, where, and how they want. We've seen tremendous growth and now we're taking it to the next level by launching a fully featured API that allows clients to integrate our eSignature functionality directly into their own website. We're just shy of 40 people and are hiring!

The top 3 technical positions we're currently hiring for are:

Lead QA Engineer - https://boards.greenhouse.io/hellosign/jobs/69005#.VW0W12RVi...

API Technical Support Rep - https://boards.greenhouse.io/hellosign/jobs/53830#.VW0W1mRVi...

Software Engineer - https://boards.greenhouse.io/hellosign/jobs/35126#.VW0W12RVi...

That's a fair point. The one constant in a startup is change. It may be that in the future we'll have developers only doing front-line support for beta features of our API.

Regarding flow, we don't have all of the developers doing support all of the time. We have one developer doing support at a time and rotate each week. This protects the rest of the team from having their flow I interrupted.

Our approach may not be scalable (and may not fit into your worldview) but having our developers do API support for us serves two important purposes:

1. Giving our clients the best possible technical support

2. Making our developers feel the pain (and joy!) of clients using what they built. I can't think of a better way to motivate developers to fix what's sub-optimal, share in the success of a job well done, and come up with new ideas to help our customers.

We're not alone in this strategy:

http://www.helpscout.net/blog/customer-pain/

https://gettingreal.37signals.com/ch14_Feel_The_Pain.php

Co-founder and CTO of HelloSign here.

Sorry to hear that OP's bug reports weren't taken seriously. Good tech support is a must for mission critical APIs.

At HelloSign we take great pride in our API and our tech support. Rather than outsource support or rely on less technical people, we have our developers directly support the API they built. So when you give our API a try, I encourage you to check in with one of our developers by visiting our public HipChat room (https://www.hipchat.com/gq4BMFKt1) or emailing them directly at apisupport@hellosign.com. And that's available to all customers no matter what pricing tier they’re on (including free).

Take a look at our API documentation here: https://www.hellosign.com/api/documentation

We’ve had a lot of API customers switch over to us from EchoSign’s API due to reliability issues. I have a lot of respect for EchoSign and their original CEO Jason Lemkin, but I do think the API was an afterthought for them. At HelloSign we think it’s the future and are committed to having the best-in-class API.

I also wanted to touch on your point about wanting to work with "a company with a soul". This is something I also look at when making buying decisions. I’ve found a company's Glassdoor reviews to be an effective barometer of how well a company treats its employees and, by extension, how its employees treat the customers. That’s one (imperfect) way to measure "soul".

Happy to answer any questions anyone on HN might have.

That sounds like registered users, which may be completely different than active users. The number of registered users tells you very little without also knowing the number of active and/or concurrent users and what type of activity they're doing.

I'm missing something.

  shouldComponentUpdate: function(nextProps) {
      return nextProps.tile.active !== this.props.tile.active;  
  }

  "That means that nextProps.tile and this.props.tile are pointing at the exact same object, so they will always be equal."

If this is the case, shouldComponentUpdate would always return false and he should not see any of the components update. But he's seeing ALL of them update.

Here are some other code review checklists, for comparison:

https://wiki.apache.org/hadoop/CodeReviewChecklist

https://gist.github.com/bwest87/10049924

http://www.mindfiresolutions.com/Code-Review-Checklist-238.p...

Some more info here: https://consul.io/intro/vs/smartstack.html

HelloSign - San Francisco, CA - http://www.hellosign.com

We're the easiest way to sign documents online

Us:

- Real revenue

- Real backing from top venture firms (not announced)

- Growing fast and expanding our team from 30 to 40

We're looking for:

- Software Developers (Full-stack)

- A Sr. Front-end Engineer (React, SASS)

- DevOps

https://www.hellosign.com/info/jobs

Pebble.

https://www.kickstarter.com/projects/597507018/pebble-e-pape...

The phrasing is misleading. The add-on cannot run without you present. In order to fetch the document without any formatting problems we needed to use ScriptService which causes this permissions prompt.

See related: https://code.google.com/p/google-apps-script-issues/issues/d...

Yes!

Add-ons have been released: https://developers.google.com/apps-script/add-ons/

Not only is it down, but it's redirecting everyone who visits a site with FB Connect on it to this error page. For example: http://www.economist.com

Amazon S3 is highly secure when configured correctly. The files are encrypted and only our servers can access them from our S3 buckets (i.e. no direct links). For more information on Amazon's security practices, see here: http://aws.amazon.com/security/

- Neal, co-founder of HelloFax

Scrive looks like a good product but is not free after the initial 3 documents. HelloSign is completely free.

I believe the HelloSign API also covers most, if not all, of the same use cases.

NOTE: I am a HelloSign co-founder

We'll eventually add in more advanced API features like embedded signing, customizable branding, etc. We may charge for some of those advanced features.

1) Absolutely. We'll be adding OAuth support shortly. 2) We don't have any filtering by signer's email address at this point but I like the idea.