stratified

há 6 anosdiscuss

PyCharm / IntelliJ - I used to be a die hard vim user but these products just blew my mind. Worth every penny and then some!

stratified

há 6 anosdiscuss

[DISCLAIMER] software engineer @ AWS, not working on billing.

Interesting project! This product can unlock a lot of customer savings, and wishing you all the best.

I have a couple of questions:

- Are you focusing on EC2 compute costs or are you focusing on other AWS offerings as well? Curious to see how the savings compare to EC2 compute optimizer [1].

- How is your churn rate? What is the value of your product once a customer optimized their AWS bill?

- Do you have a screencast of your product?

[1] https://aws.amazon.com/compute-optimizer/

stratified

há 6 anosdiscuss

Developer tools is a broad term. My subjective opinion:

* If you mean code libraries (e.g. a licensing model)? I don’t think a lot of people would pay for that these days.

* Managed solutions for sure, most developers and small companies are happy to outsource anything that reeks of devops.

* IDEs etc, yup worth every penny.

stratified

há 6 anosdiscuss

[DISCLAIMER] I work at AWS, not speaking for my employer.

We really need some more details on your infrastructure, but I assume it's EC2 instance cost that skyrocketed?

A couple of pointers:

- Experiment with different GPU instance types.

- Try Inferentia [1], a dedicated ML chip. Most popular ML frameworks are supported by the Neuron compiler.

Assuming you manage your instances in an auto scaling group (ASG):

- Enable a target tracking scaling policy to reactively scale your fleet. The best scaling metric depends on your inference workload.

- If your workload is predictable (e.g. high traffic during the daytime, low traffic during nighttime), enable predictive scaling. [3]

[1] https://aws.amazon.com/machine-learning/inferentia/

[2] https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-sca...

[3] https://docs.aws.amazon.com/autoscaling/plans/userguide/how-...

stratified

há 6 anosdiscuss

The unwritten laws of engineering (James G. Skakoon, original by W.J. King). 67 page introduction to "soft skills" for engineers. I wish I read this book earlier to understand that being a great coder is only part of growing into a great engineer.

comments