It was recently announced that InfoQ is creating a new Operations community. In addition to that, another major change which has been in the works for the last few months at InfoQ is the conversion of the Java community to the Scala community. InfoQ spoke with a prominent Scala expert and members of the former InfoQ Java editorial team to learn more about this change and why it was made.
An IT services provider company has migrated an ERP application totaling 950,000 lines of VB6 code to .NET in 9 months.
During his Devoxx talk, Mark Reinhold has announced that JDK 7 will have Closures. With the inclusion of this much debated feature, JDK 7 schedule will be extended until around September 2010.
Scala has been receiving much attention lately as a possible candidate to replace Java in the future. James Strachan creator of Groovy advocates in favor of Scala as James Gosling, creator of Java and Charles Nutter JRuby Core Developer, have done in the past.
During the NACA project run by Publicitas Ltd., 4m lines of COBOL were automatically trans-coded (migrated) toward their Java equivalent. The company claims that the recurrent annual savings in cash-outs amount to a total of 3m euros and has released the tools from the NACA project under GPL.
The state of the art in political technology evolved radically 2004-2008. In 2004, software development in Democratic political campaigns consisted of a few rag-tag hackers taking shots in the dark and building applications. In 2008, political start-ups built innovative social applications that raised nearly 1/2 billion dollars, and elected a President.
Part of a development team has been laid off, the team is down to four developers with a part time Scrum Master and no dedicated Product Owner. Is Scrum still applicable? What options are there? How does one adapt?
Advice from Esther Derby, George Dinwiddie, Jo Geske, Mike Sutton and Ilja Preuss on how to make retrospectives better. The ideas include tips for the facilitator/Scrum Master and new ways to use the burndown chart.
Any change whether an Agile implementation or re-arranging the office furniture is going to encounter some resistance. The real question is how we react when that happens. Dave Nicolette and Lasse Koskela's workshop - was designed too help us understand where resistance comes from and how to handle it.
Software development is Hard. One of the main reasons is that it is a complex adaptive system. Agile - when done right - seems to do a very good job of providing stabilizing feedback. We take a look at what it means for something to be a 'complex adaptive system' and what particular practices in Agile help us out.
Whether deep inside the brain, within software, or even within the teams which develop software, how do processes work, how do they misfire, and how can they be altered to achieve the desired results?
Sometimes teams have trouble starting new habits: writing unit tests, fix compiler warnings, not breaking the build. How do we help the team change these habits? Clint Shank designed a game to help people transition.
Greg Smith offers an in-depth practical perspective on making your agile transition just as much about culture change as it is about process change.
Joseph Pelrine has come full circle: from university studies in Psychology, journeying through SmallTalk, XP and Scrum, and now back to broader questions: Why and how does Agile work? In this interview, Joseph talked about Complexity Science, and how story-telling, "sense-making," network analysis and speed-dating's gut-feel approach may prove more useful than our old toolkits for managing teams.
Even the very greenest of agile teams clearly recognize the word 'Retrospective'. But, alas, it is often overlooked that a retrospective may be a wasted effort if not used to initiate an actual improvement that the team follows through on. Jim Shore gives advice on how to make the most of your retrospective and reminds us of the activity's ultimate place in the agile heartbeat.