BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Agile Content on InfoQ

  • Book Excerpt: Practices of an Agile Developer

    This book collects the personal habits, ideas, and approaches of successful agile software developers and presents them in a series of short, easy-to-digest tips. Practical and focused, it offers proven and effective agile practices to make the reader a better developer. InfoQ.com brings you an excerpt, "Chapter 7: Agile Debugging," as a free pdf download.

  • Top 8 SOA Adoption Pitfalls

    Thomas Erl is the world's top-selling SOA author. He has written two books on SOA. Understanding the pitfalls others have fallen victim to will help you chart a safer route down your own SOA roadmap. To this end Thomas has collected the eight most common SOA adoption pitfalls of last year.

  • Book Review: Collaboration Explained: Facilitation skills for software project leaders

    David Spann, himself an experienced facilitator, provides an insightful review of "Collaboration Explained: Facilitation Skills for Software Project Leaders" by Jean Tabaka. Jean, an experienced teacher, consultant and coach, offers techniques to enhance group effectiveness, provides some templates to assure their first efforts are well planned, and tells some great stories along the way.

  • Book Review: Agile Java Development with Spring, Hibernate and Eclipse.

    Anil Hemrajani relates Agile practices to Java and several open source toolsets (Spring, Hibernate, Eclipse) designed to make Java development simpler. It's a high level overview of some free technologies used in web app development. Matt Morton liked this book, recommending it to technical managers and intermediate developers in small Java web development shops.

  • SOA anti-patterns

    SOA Expert Steve Jones from CapGemini provides a hands on look at SOA Antipatterns and a list of ways your SOA project can go wrong. This list includes signs that these problems are cropping up as well as what to do when you see them happening.

  • 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.

  • 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.

  • What is Agility, and Why Should You Care?

    Coach Mishkin Berteig introduces the benefits of Agility with two stories of highly responsive teams, and outlines some further reading. Agile helps people work more effectively by empowering teams, amplifying learning and eliminating waste. Agility teaches the team to modify its own working process over time, always with a view to providing more value to the enterprise while reducing waste.

  • 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

  • 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.

  • Being Agile Without Going Overboard

    Agile Software Development is gaining popularity. But, what does it mean to be agile? Is it using unit testing, continuous integration, following XP, Scrum? In this article Venkat Subramaniam discusses how to incrementally introduce agility into a project which is in trouble and not currently agile.

BT