|
|
|
|
|
|
by foobiekr
1218 days ago
|
|
|
As a rule, it is better to have developers learn one way to work, rather than N. A problem with time travel debugging is that you generally can't use it in production [of course, there are people who think devs should have direct access to prod, for them there is no help], and you 100% cannot use it for anything deployed at a customer (so for embedded, devices, actual non-SAAS software etc. etc.). It's better to shore up your tools so that the workflow is very straightforward and leave stuff like time travel for people doing work on a very narrow subset of very hard to understand bugs. |
|
|