InfoQ Homepage Development Content on InfoQ
-
Dealing with Legacy Code
Here's a three-pronged attack to use on the legacy code that everyone eventually inherits: Build, Automate, Test. Use this BAT to create a safety net to ensure your code continues to work the way you want it to. Richardson shows how this helps quickly identify and eliminate unintended side effects. See how your day-to-day work compares, and see if you need to approach your work differently.
-
Evolutionary integration with ESBs
ESB Programming experts provide simple working examples and clearly communicated ideas and patterns using the open source Mule ESB tool set. These examples provide both working code as well as suggest a methodology of evolutionary integration which can be used to dramatically simplify and accelerate SOA integration.
-
Agile Asset Management with Ruby DSLs
Ruby makes it easy to craft Domain-Specific-Languages with Ruby syntax. This article is a story about the benefits derived from implementing a Ruby DSL for a PLANET ARGON development project.
-
Casestudy: Brasilian National Healthcare System
This casestudy takes a detailed look at the implementation and architecture behind the Brasilian National Healthcare System, a 2M line of code, truly mission critical Java application. Lessons learned, best practices, and details down to the interaction diagram are covered
-
Simple JAVA and .NET SOA interoperability
.NET and Java interop can be made really simple using a REST documentcentric approach. This article compares a REST and SOAP approach to interop as well as the advantages of using HTTP POST vs. GET for REST invocations.
-
Ruby and Rails: In your face... but out of your way
Ruby on Rails is in many ways a system in itself. But in many, many other ways, Rails exposes, explores, and exploits its connections to Ruby, rather than hiding or disguising them. David A. Black, author of the book Ruby for Rails from Manning, shares his thoughts on whether or not Rails developers should take the time to master Ruby.
-
.Net Exceptions - Tracking Down Where In The Code The Exceptions Occurred
Tess Ferrnandez, an escalation engineer in PSS (product support services) at Microsoft, outlines the procedure for tracking down where in your code an exception occurred by using a stack dump.