I recently had the pleasure of seeing Guy Currier, of Ziff-Davis Enterprise, give a talk about their research on spending.  His approach seemed more like an engineering analysis than what I've come to expect from a survey-based researcher. And that is a GOOD thing.

The breath of fresh air in his presentation was simple: he had "confidence factors" or "proposed adjustments" for survey results based

I am currently developing a tool for executing UML models as an add-in for Enterprise Architect. The way it works is a modeler uses a formal language (something similar to JavaScript) to specify behaviors of operations in class diagrams, and an interpreter run the model. In this blog post I talk a bit about the design problem of relating class diagram relationships to a formal syntax and semantics.

 

written by Robert Brotherus, March 16, 2009 
So here's another attempt at a more condensed xml-version of the battle-data: 

<Battle width="500" height="500" >
  <Side General="Abrams">

  <Tank Type="Sherman" Count="6" Tactics="Tactics1"> 

  ... 
  </Side> 
  <Side> 
... 
  </Side> 
</Battle>

 

I assume this is what you were looking for?

I agree, it's rather nicer than that expanded format I used. So how does

You might have noticed my blogging is slowing down a little,  in case you're wondering the culprit is xsights - As we're getting closer to
production (2-3 weeks if all goes well) everything else slows down...

We all know about continuous integration (CI). We (xsights) are seeing a lot of ROI on the investments we made into signing up to CI esp. when we augmented by automated

At the risk of sharing some self-serving factoids, I nonetheless found the results of uTest 's social networking Bug Battle interesting. In all, 1,119 testers (using uTest tools) from 64 countries around the world competed in the quarterly contest to find bugs in the three top social networking platforms -- Facebook, LinkedIn and MySpace.

In my last post, I mentioned a Usenet discussion about continue statements and their relation to goto statements, and said that almost none of the responses to that post went beyond the responders' personal opinions.  The comments associated with that post that post mostly repeated the pattern of the Usenet discussion: They did not go much beyond stating the commenters' opinions.

One of the

Rails 2.3 is out (actually, 2.3.2). I thought I'd take a few quick moments to summarize for DDJ readers the new and noteworthy features that make this a stellar release.

Against a student's faulty program, I might scrawl "infinite loop" or "uninitialised variable". Against a broken SF story, a Turkey City Lexicon reader might scrawl "Cozy Catastrophe", "Signal from Fred", or "Squid in the Mouth". Or "AM/FM". The classic AM/FM story must be Heinlein's The Day After Tomorrow: six men in an underground citadel, sole remnant of the US Army after invasion by the PanAsian Empire, take up a dead colleague's discovery of the electrogravitic spectrum, the magnetogravitic spectrum, and the electromagnetogravitic spectrum. Maxwell via Hertz to tractor beams and transmutation in a month: ultimate humiliation of the PanAsians, and I wish my hardware behaved like F*ck*ng Magic rather than the backlash and hysteresis of Actual Machinery. So, and with last week's Murphy's Law comments in mind, I want to point you at a very non-AM/FM short story that I was pleased to rediscover online: M.I. Mayfield's On Handling the Data.