I believe, that there are plenty of areas where you could succeed by literally just building what is already here but making it actually good.
Less features but better quality including with UX.
3 karma · joined July 20, 2020
Less features but better quality including with UX.
If it wouldn't make sense for us to have test and prod, we wouldn't do it but i can't imagine a scenario where this is NOT beneficial.
We have 2 GCP accounts. One for production and one for test. Same Setup, not an issue due to terraform and the cost is reasonable for a test env.
Yes i would test basic / standard customizations a customer would do.
I would test the customization system itself.
If it is to complex, your cusotmiztaion system will bring you much more issues later on.
Most codebases are build and operated by 1-3 teams and if you are not able to reproduce your prod env as a test env, your architecture is broken.
The biggest issue in all my dev work so far was a really shitty codebase which would work somehow and had and still have hidden big issues going on.
You just don't see it today perhaps and delivered it in 1 day instead of 3. But you will fix the issue in production half a year later and either have lost data, corrupted data or you have to correct data.
Not doing any tests, is literally shit.
Missing Unit tests also often means no proper CI/CD pipeline. Because yeah why would you need a proper build if you don't even execute tests anyway right?
IT IS always a clearly ignored requirement of doing proper work. Quality work. Do less, do better. Its the fault of the manager to not think about it and enforce it and its the fault of the developer to build shit.