602 karma · joined March 7, 2007
That's often why contract work can pay better when it comes to hourly wages: there's more risk. If it were me, I'd try to have about 50% more in contract work wages lined up than for at least 6-months before leaving a "secure" job.
That can be a lot of money for some people, and in general, I'm a bit disappointed that I found out about the Billing product increase through HN. I would have expected to get an email from Stripe, maybe a month ago, saying "Hey: our rates are going up on 12 November"
I genuinely don't even know: am I going to be seeing this price increase? Would have liked getting an email about something like this, rather than finding out on HN, and now having to dig into things to figure out if I'm actually affected (which I presume I am).
To give you a comparison: if my bank or credit card company increased their rate, I'd expect to be (and am) notified of that.
My two cents :)
The idea is pretty straight forward: you click on the Extension Icon, and it'll analyze the page you're on and show you the libraries, basic data from GitHub (like star-count and when it was last committed to), the location of the developer(s) (if shared), and the description.
Open to any feedback or questions :)
For me, HN has become a source of news/ideas related to innovation (with an obvious leaning towards digital/technological innovation).
I guess, given how I see this community (and use it for access), it's refreshing to see an article like this :)
I find that there isn't enough critical thought given to why one ought to pursue an aggressive growth strategy. And that generally, staying small is seen as a failure to grow, rather than a conscious effort to grow in line with ones own life. Going from 3 to 100 employees in a (relatively) short period will naturally have a large impact on one's personal life and mental/emotional state. I think it's important to ask, before one ventures into that kind of adventure, whether or not you're okay risking mental/emotional (and arguably physical) stability in place of the adventure, and the potential financial windfall.
There's nothing wrong with saying no to that risk. This is a short life we have, and spending it chasing growth to keep up w/ the momentum of the extremes of capitalism doesn't need to be your game ;)
[edit] Prefer my last paragraph be written as: There's nothing wrong with saying no to that risk. This is a short life we have, and if you're spending it chasing growth to keep up w/ the momentum of the extremes of capitalism, it doesn't need to be your game ;)
We ended up plugging in the AWS JavaScrpt S3 SDK. We trust their uptime much more, and browser support is pretty widespread. It came with it's own headaches (namely, client side clocks being out of sync, and AWS rejecting uploads due to some security checks), but once we got everything figured out, it became incredibly stable.
It works by uploading files directly to your S3 bucket. Setup wasn't seamless (notably, setting things up with AWS Incognito), but in the end, we're incredibly happy we went this way.
We still use 3rd parties for resize images that are uploaded (namely, Cloudinary, which has been fantastic), but decoupling the upload logic from the usage logic has helped tremendously, and affords us reliability in that we control where the file is stored, how it's name, and are not tethered to a 3rd party (other than AWS).
Pricing is linked to in the footer: https://www.getonboarded.com/pricing
I'd promote the email-address thing a bit more. Often people want a branded email address, but don't know exactly how to go bout it. That would stand out to me (eg. plug-and-play with your existing gmail)
Best of luck!
Also, hi from Toronto! I work out of CSI at Bloor + Bathurst. Nice to see another Torontonian on here :)