Agile Manifesto put to test

Keith Braithwaite Zuhlke Engineering

In 1848 Marx and Engels created the exemplar of a “Manifesto” , a document meant to collate and summarise the thoughts of a movement. If you wanted to know what a Communist could be expected to think, or do, you could look in the Manifesto. So it is with the various Manifesto's we have in the IT industry. I you want to know how an Agile developer should behave you can look at the manifesto. As with the Communist Manifesto the Agile Manifesto can be considered a critique of and a response to industrial conditions in a certain time and place. What does that tell us about the recommendations in that Manifesto? Do those conditions still apply? How has current good practice changed? What guidance can this model provide for what comes next?

Polygot Programming Panel on .NET Rocks Live!

Richard Campbell Telerik Carl Franklin Pwop Studios

Join Carl and Richard from .NET Rocks as they talk to a diverse group of experts for a panel discussion about the current diversity of programming languages in the development community today. The panellists cover the spectrum of language experience, so no stone should be left unturned. What’s the state of the .NET and Java platform? Where are dynamic languages going? How will multicore processors effect languages in the future? Bring your own questions and be part of a .NET Rocks episode!

Rethinking Enterprise

Ted Neward Neward & Associates

The era of the big, heavy, transactionally-oriented client/server topology, as best described by the J2EE Specification and Blueprints document, seems to be over. The era of the lightweight, transactionally-oriented client/server topology seems to be at its zenith. Is this really where we want to be when building enterprise systems? And how did we end up here, anyway? What's the new "enterprise" developer supposed to do?