4 ms·
Finding products breakages through analytics is very backwards. If a team is deploying code that untested (or with that poor a process), could you really trust
by scott_karana 9y ago
Finding products breakages through analytics is very backwards. If a team is deploying code that untested (or with that poor a process), could you really trust them to make informed judgements either? That needs to be fixed earlier than your product.
UX improvements or mistakes in a conversion pipeline, sure though. Fair points there. :)
- TheReveller 9y agoI believe that's naive. There is always a non-zero chance that deploying new code will cause an issue that is not covered by your unit tests or integration tests. Good testing methodology means adding to your tests when you find such a case, not promising that all possible cases are covered all the time, because that's unreasonable, and the assumption that there's no way it could break on deploy is the kind of hubris that leads to breakages when you deploy.
- scott_karana 9y agoI agree with "defence in depth": analytics can help catch problems... However, many here are pitching it as a primary selling point. Relying exclusively on it is a design/process failure, in my book.