InfoQ Homepage Design Content on InfoQ
-
Refactor or Rewrite?
The goal of refactoring and rewriting is to improve the sanity of the system by improving the code readability, structure and clarity. A clean code would be easier to maintain and enhance. However, on many occasions Agile teams have a tough time deciding between the two.
-
SOA as an Ecosystem
Today’s enterprise is always a part of a larger ecosystem including its buyers and suppliers. In his new post, Richard Veryard describes how this ecosystem should be reflected in a SOA design.
-
Where has the innovation gone?
Some commentators are questioning the level of innovation happening in the Agile space. Does iterative and incremental development lead us away from innovation towards reusing old solutions, building on what we already know rather than creating truly "out of the box" solutions. Adding an R&D stream is suggested as a way to bring innovation into Agile projects.
-
Enabling the Last Responsible Moment in Deployment
An interesting question can be asked during a design decision: "Does this approach create a commitment" rather than "is this the right design?". A conversation on the KanbanDev Yahoo! group explores this question, different approaches to implement an effective answer, and the benefits to be reaped by this approach.
-
Is CRUD Bad for REST?
In his new post, Arnon Rotem-Gal-Oz explains that REST is more than just a set of standards and APIs, and it requires following REST architectural principles for reaping its complete benefits.
-
How Relevant Is Contract First Development Using Angle Brackets?
Christian Weyer of Thinktecture, announced the release of WSCF.blue a Visual Studio Add-in that enables contract first development of web services using WCF.
-
Stop and Refactor?
When should you refactor? There are times when you simply need to pay down technical debt - you should stop and refactor. No, you should only refactor when one is working on a User Story. Which advice is best? Is there, perhaps, a third option?
-
Design Characteristics Of Resource Oriented Server Frameworks
Dhananjay Nene, who has also written a nice article that chronicles the history of REST, examines the various characteristics to be expected when designing a server side Resource Oriented Framework (ROF). The article also attempts to capture the relationship with a fine grained object model of an application and its’ resource model.
-
REST is a style -- WOA is the architecture.
Dion Hinchcliffe discusses Web Architecture and the relationship of REST practices and principles in the construction of a Web Oriented Architecture (WOA). The relationship between WOA and SOA is also explored.
-
Presentation: Kent Beck on Responsive Design
Purpose and intent are just as important as skill in effective software development. Skill allows you to deliver value in difficult technical circumstances. Clear purpose and positive intent allow you to deliver value in difficult social and business circumstances. Kent Beck shares his design technique which involves both intent and a small set of strategies he uses when designing.
-
Article: Chunk Cloud Computing
In this article, Jimmy Nilsson describes an architectural style that he has observed slowly growing in popularity over the last few years, a style that he calls Chunk Cloud Computing.
-
Presentation: The Joys and Pains of a Long Lived Codebase
In this presentation recorded at QCon SF 2008, Jeremy D. Miller shares lessons learned while developing a project over 5 years. He talks about his mistakes, what to avoid and how to design, code and test better.
-
REST – The Good, the Bad and the Ugly
There are endless debates in the industry and among developers on merits and drawbacks of REST. A new post by Arnon Rotem-Gal-Oz provides some thoughts on both REST’s “goodness” and “badness”.
-
Presentation: Meeting the Challenge of Simplicity
This session addresses the abstract notion of simplicity, looks at why it is critical in modern UI design and answers questions: Why does simplicity matter? Is there a meaningful definition of simplicity? Why do design processes and good intentions undermine simplicity? What processes and techniques can software developers use to achieve simplicity?
-
Presentation: Practice-based Design: Some Object Lessons
In this OOPSLA 2008 session, Lucy Suchman teaches 8 lessons about objects: Learning to see, Classification, Object Agencies, Configurations, Boundaries and Interfaces, Contextualizations, Recontextualizations, and Transformations, showing how they can influence design.