InfoQ Homepage Patterns Content on InfoQ
-
Mary-Lynn Manns on Fearless Change
Mary-Lynn discusses how Fearless Change presented patterns focused on the evangelist and the introduction of new change ideas into an organization. She goes on to note how the sequel, tentatively titled More Fearless Change, adds patterns that focus on gaining the necessary emotional and personal commitment to making change happen. She also talks about Agile and its adoption.
-
Mark Pollack on Spring.NET 1.3 and 2.0
Mark Pollack talks about the features coming in Spring.NET 1.3 and 2.0. He also covers Spring.NET Integration, the Stonehenge project and the relationship with Spring Java.
-
Ralph Johnson on Parallel Programming Patterns
Ralph Johnson, one of the four GoF authors, talks about the upcoming book “The Patterns for Parallel Programming”. He highlights the difficulties in dealing with discovering and writing down parallel programming patterns, how to choose and use such a pattern, and similarities with the initial Design Patterns book.
-
Joseph Yoder on Adaptive Object Model Architecture
In this interview Joseph Yoder talks about the Adaptive Object Model (AOM) architecture, a software architecture for easily adapting to changing business requirements.
-
Software Design Helps Being Agile
In this interview made by InfoQ’s Deborah Hartmann during Agile 2008, Rebecca Wirfs-Brock talks about software design, the need for good design and the technical debt that might accumulate slowing down the development process. The conclusion is that agile developers should not disregard design.
-
Greg Young Discusses State Transitions in Domain-Driven Design and DDD Best Practices
In this interview, Greg Young talks about managing state transitions in a Domain-Driven Design project using two separate models, one for reading data from datastore and the other for write-only command operations. He also discussed Command Query Separation to keep the design cleaner and easier to test and maintain and the best practices that developers can use when working on DDD projects.
-
Ian Robinson discusses REST, WS-* and Implementing an SOA
In this interview from QCon San Francisco 2008, Ian Robinson discusses REST vs. WS-*, REST contracts, WADL, how to approach company-wide SOA initiatives, how an SOA changes a company, SOA and Agile, tool support for REST, reuse and foreseeing client needs, versioning and the future of REST-based services in enterprise SOA development.
-
Pressure and Performance – The CTO's Dilemma
In this interview made by Deborah Hartmann during Agile 2008, Diana Larsen and Jim Shore talk about patterns observed in CTOs' activity. CTOs emerge as real people caring for other people in their organization, and are put under a lot of pressure and constraints.
-
Erich Gamma Discusses Jazz, Eclipse, JUnit and Design Patterns
In this interview from QCon London 2008, Erich Gamma discusses the Jazz project, why Eclipse has been successful, the strict Eclipse release schedule, JUnit, Design Patterns, how to identify a design pattern, design patterns and the 'Don't Repeat Yourself' principle, the design pattern community, and whether dependency injection is a design pattern.
-
Linda Rising on "Fearless Change" Patterns
In this interview made by Floyd Marinescu, co-founder of InfoQ, Linda Rising talks about the book "Fearless Change: Patterns for Introducing New Ideas" and offers examples of how the patterns presented in the book can ease the stress of Agile adoption.
-
Randy Shoup Discusses the eBay Architecture
In this interview from QCon San Francisco 2007, Randy Shoup discusses the architecture of eBay. Topics discussed include eBay's architectural principles, horizontal and vertical partitioning, ACID vs. BASE, handling data inconsistency, distributed caching, updating eBay on the fly, architectural and coding standards, eBay's search infrastructure, grid computing, and SOA.
-
Markus Voelter about Software Architecture Documentation
During OOPSLA 2007, InfoQ interviewed Markus Voelter asking him about creating software architecture documentation. Many people mention UML when they are asked about software design documentation, but Markus has a different take on that. He thinks that we should be using models which can be processed with tools which can validate or invalidate them.
