Recent submissions

Comment · 7 years ago
For an out of the box solution, take a look at the pixelstick
Comment · 7 years ago
30 days would be fine - but since it’s 30 days after the end of the month, it ends up being more along the lines of 45-60 days after the user has been actively using the service (and thus costing us money).
Comment · 7 years ago
As an app developer, I wouldn't care about the 30% cut if apple's In-App Purchase SDK was up to par with other payment processors.

For example - as a developer I can't cancel subscriptions on a user's behalf, even if they've requested us to cancel it multiple times, nor can I refund a user's subscription, give them discounts/free months for their troubles/etc. The thing is, when a user reaches out to Apple to request a refund (since we can't do it on their behalf), and Apple denies the refund, we get the bad review.

On top of all of that, Apple does not pay out their developers until 30 days after the end of the month. That means that we can be waiting for 60(!) days before we receive revenue from an active, paid, subscription. They don't even let us know how much we will get paid for the month until a week before payments are dispatched.

Comment · 7 years ago
Fargate definitely takes some time to figure out. It took a while for us to realize that we needed to bump up our instance sizes because the default instance was a t2.micro.

However, now that we got it configured properly (took about 6 hours over the span of 3 days to catch the issues), we flawlessly serve 11M API requests/day without a problem. We were running these on DO boxes, moved it over to elastic beanstalk which caused more problems than it was worth, and finally landed on Fargate.

Tried EKS, but it was a bit more cumbersome than we would have liked for a K8s service. (We run another product of similar scale on K8s via GKE).

If you're looking for something closer to Heroku than K8s, then Fargate is decent option.

Comment · 8 years ago
Would love an early access code :) Email in Bio
Comment · 8 years ago
Essentially, it's a convertible note without the debt aspect.
Comment · 8 years ago
Well then that would just be silly. A large number of YC companies don't get in the first few times they apply with an idea. Getting rejected from YC doesn't mean your startup isn't viable - it may just mean it's not ready for investment (from them) yet.
Comment · 8 years ago

  If you’re accepted, you will be early accepted into the Summer 2019 batch which begins in June. If you’re not accepted, you can apply again during the regular Summer 2019 application cycle which begins in March.
I assume that means you'll find out at the same time as everyone else - so yes, "Early Rejection"
Comment · 8 years ago
Great to know! Here's to hoping they pay out the entire amount I'm owed.

Thanks, Guys!

Comment · 8 years ago
I've had friends that have lost $100k+ due to Adsense terminations on legitimate sites. I've personally lost about $10k. We'll see how much I actually get paid out from this class action (I think I read that they cap it at $5k)
Comment · 8 years ago
The update to the post can be found here: http://www.askamanager.org/2016/10/update-a-coworker-stole-m...

TLDR: Guy gets his job back and a generous raise (almost double his paycheck) after getting fired and threatening legal action.

Comment · 9 years ago
30 hashes a second is what you'd likely see on mid-range laptops. You can test your machine on CoinHive (https://coinhive.com/)

My fully maxed out 2017 rMBP can only do 50-60h/s at full speed with all threads. Most people don't have a machine nearly as powerful as mine.

Comment · 9 years ago
I had a run-in with CoinHive this weekend so I did a bit of research.

Most modern computers can do about 30/h a second. Coinhive currently pays out 0.00009030 XMR ($0.02 USD) per 1M hashes.

For a 10 second pause, they'd mine 300 hashes (about $0.000006 USD). To make $1 USD, they'd need to have ~166,666.66 people connect to their in store WIFI.

Comment · 9 years ago
Well that's not necessarily true. From one of your other submissions, you stated "...I am very bad at interviewing..."

So the problem seems more of, "Hiring Mangers think I'm unqualified" rather than "There aren't enough jobs for qualified developers"

Hiring an unqualified developer is MUCH worse than not hiring a developer at all. It's wasted time and money for the company. I've been on both sides of the table so if you want some feedback on your resume/interviewing skills feel free to shoot me an email.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton