Comments - System Fail - TechHui2024-03-28T23:53:51Zhttp://www.techhui.com/profiles/comment/feed?attachedTo=1702911%3ABlogPost%3A124145&xn_auth=noSome people, when confronted…tag:www.techhui.com,2013-08-23:1702911:Comment:1243802013-08-23T16:00:07.939ZStephen McMahonhttp://www.techhui.com/profile/slmcmahon
<div id="imcontent" dir="ltr"><span dir="ltr">Some people, when confronted with a problem, think, 'I know, I'll use threads' - and then two they hav erpoblesm.</span></div>
<div id="imcontent" dir="ltr"><span dir="ltr">Some people, when confronted with a problem, think, 'I know, I'll use threads' - and then two they hav erpoblesm.</span></div> These are great insights. For…tag:www.techhui.com,2013-08-20:1702911:Comment:1243362013-08-20T17:27:13.215ZDaniel Leuckhttp://www.techhui.com/profile/dleuck
<p>These are great insights. For 2) I would add that its rarely a good idea for a typical programmer (i.e. the 99.99% of programmers who aren't experts in concurrency) to <em>ever</em> do low level concurrent programming in a critical production system. There are plenty of great frameworks that handle concurrency and allow you to plug in your code in the appropriate places. I remember an interesting comment from Prof. Doug Lea, the author of Concurrent Programming in Java, during a JCP…</p>
<p>These are great insights. For 2) I would add that its rarely a good idea for a typical programmer (i.e. the 99.99% of programmers who aren't experts in concurrency) to <em>ever</em> do low level concurrent programming in a critical production system. There are plenty of great frameworks that handle concurrency and allow you to plug in your code in the appropriate places. I remember an interesting comment from Prof. Doug Lea, the author of Concurrent Programming in Java, during a JCP discussion, "Concurrent systems are hard to write and even harder to test. I get it wrong all the time."</p>
<p>Also, while I agree that you should always optimize for stability first, its a good idea to do some thinking about future performance requirements so you don't make decisions that prevent scaling up in the future.</p>