▲ | 0xbadcafebee 5 days ago | |||||||
I see they're still using the old 2000s-style "dev", "test", "prod" environments. How many developers here are aware that this is a bad pattern? Do you use it even though you know it's a bad pattern, and if so, why? | ||||||||
▲ | aloknnikhil 5 days ago | parent | next [-] | |||||||
Since when did having isolated environments for dev / test and prod become a bad pattern? | ||||||||
| ||||||||
▲ | overfeed 5 days ago | parent | prev | next [-] | |||||||
> How many developers here are aware that this is a bad pattern? I've been around the block and I think dev/staging/prod is a great pattern! Anyone telling otherwise may be cargo-culting hyperscalers who: 1. Can't replicate their prod environment without spending tens/hundreds of billions in capex 2. Have spent an aggregate of billions investing in developing tools, processes, core-infrastructure teams, and specialized SREs to monitor and keep prod healthy. 2.1 Have tools supporting gated release to a fraction of their users with automated anomaly detection. FANGs can easily test changes against 0.01% of their userbase and get meaningful data back. If you're not constrained by (1) and don't have the benefits of (2), dev/test/prod is an excellent strategy you should use instead of testing in production for no reason. | ||||||||
| ||||||||
▲ | diamondfist25 5 days ago | parent | prev [-] | |||||||
is it a bad pattern? i'd love to know more cuz im starting on this route for my hetzner k3s setup | ||||||||
|