Skip to Content

software development

Posted on  by  from the site Ninja Verification
In software design, a continuous integration system is a system for compiling and testing code on a continuous basis. When a build fails, the code is rejected and the owner notified. When the code is good (compiles okay and sanity tests pass), the code is accepted and is made available for distributing to the development [...]
Martin d'Anjou
Posted on  by  from the site Ninja Verification
This is the best rant on the demise of the goto statement I have ever heard. It is from the Tango conference 2008 - Fibers talk by Mikola Lysenko. If you fast forward to 23 min 05 secs, you will hear this: One way you can think about states [in a state machine] is that they’re [...]
Martin d'Anjou
Posted on  by  from the site Ninja Verification
If you use GNU Make in your verification environment, maybe you have dreamed of typing make -j 120. It turns out it is possible, and it is a very interesting use of the GNU Make SHELL variable. You know that make -j N causes GNU make to spawn the build of N prerequisites in parallel. [...]
Martin d'Anjou
Posted on  by  from the site Ninja Verification
A sentence in an article by Joel Spolsky caught my attention: “Can’t we just default to IE7 mode? One line of code … Zip! Solved!”. This is the typical necessary solution that quadruples the testing effort. If you though it only doubled the testing, think again. Let’s examine this in detail. First we have the code: ... // [...]
Martin d'Anjou
Syndicate content