TL; DR: generally, developing a good sense of what to do ***before
writing a single line of code*** works really well.
On 9/4/19 6:32 , N. Bouraqadi wrote:
Hi everyone,
Can I get your input on the following questions :
- What are your best practices and recommendations for developing and testing concurrent software?
- How to discover need for synchronization/critical sections/ when doing TDD?
- How to write code to avoid dead-locks?
Thanks for your help,
Noury
_______________________________________________
Esug-list mailing list
Esug-list@lists.esug.org
http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org
.
_______________________________________________
Esug-list mailing list
Esug-list@lists.esug.orghttp://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org