hampfi

3 ms·

1. 1.▲
   by hampfi 6y ago

   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.
2. 2.▲
   by hampfi 6y ago

   Obviously but this is not a black and white thing. 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.
3. 3.▲
   by hampfi 6y ago

   I know this very well and i'm stlil not seeing an issue. 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.
4. 4.▲
   by hampfi 6y ago

   Thats a weird point you are making. 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 late
5. 5.▲
   by hampfi 6y ago

   Not sure where you are working but not a lot of people work at/on a huge code base. 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.
6. 6.▲
   by hampfi 6y ago

   Yeah no. 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. B