undefined | Better HN

0 pointsericd3y ago0 comments

Couldn't this be done by giving the devs some transparency into how it's killing their team's budget and reminders, instead, so that they'd manage this themselves? Because this sounds super frustrating to deal with.

0 comments

hacb3y ago

We kind of already have. We built a CLI that allows them to create/update/delete/list all their dev envs, so they have all the tooling needed. Also, we are still a small/medium sized company, so we often had the chance to talk with them to expose this issue, but in the end it never really worked.

wizhi3y ago

> we are still a small/medium sized company

Sorry this is somewhat off-topic, but _why_ do you have virtual development machines?

hacb3y ago

We currently have ~40 microservices running (for the same number of devs), and having the full stack on a laptop is not possible. Especially with 80% of the devs having MacBook and Docker in a VM.

Also, this allow us (the infra folks) to chose how devs will work (partially), so it's easier for us to debug when they have issues because we do not have to deal with custom Makefiles etc.

1 more reply

aprdm3y ago

One example can be to target many different OSes/CPU architecture / GPUs architecture.

trumbitta23y ago

A weekly digest over email, or a dashboard on a real screen if you all work out or the same office, indicating costs and what's contributing to them. That will do wonders.

hacb3y ago

That will also add a lot of overhead/maintenance cost that we can't currently handle.

j / k navigate · click thread line to collapse

0 comments

hacb3y ago

wizhi3y ago

> we are still a small/medium sized company

Sorry this is somewhat off-topic, but _why_ do you have virtual development machines?

hacb3y ago

We currently have ~40 microservices running (for the same number of devs), and having the full stack on a laptop is not possible. Especially with 80% of the devs having MacBook and Docker in a VM.

Also, this allow us (the infra folks) to chose how devs will work (partially), so it's easier for us to debug when they have issues because we do not have to deal with custom Makefiles etc.

1 more reply

aprdm3y ago

One example can be to target many different OSes/CPU architecture / GPUs architecture.

trumbitta23y ago

A weekly digest over email, or a dashboard on a real screen if you all work out or the same office, indicating costs and what's contributing to them. That will do wonders.

hacb3y ago

That will also add a lot of overhead/maintenance cost that we can't currently handle.

j / k navigate · click thread line to collapse