Hihi, das ist sooo geeky, das versteht doch kaum jemand. Aber das macht den Charme dieses Comics aus. Immer ein Volltreffer. Gruss von einem, der auch schon seit 30 Jahren dabei ist.
Thomas Tempelmann |
December 15, 2011 at 11:52 PM
Hi, I don't get it... Please explain more...
Dennis Lean |
December 16, 2011 at 03:33 AM
Perhaps he forgot to mutex.
December 16, 2011 at 06:47 AM
Warum soll das kaum jemand verstehen?
Bei der Zielgruppe, die hier mitliest...
December 16, 2011 at 08:23 AM
i don't get it :(
December 16, 2011 at 08:29 AM
lol - ich spiele seit ~8 jahren für geld softwareentwickler - versehen tu ich 9/10... der hier ist wieder mal grenzgenial :-)
December 19, 2011 at 09:27 AM
the point is that programming/design flaws related to the multithreaded aspect of software usually show their effect not immediately, i.e. not at compile time nor immediately after program start.
(e.g. race conditions, forgetting to lock/free a mutex, etc.)
furthermore, when the problems eventually show, the're usually rather annoying to find/debug since they tend to be non-deterministic and therefore harder to reproduce.
(e.g. (c++) a program runs fine for a while, until after several minutes or so, the last thing you see before the crash is "segmentation fault", and you know there is a longer valgrind debugging session ahead of you.
btw, imho "ooops" is a way to reserved reaction for that matter, I would've gone for the f-word;))
December 19, 2011 at 03:40 PM
The comments to this entry are closed.
I'm a IT-guy in Hamburg, Germany