InfoQ Homepage Methodologies Content on InfoQ
-
Drunken Stumble: The Correct Way To Build Software
Garrett Smith introduces Drunken Stumble, a development method in two stages: a lean, which represents the goal of the programmer or team, and a stumble, which is a series of automatic "next steps".
-
Making Eclipse IDE Better at Handling Real-life Projects
Mickael Istria showcases a number of extensions to the Eclipse IDE making it easier to import projects (simple or complex) and honoring modularity in the Project Explorer.
-
The Power of Hope: Getting You from Here to There
Portia Tung discusses the concept of Hope, trying to help us better understand the relationship with Hope and figure out how to achieve even our most ambitious of goals.
-
The Sweet Spot
Alberto Brandolini discusses how the Theory of Constraints, Kanban, CQRS, Domain-Driven Design, EventStorming and UX blend together to solve the real problems in software development.
-
Naming Things
Ian Barber discusses the importance of behavior, domains and clarity of the names used when writing software or building systems.
-
So You Think You Know Pub/Sub?
Udi Dahan takes a look at why different kinds of pub/sub need to be used for specific domains like healthcare, finance, “internet of things”, and some kinds of retail.
-
Good Design Is Imperfect Design
Eric Evans discusses how to create good or even great designs with DDD without attempting to be perfect.
-
SOLID: The Next Step Is Functional
Anil Wadghule explains why applying SOLID OO design principles to their extreme leads to Functional Programming.
-
An Architect’s World View
Colin Garlick presents a foundation of value for the practice of architecture, starting with the values that architecture is established on, showing what's important for an architecture.
-
Stuff I Learned about Performance
Mike Barker shares lessons learned at LMAX Exchange: starting from a clean domain model is imperative and understanding the trade-offs between performance and safety/generality/functionality.
-
Worse Is Better, for Better or Worse
Kevlin Henney revisits the original premise and definition of “Worse is Better”, and looks at how this approach to development can still teach something surprising and new.
-
Keep Things Simple
David Tanzer, Oliver Zymanski explain with examples how to apply the rules and principles of object-oriented software design to create simple architectural designs.