Calendario prossimi incontri

Di -
Salve morcini,
ecco il calendario dei prossimi incontri:
31-07: CORBA: memory management nei sistemi distribuiti

data da definire:
xx-yy: Time Boxing techniques: la tecnica del "Pomodoro".

Commenti

Posta un commento

Post popolari in questo blog

JNI? there's someone who remembers something?

Di -
Java Communications Without JNI JNA is an open source project maintained by Tim Wall that allows you to write Java code only to call into native libraries (i.e., DLLs on Windows). Without JNA, you would have to write potentially complex Java Native Interface (JNI) code or other glue code to make this work. For instance, the following code sample from the JNA Wikipedia page works as-is on Windows, Linux, or OS X, to call the native C runtime  printf  function: ? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 import com.sun.jna.Library; import com.sun.jna.Native; import com.sun.jna.Platform;     /** Simple example of native library declaration and usage. */ public class HelloWorld {      public interface CLibrary extends Library {          CLibrary INSTANCE = (CLibrary) Native.loadLibrary(        ...
Continua a leggere

Peer reviews catch 60% of the defects...

Di MarcoR -
“Peer reviews catch 60% of the defects.” http://www.cs.umd.edu/~mvz/pub/eworkshop02.pdf All of us have known for a long time that code reviews find defects, and that reviews are cheaper and can be more effective than most kinds of testing. In Code Complete, Steve McConnell builds an overwhelming case for code reviews: disciplined code inspections can find between 45%-70% of all defects in code, while even fast, informal reviews can find 20%-30%. Studies at IBM, HP, Microsoft and other places show that it is several times cheaper to find bugs in code reviews than through testing. And evidence keeps coming in to support that code reviews work. http://www.cc2e.com/
Continua a leggere