chrisquinnr

5 ms·

1.
by chrisquinnr 3y ago
>I have felt strongly that we would have been better off with a more boring approach like REST What led you to this feeling? I know you want to hear from people on why GraphQL is good, but why would REST have been a better choice in that
2.
by chrisquinnr 6y ago
Landmrk | React Developer | Remote | Full Time | Contract 3-6 mo to hire We're a location based marketing startup: we've worked with some of the biggest brands, music labels and artists and launched global campaigns using our besp
3.
by chrisquinnr 6y ago
This is a great collection. Lots of useful approaches, some of which I haven't seen before. Sure, some stuff wouldn't work for us, but that doesn't mean it's not useful to know about. Further reading section is also A++.
4.
by chrisquinnr 7y ago
I really enjoy getting to influence projects at their genesis, being a CTO gives me a mandate to intercept & triage requirements. Trading off some day-to-day coding for this opportunity is a win for me.
5.
by chrisquinnr 11y ago
I can't decide what to think about this pricing. Would a company pay $6k a year to almost not worry about hosting / ops? Actually, yeah, probably. Still seems like it's missing a lower tier though.
6.
Meteor Galaxy launches starting at $495 p/month(meteor.com)
3 points by chrisquinnr 11y ago|1 comments
7.
by chrisquinnr 11y ago
I have, not ready for prime time yet as client is dragging their heels but the tech is sound. Using stripe, with big props to http://themeteorchef.com/recipes/building-a-saas-with-meteor...
8.
by chrisquinnr 11y ago
+1 If there's not a Meteor-specific package you're comfortable with then this is the option. Case in point, I prefer using stripe and twilio via meteorhacks:npm.
9.
by chrisquinnr 11y ago
I've yet to come across a situation where something I wanted to do didn't a) have an existing Meteor package, or b) have an npm package that you can include using meteorhacks:npm by arunoda. I'm using Meteor for two enterpris
10.
by chrisquinnr 11y ago
For 1), the hardest part for me coming from LAMP stack apps was shifting over to the way routing works (see https://github.com/iron-meteor/iron-router ) and attaching your subscriptions to routes. For 3) I've used