2 ms·
It’s not one or the other. It should be trivial to deploy to prod without complex configuration (modern edge compute platforms seem to do a good job of this). H
by vlovich123 4y ago
It’s not one or the other. It should be trivial to deploy to prod without complex configuration (modern edge compute platforms seem to do a good job of this). However, local testing should definitely still be a thing.
You may have gigabit but you’re still potentially traversing the world - latency is going to lengthen the duration of your test suite. Plus when deployed you’re dealing with flakiness that’s totally outside your control (external internet connectivity of CI tends to be flakier than local connections).
In terms of equity, I have not seen gigabit fiber be widely available. Nominally I have gigabit cable in San Francisco although real world performance is much wider variance than one might hope. And some junior members at the start of their career may be choosing to be as economical as possible (eg using just a cellular hotspot through their phone for all their connectivity needs). Heck, at the office I get maybe 50 mbit/s out of the wifi with no wired option (and that’s not talking about the quality of the wifi).
It’s a nice idea and may work on small teams. For anything moderately complex, you’ll want local AND cloud, not OR. Also make sure to design for both from the get go.
Source: I’ve seen the gamut of what works and keeps testing infra humming smoothly along for dev teams of all sizes/maturity. Everyone learns the lesson of being able to run tests locally at some point.
Remote development on cloud servers can work and is an orthogonal thing. But if possible don’t use cloud services if possible (ie use local simulators/emulators if possible and they do a decent enough job).