InfoQ Homepage Troubleshooting Content on InfoQ


RSS Feed
  • LINQ To Logs And Traces

    Microsoft Open Technologies recently announced the release of Tx, an open source project that can help debugging using Logs/Traces, and building of real-time monitoring and alerting systems.

  • Fiddler Web Debugging Proxy

    Fiddler is a free proxy that logs HTTP(S) traffic, allowing developers to inspect requests and responses, set breakpoints, and tamper with incoming or outgoing data. Fiddler also includes an event-based scripting subsystem and can be extended using any .NET language. A simple but powerful example of Fiddler's utility can be seen when trying to get a complete view of a site's AJAX traffic.

  • Open Source Troubleshooting for Java

    VisualVM is an OpenJDK project from Sun to create an all-in-one troubleshooting tool for Java applications. The tool is a combination of several existing tools and newer profiling capabilities.

  • Are there weaknesses with Collective Code Ownership?

    The Agile development community has been practicing Collective Code Ownership for long enough now that we had enough time to find some of the faults.

  • Explicit vs. concise code in Ruby

    Ruby offers many ways of reducing code size. However, this can backfire in some situations. We look at one problem with Ruby's method for identifying nil and false values.

  • Presentation: Maintaining Java Apps in Production Environments

    Alexandre Rafalovitch delivers an organized overview of the tools and techniques that help with resolving problems that arise in real production environments. The presentation places emphasis on free and open source tools capable of being useful out of the box, without extensive configuration. Common problems are discussed, along with methods of rapid analysis and root cause determination.

  • Rails Helps Service Survive Hawaii Earthquake, a document storage company successfully maintained all company services during Hawaii's recent earthquake. Among other factors, the company's leader credited their use of Ruby on Rails as part of their ability to stay up during the catastrophe.

  • No Bug Database?

    James Shore, a recognized speaker and writer in the Agile space, has had a crazy idea: Get rid of your bug database. He's not advocating that teams ignore problems; but bug databases are often so packed with questions, feature requests, and defects that there's little hope of their all being resolved. Shore and some others in Extreme Programming circles think there's a better way.

  • InfoQ Article: Exclusive Excerpt from Practices of an Agile Developer

    Andy Hunt, one of the originators of the Agile Manifesto, and Venkat Subramaniam have written a compilation of the habits, ideas, and approaches of successful Agile software developers in "Practices of an Agile Developer". InfoQ brings you a free excerpt on Agile Debugging.

  • Increase Your Personal Resilience to Change

    "Highly resilient people are best suited for a world of constant change. They don't fight against disruptive change... they adjust to new situations quickly." Sounds useful for members of Agile teams which want to "embrace change", even more so for those experiencing the drastic change from traditional to Agile methods. Bob Weinstein's article lists some ways to increase your own resiliency.

  • Series: Churchill, the Agile PM

    Mark Kozak-Holland is the author of the book "Churchill's Adaptive Enterprise: Lessons for Business Today". In his series, he studies Churchill's history and habits, and draws parallels between events in World War II and today's business challenges. In episode 2, Mr. Churchill inherits his "project" from hell...

  • Worth Repeating: The BigBook Technique

    Mark Hedlund has a favourite story: he tells of the BigBook Technique, a simple ploy engineers once used to communicate with their CEO about a death-march project. With yet another big-project implosion in the news, Hedlund felt the need to roll out this simple remedy, again. In effect: nine women simply cannot deliver a baby in one month. If that sounds familiar, this story may be of use to you.

  • Meeting the Challenge of Collective Code Ownership

    The challenge: find the balance between pure practice and local compromise. Martin Fowler has brought us a story of a team in trouble, which took a step back to improve coding discipline and brush up on the basic practices that support collective ownership. In addition to the short-term gains of increased velocity and improved morale, the overall quality of the team's output improved as well.


Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.