aliscott
Joined 14 years ago
Karma
59
Submissions
32
Member since
Aug 1
Creating infracost.io
View on Hacker NewsRecent submissions
Comment · 1 year ago
Infracost | Senior Software Engineer | Remote (GMT+2 to GMT-6) | Full-time | €80K - €140K EUR
Infracost helps engineering teams understand cloud costs before they deploy infrastructure changes. We’re looking for a Senior Software Engineer to help us solve challenging problems at scale.
What we’re looking for:
* Solid experience with statically typed languages. Our core parsing functionality is in Golang.
* Knowledge of Node.js and TypeScript—our APIs and business logic rely heavily on them.
* Experience building and maintaining complex systems, solving integration, performance, and scalability challenges.
* (Preferred) Familiarity with Terraform, Kubernetes, and AWS—we use these tools, and so do our customers.
Recent challenges we’ve tackled:
* Refactoring our Terraform HCL evaluator to handle monorepos with thousands of projects.
* Mapping Terraform resources to their deployed cloud counterparts accurately.
* Scaling our APIs and onboarding to support customers with thousands of GitHub orgs and tens of thousands of repos.
More info & apply: https://www.ycombinator.com/companies/infracost/jobs/vdMNDwh...
Comment · 3 years ago
Great point about the multiple API calls. One of the big problems we’ve heard about using SCPs is that they are too late. If a deployment fails because of them the developer needs to go through another pull request/code review.
Estimating costs for serverless technologies upfront is definitely challenging. We're thinking of bringing in the last 30 days of usage for these resources to give engineers some visibility.
Comment · 3 years ago
Awesome, yeah we’ve seen people using this method and the main complaint we’ve heard is this is annoying for developers since it blocks their deployments when they run `terraform apply`, so they need to create new pull requests and wait for another code review. Combining both can definitely help with this.
Comment · 5 years ago
(co-founder here) Thanks! We started on this last August, so still pretty early and got a lot more we want to add.
Comment · 5 years ago
Thanks, feel free to reach out if we can help with anything.
Comment · 5 years ago
Thanks got it, will contact you when it's live.
Comment · 5 years ago
Sure, it's https://twitter.com/leckie. Thanks!
Comment · 5 years ago
Great, thanks for the details - supporting these negotiated rates and any custom price books is definitely on our roadmap.
Comment · 5 years ago
Thanks, running on self managed clusters or bare metal can save costs in some circumstances, but comes with trade-offs and overheads as well. In our previous company we were managing Kubernetes on bare-metal and what we found was every team started using more and more resources until we ended up with a sprawl of over-provisioned and under-utilized services. We want to support this use case as well by allowing price books to be set up for custom environments so each developer can see a "cost" for these cases as well.
Comment · 5 years ago
Do you know if they have public pricing available? Or are you using negotiated rates? If so, we're looking to add support for custom price books in the future.
Comment · 5 years ago
Agree, state files can contain sensitive information. We parse the Terraform client side and only send the details to the API that are needed to determine the price, i.e. the instance type, region, etc.