It was, but I don't know why. I'm curious to hear if Heroku releases any information about how this happened. Heroku's DNS was returning a single 100.64.x.x address which is in a reserved range.
What would it do? I looked (probably too) briefly...and thought the the main value was mostly the coach. Or at least, the value I saw that I was "OMG, we need this in French _now_".
It would have some expanded functionality to take the place of the coach - it would give turn-by-turn directions each day on what to eat, and educate the user on how to avoid FODMAPs / other eating options. But it would have less customization (at least at first), and the user obviously wouldn't be able to get questions answered in the same way
Gotcha. So that could make sense. Someone could start with the coaching, then downgrade to this option instead of just cancelling due to price once they don't use the coaching services enough.
i.e., it would help you with churn a bit, I think.
If you compare that to paying for a dietitian, it's actually not TOO bad. BUT, I think churn will be high due to price.
I could see a declining fee model. Just a thought.
We are trying a low FODMAP for my wife. I could see her paying for it for 2-3 months, then we would probably find that expensive at $29/w...but, if after 3 months, it went down to say $29 per month, then it would totally make sense as we would use it a lot less, I think.
At least if we compare to when she stopped gluten, lactose and a few other things 6 years ago...the worst was the first 2-3 months.
A dietitian is a different service though. Registered dietitians are trained, accredited professionals that can legally give you medical advice. This service will not give you medical advice.
> If you compare that to paying for a dietitian, it's actually not TOO bad. BUT, I think churn will be high due to price.
Could the high pricing be because this is really a guide to a solution -- once customers have need for a guide, they'll stop using the service; that is, churn is naturally built in due to the nature of the service.
Yup, this is the comparison we see - alternative is going to a dietitian, which is very expensive. Re: your other post on people potentially churning after 2-3 months - we've actually seen strong retention, but leaving after 2-3 months is certainly a use case we've seen as well. Those users tend to have gotten a lot of value from the product, and are also profitable for us - overall not a bad outcome
No and honestly after using mailgun for about 3 hours now, I will not go back to sparkpost. I will be requesting a full refund since service was never rendered and if that is not answered, I guess chargeback.
I have some availability to do freelance work, roughly a day or two per week. I have extensive SaaS experience with US based startups.
Location: Canada, but only remote work.
Remote: Yes, only.
Willing to relocate: No, could travel once in a while but that's about it.
Technologies: Ruby (Rails, or not), JavaScript, CoffeeScript, testing frameworks like RSpec and Jasmine, Go, React.
Résumé/CV: https://www.linkedin.com/in/jipiboily
Email: j@jipi.ca
Having hired a bunch of people, including juniors out of school, I'll tell you this: apply, just apply.
A job description and requirement is their picture of the ideal candidate, but they will hire the person that's the closest to that, and other things not mentioned in the offers like how you would fit culturally in the team, work with others, and so many other things.
Just apply to what you want to do, what's the worst case again? Ah, you spent time writing a cover letter.
Btw, keep your cover letter short. People might not read it if it's too long.
Another last tip: apply even if you are almost certain you won't have it. Never say "I'll apply when I get more experience". You know what? By then, you will change, the company will change, and it might not be a good fit anymore. I wanted to apply to a couple of specifics startups in the past that I never applied too because I felt like I was not up to it, in the end, I was wrong and the company changed so much that I don't want to work there anymore at all, but I'm sure that would have been great for years.
In school there was a scholarship I was almost eligible for. I needed a 3.5 gpa but only had 3.2 so I didn't apply thinking I was disqualified. A few months later I found out someone with a 2.3 got it because lack of entries.
Then again later I entered a programming competition with a $5 entry fee. Only 2 people entered and we each won $100 and $75. A 3rd place prize of $50 went unclaimed. Anyone who entered and earned 0 correct would have gotten it. As second place dude didn't get any right.
If it's low effort or something you enjoy, always apply. It's almost always worth it. You miss 100% of the shots you don't take.
It seems that everything in the process, from the "Jobs Page" that goes to a black hole, to the unrealistic job descriptions, to the months-long interview processes, to the opaque and feedback-less selection process, seems to be built for the purpose of not hiring candidates. Which seems odd for an industry that constantly complains about not being able to find talent and is bent on perpetuating the "shortage of engineers" meme.
This CI server is so easy to get up and running, it's impressive! I'm more a fan of hosted solutions like Circle, Travis or Codeship but this is what I would use if I had the need to have my own CI installed.
btw, I'm not sure this still works, but I wrote a blog post on how to get from zero to a fully working Drone CI in less than 10 minutes, pretty sure it still works as the basics didn't change much.
It's always DNS.