3 ms·

> All developers work with a fully fledged incident.io environment locally on their laptops: it allows for a <30s feedback loop between changing code and runnin

by mcny 3y ago

> All developers work with a fully fledged incident.io environment locally on their laptops: it allows for a <30s feedback loop between changing code and running it, which is a key factor in how productively you can work with our codebase. This to me is the biggest accomplishment. I've never worked at a company (besides brief time helping out with some startups) where I have been able to run a dev/local instance of the whole company on a single machine. There's always this thing, or that, or the other that is not accessible. There's always a gotcha.

teaearlgraycold 3y ago
I’m currently doing my best to make this possible with an app I’m building. I had to convince the CEO the M2 Max would come in handy for this (we run object detection models and stable diffusion). So far it’s working out!
8n4vidtmkvmk 3y ago
I never couldn't run the damn app locally until my latest job. Drives me bonkers. I don't understand how people aren't more upset and this atrocious devex. Damn college kids don't know what they're missing.
kamikaz1k 3y ago
I used to work in a company like that, and since leaving it I’ve missed that so much. People who haven’t lived in that world just cannot understand how much better it is, and will come up with all kinds of cope.
physicles 3y ago
I can’t imagine not having this. We use k3s to run everything locally and it works great. But we (un)fortunately added snowflake in the last year — it solves some very real problems for us, but it’s also a pain to iterate on that stuff.
daxfohl 3y ago
We used to have that, but it's hard to support as you scale. The level of effort is somewhat quadratic to company size: linear in the number of services you support and in the number of engineers you have to support. Also divergent use cases come up that don't quite fit, and suddenly the infra team is the bottleneck to feature delivery, and people just start doing their own thing. Once that Pandora's Box is opened, it's essentially impossible to claw your way back. I've heard of largeish companies that still manage to do this well, but I'd love to learn how. That said, yeah I agree this is the biggest accomplishment. Getting dev cycles down from hours or days to minutes is more important than getting them down from minutes to 25% fewer minutes.
- mcny 3y ago
  I was thinking of this as I was reading the comments on another thread here https://news.ycombinator.com/item?id=38816135 https://news.ycombinator.com/item?id=38816135 Like if you have logic apps and azure Data pipelines, how do you create and more importantly keep current the local development equivalents for those? I'm not saying if you are YouTube that all the videos on YouTube must fit on a developer's local machine but would be nice if you could run the whole instance locally or if not, at least be able to reproduce the whole set up on a different environment without six months worth of back and forth emails.
  - daxfohl 3y ago
    Yeah, the whole top down vs bottom up quandary. Top down is more boring but easier to support at scale. Bottom up is more dynamic but cross cutting changes end up taking inordinate effort.

by mcny 3y ago

teaearlgraycold 3y ago

I’m currently doing my best to make this possible with an app I’m building. I had to convince the CEO the M2 Max would come in handy for this (we run object detection models and stable diffusion). So far it’s working out!

8n4vidtmkvmk 3y ago

I never couldn't run the damn app locally until my latest job. Drives me bonkers. I don't understand how people aren't more upset and this atrocious devex. Damn college kids don't know what they're missing.

kamikaz1k 3y ago

I used to work in a company like that, and since leaving it I’ve missed that so much. People who haven’t lived in that world just cannot understand how much better it is, and will come up with all kinds of cope.

physicles 3y ago

I can’t imagine not having this. We use k3s to run everything locally and it works great. But we (un)fortunately added snowflake in the last year — it solves some very real problems for us, but it’s also a pain to iterate on that stuff.

daxfohl 3y ago

We used to have that, but it's hard to support as you scale. The level of effort is somewhat quadratic to company size: linear in the number of services you support and in the number of engineers you have to support. Also divergent use cases come up that don't quite fit, and suddenly the infra team is the bottleneck to feature delivery, and people just start doing their own thing. Once that Pandora's Box is opened, it's essentially impossible to claw your way back. I've heard of largeish companies that still manage to do this well, but I'd love to learn how. That said, yeah I agree this is the biggest accomplishment. Getting dev cycles down from hours or days to minutes is more important than getting them down from minutes to 25% fewer minutes.

mcny 3y ago
I was thinking of this as I was reading the comments on another thread here https://news.ycombinator.com/item?id=38816135 https://news.ycombinator.com/item?id=38816135 Like if you have logic apps and azure Data pipelines, how do you create and more importantly keep current the local development equivalents for those? I'm not saying if you are YouTube that all the videos on YouTube must fit on a developer's local machine but would be nice if you could run the whole instance locally or if not, at least be able to reproduce the whole set up on a different environment without six months worth of back and forth emails.
- daxfohl 3y ago
  Yeah, the whole top down vs bottom up quandary. Top down is more boring but easier to support at scale. Bottom up is more dynamic but cross cutting changes end up taking inordinate effort.