4 ms·
I downvoted you because your first comment was "Hellosign is a joke." solely due to the aforementioned bug. Then you edited your comment. You ran into a bug in
by switz 6y ago
I downvoted you because your first comment was "Hellosign is a joke." solely due to the aforementioned bug. Then you edited your comment.
You ran into a bug in some web software. It happens. Sounds like it was already fixed.
Meanwhile, the above blog post is a pretty amazing technical breakdown that is extremely detailed and well constructed. To reduce the entire company down to "a joke" because you ran into a bug once is just rude and dismissive. You might even agree because you changed your comment, although you still found a way to insult the blog post and the author.
And no, I don't work for Hellosign. I'm just a software engineer with some empathy for the hard work that has clearly gone into this. This is great knowledge sharing. Time and place.
- babuskov 6y ago> You might even agree because you changed your comment Yes. I changed it like 5 seconds after posting. Even tried to create a new document to show how it failed, but it was on a different computer and I couldn't reproduce it here. It's probably a browser/OS combination. > And no, I don't work for Hellosign. Well, alright then. But you aren't the only one. The score on it has had many ups and downs today.
- joefife 6y agoTheir job is not to make a best effort. Their job is to provide an authoritative and trustworthy record. This is quite serious if these documents are to be used in litigation. Generally I'm happy with best effort, but in the case of this situation where a reliable record is required, they've dropped the ball.
- michaelcampbell 6y agoWhat more effort can one give but best?
- Klinky 6y agoMaybe "best effort" is a misnomer, but it's often used to signify a general attempt without guarantee, rather than the absolute best effort possible. Like a delivery service making a "best effort" to complete delivery in 2 days, but there are no guarantees compared to the more expensive overnight service, or UDP vs TCP as far as packet guarantees. In this case it seems they make a "best effort"(not guarantee) to offer uniform document display across browsers and OSes, which suggests they may only test the most popular browsers and OSes, and edge cases like Firefox on macOS may not get much love. https://en.wikipedia.org/wiki/Best-effort_delivery https://en.wikipedia.org/wiki/Best-effort_delivery
- edoceo 6y agoJust be perfect everytime.
- an_opabinia 6y agoWhat’s funny is if you’ve ever talked to a lawyer, which clearly you haven’t, you’d discover that (1) the formatting of the document isn’t that important (2) you don’t need a signature for there to be an agreement (3) in situations where the above are in dispute, or where the above isn’t true, it’s not really about the contract, it’s about the partnership I think HelloSign provides the right amount of magic for ordinary people who think those things matter. It should just be cheaper and provide an API for free.
- ponker 6y agoIf you expect 100% bug free software, expect to pay literally hundreds of millions of dollars for it. It does exist but for some reason people prefer the mostly good stuff that costs $10.
- enraged_camel 6y ago>> To reduce the entire company down to "a joke" because you ran into a bug once is just rude and dismissive. It depends on the software and its purpose. Signatures are very serious business. They carry with them enormous legal weight and not getting them 100% right can have massive repercussions. Therefore, it’s all about trust. So then the question becomes, if trivial bugs like this were not caught during QA, what else must have slipped through?