364 karma · joined October 23, 2014
This is totally anecdotal but I remember from an early season of Survivor that there was a contestant who cooked for everyone so nobody wanted to vote them off the island. I think some of that tribal thinking applies to business.
Here's Cashier's mission statement:
> Laravel Cashier provides an expressive, fluent interface to Stripe's and Braintree's subscription billing services. It handles almost all of the boilerplate subscription billing code you are dreading writing. In addition to basic subscription management, Cashier can handle coupons, swapping subscription, subscription "quantities", cancellation grace periods, and even generate invoice PDFs.
In my opinion, Cashier fails to achieve its purported goals. First of all, the Stripe API is already a joy to work with and there's little value in trying to improve it by hiding API methods behind a bunch of smoke and mirrors. Second, Cashier doesn't significantly reduce boilerplate code. It actually traps you into its limited and opinionated way of doing things. It's a net negative for anything but the most basic of use cases. In my experience, I had to write additional billing code to get it to do basic things it should have been able to do in the first place. It got to the point where it just wasn't worth it anymore and starting from scratch was the better option, hence this package.
Here's just one example: I want to create a Stripe customer, without a card up front, trialing on a subscription. A super common SaaS use case. You would think that Cashier would make that easy, right? Nope. Instead, you have to manually set a custom 'trial_ends_at' field on your application user, deal with this hacky onGenericTrial() method to determine if your user is on a trial without a subscription (which I needed to create!), and in the end no customer or subscription is ever created in Stripe. Instead of using Stripe to do what it's made for, Cashier handles this itself, creating an unmanageable nightmare. What's even worse is that your application is effectively out of sync with Stripe.
The package I created avoids these headaches. It provides a wrapper around the Stripe API that automatically syncs Stripe data with your application whenever you make an API call or Stripe sends data to your webhook. This way you aren't locked into any specific way of doing things and you have total control over your data.
The only disclaimer I want to add is that my package doesn't plan on supporting Braintree, which is only used by about 5% of Cashier users by installs according to Packagist[1][2].
[1]: https://packagist.org/packages/laravel/cashier
[2]: https://packagist.org/packages/laravel/cashier-braintree
For example, my startup can pull information on ownership, mortgage and sales history, liens, and foreclosure records, among many other things, for a given property. If you were to cross-reference the data with other public and proprietary sources, it could get pretty, umm... what's the right word?, "interesting", in terms of accuracy and level of detail.
Linus Torvalds: Well, so this is kind of cliché in technology, the whole Tesla versus Edison, where Tesla is seen as the visionary scientist and crazy idea man. And people love Tesla. I mean, there are people who name their companies after him.
The other person there is Edison, who is actually often vilified for being kind of pedestrian and is — I mean, his most famous quote is, "Genius is one percent inspiration and 99 percent perspiration." And I'm in the Edison camp, even if people don't always like him. Because if you actually compare the two, Tesla has kind of this mind grab these days, but who actually changed the world? Edison may not have been a nice person, he did a lot of things — he was maybe not so intellectual, not so visionary. But I think I'm more of an Edison than a Tesla.
http://www.ted.com/talks/linus_torvalds_the_mind_behind_linu...
Your best bet is to work backwards. By that I mean interview users first (preferably in a low-competition niche), find out what their needs are (preferably a business need that they're willing to pay you money for), and then build a product to satisfy those needs (as fast as possible with a well-tested and reliable stack). Don't fall into the trap of building a product nobody cares about and then trying and failing to find an audience for it. I made this mistake and it was painful.
My thoughts exactly. When I think of notes, grocery lists and todo lists come to mind. In my opinion, the function of note taking is comparable to RAM. It's short-term and ephemeral. Notes may contribute to a long-term document that should absolutely be digitized, but storing the notes themselves defeats their purpose in my view.
Notes are supposed to be brief records to _aid memory_, not critically important documents. For this purpose, pen and paper should be good enough in my point of view. For anything more serious, I would absolutely agree that "longevity, portability, and privacy" are much more important. However, for this use case I don't believe technology adds very much value. Depends on your definition of a "note" I guess.
I know HN is for the tech crowd, but can I suggest something so simple it sounds stupid? If you want to read your notes 50 years from now use a pen and paper. Go ahead, downvote away. Yes, you won't be able to index them and search them and yadda yadda yadda but you're writing _notes_, not full-fledged documents.
What is a note? "A brief record of facts, topics, or thoughts, written down as an aid to memory." according to Google.
I keep a small Moleskine notebook and a pen with me to write down notes and ideas. James Altucher uses a waiter's pad. It works just fine. I know it's a radical thing to say but technology isn't always the solution to our problems.
Don't automatically assume you have to accept their terms and negotiate on price. You can ask for anything you want. You don't get what you don't ask for. If it's a publicly traded company why not ask for stock? A stock deal might be more valuable than a cash deal. Something to consider.
As an aside, I'm working on a RE investment product that solves challenges similar to this one and I'm looking for RE investors to join me. If you're interested, shoot me an email at hello[at]myname.com.