|
|
|
|
|
|
by ojintoad
1278 days ago
|
|
|
I haven't read the full thing but one thing you can do is institutionalize some of this stuff. The screenshot here especially: https://wizardzines.com/zines/debugging-guide/samples/2-tiny... You can institutionalize this practice at your org in some ways. At my org we have: * strawman apps for our cloud systems and our windows services to practice deployments and startup/shutdown behavior without having to wait to compile full apps * alwaysfails and alwayspasses tests in our test projects for confirming how test frameworks behave and our test reporting/logging function * to some extent, health check pages on apps can hold limited tests https://www.thoughtworks.com/radar/techniques/health-check-p... Maybe the zine encourages that, haven't read it yet, but looking forward to digging in based on recognizing this strategy. |
|
|
