Tracking change and innovation in the enterprise software development community
JProbe Freeware,
an Eclipse plug-in,
diagnoses
memory issues
quickly & easily.
QCon San Francisco
Nov 19-21:
+ 80 sessions & tracks
Register now
and Save $400!
IBM WebSphere
Virtualize apps
to lower costs,
Increase agility
Learn more!
Terracotta:
Scale your
Apps w/ease
Offload the DB:
Learn More!
Debate sprang up at JAOO '07 around Bob Martin's assertion that "nowadays it is irresponsible for a developer to ship a line of code he has not executed in a unit test." In this InfoQ video, he debated with Jim Coplien on this and other topics, including Design by Contract vs. TDD and how much up-front architecture is needed to keep a system consistent with the business domain model.
Declan Whelan wrote a thought-provoking blog citing an idea he learned from Mishkin Berteig about an (unspoken) principle behind successful Agile teams: truthfulness. The idea is simple: without individuals being honest and open, most agile practices will not work.
In a recent post, Michael Feathers argues against the widely held idea that unit testing, by itself, improves code quality. Michael talks about unit testing, integration tests, TDD and Clean Room Software Development, concluding that code quality is a function of thought and reflection, not bug prevention.
The involvement of customer in an Agile project is taken for granted, however in many situations, intentionally or unintentionally, the customer may not follow the Agile practices. An interesting discussion on the Extreme Programming group tries to decipher the situation and find possible solutions.
Can refactoring and unit testing really create robust “working software” that survives the real world? In this story adapted from his book Release It! Michael Nygard contends that "abstractions leak": we need to attend to architecture, even in Agile projects, to guard ourselves against the 5AM failures that occur when foundational abstractions misbehave.
John Harby is a participant in several OASIS Technical Committees and was co-author of The Middleware Company SOA Blueprints initiative. He is an independent consultant on SOA and middleware in Enterprise scale projects. John writes about problems with the ESB pattern including vendor lock-in, centralization and feature overkill. In this article, John proposes an alternative capability.
Use of Agile methodologies is growing, but this comes with its own challenges: including the possibility of dilution as teams copy practices rather than growing them, implementing them without understanding. Perhaps it's time to talk about how failure to teach the basics puts much at risk: the integrity and engagement of team members, and the trust of their customers.
At QconLondon 2007 Jim Coplien spoke with "Pragmatic" Dave Thomas for InfoQ. This energetic 30-minute interview runs the gamut of Dave's wide-ranging interests: 'agile' publishing; how to turn what you love doing into a book; programming (and methodology) monocultures; staying limber with code "katas"; and advice for academics: help your students live with the passion of a 5-year old!
Zed Shaw and Matt Pelletier sat down with InfoQ's Obie Fernandez at RailsConf to explore some of the reasoning behind setting up the mongrel project, getting adoption in enterprise and dealing with developers who just aren't ready. Watch the interview to find out how much Shaw's Enterprise Mongrel product will cost, where the support contracts are and who'll come out on top when the vultures land.
