3 ms·
I get the benefits of having identical environments as production (and that's what I aim for, at least, with our staging server) but to be honest, I like having
by narcissus 15y ago
I get the benefits of having identical environments as production (and that's what I aim for, at least, with our staging server) but to be honest, I like having a small amount of diversity across our development servers. It's the small differences that have helped us to work out that bizarre bug (turns out, it was actually a problem specific to a particular version of PHP) or to find those small assumptions about the environment (eg. assumed file paths and so on).
The latter aren't that much of an issue, but I find that being able to deal path changes, for example, makes the code that little bit more flexible, making it a little easier to make changes to the production environments going forward with less issue.
- gbog 15y agoI just changed job and got from a very unified setup (Linux-only, everyone working on one server) to a much more disperse one (all OSes, working on local). I agree that some diversity helps to keep flexibility and have a code base, data model that is more forgiving for little discrepancies. But I guess there must be some checkpoints, or rules, were you don't allow any flexibility. You build a much more flexible project on rocks. For instance, no deployment if one test don't pass, and tests should include "X"-lint checks.