Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Does your interview process require knowing cloud costs off the top of your head? Because that's hard to track tbh


Sounds like it requires knowing them to an order of magnitude or so... Which honestly sounds like a pretty good bar to have your team above?


Honestly, after ~13y in this, I only know a handful of items from the famous latency table, notably those I've used a lot (mutexes cost 25ns, is only 1/4th of main memory reference tho, then disk seek is x100K of that). I'm "DevOps" (and titular variants thereof) in most of my resume.

That said, I'm not above your bar as each cloud provider have their own pricing model. I'm not even above your bar for AWS---which I've used the past six years---just for the sheer diversity of their offerings, not to mention regional variations. I know how EC2 servers are priced relative to each other but when we include ECS, DynamoDB, Lambda, etc., I'm gonna need a cheat sheet.


You'd probably be able to tell me if using Lambda for my backend is gonna be closest to, $2, $20, or $200 / month, right?


What the… no.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: