I wonder, why do we bother testing our software? 1 accepted (postponed to after an imminent release), 1 assigned, 11 closed (only 3 after the testing took place; of these one closed with wontfix), and 40 open issues (14 of which are from the last testing cycle). […]
So, I’m making a presentation. In a brief moment of inspiration ((I was drunk.)), I managed to not only come up with one good name, but 4. They are all descriptive of the presentation, so now I need your help in deciding which one to go with: […]
Last night, I has a horrible nightmare. I had the gadgunchies ((Portmanteau of “gadgets” and “munchies”, being the scientific (not scientific, I totally just made it up myself) term for an all-consiming craving for getting new gadgets.)), but unfortunately, it was Sunday and all shops were closed, so I couldn’t satisfy the beast within. In […]
So, this is my overview slide for a presentation at the end of the month: A little boring, at little barren… Then, BAM ((They won’t know what hit them…)): gratuitous titstank: Yeah, it’s Friday and I’m presently easily amused… […]
So, I guess, now we know how Duke Nukem Forever got its name; it’s not about the development cycle, but rather about the download time… (And it’s not the connection; it should be able to download around 20 times faster than that…) […]
We’re using Hudson ((Though it has been renamed to Jenkins for stupid reasons.)) at work for continuous integration. The setup of dependency detection is less than optimal, though, which is reflected in my commit comments (I’m, mwesterg): […]