Discuss: https://image.nostr.build/ee5d28625c19ea6e51f2ad27a9aacb10f31213b5bb87749989a5212b439d1932.png https://image.nostr.build/16d6d29d615b339fefb9cdc58da80b5550f4e6187c9e04abdc6bb7fc852cc76e.png https://image.nostr.build/da00492fc87a8e27109e8d877f057dffe42ace20cce7952707b72cf0cd28bea9.png
Can you create a jira for this ?
"race conditions" being on that list makes it seem like a joke those can load to horrible crashes, and take ages to debug, but once you find them it's usually a small change to fix them can't exactly measure developer productivity by the quantity of code changes
Typical FAANG workflow to resolve app issues "efficiently": 1. Customer issues originating in Country A are initially logged in Salesforce. 2. If technical intervention is required, the support team in Country B escalates these cases to incidents within ServiceNow. 3. A team in Country C then assesses these incidents. Bugs requiring code changes are tracked in Azure DevOps (ADO). 4. A development team in Country D is trying to resolve the coding issue. They prioritize critical bugs for resolution within the current sprint, while less severe issues are addressed in the upcoming Program Increment (PI). You can't make this shit up! It's like a giant game of Chinese whispers across the globe. I guess, any developer stucked in this game long enough is planning how to escape. https://image.nostr.build/7ae8c768c1eb19526490d97d5ae3a7020ffbe9dac5e4ba799a01da171695c0d9.jpg
Seen it for decades; exited from it