InfoQ Homepage Design Content on InfoQ
-
Using Design Thinking to Stop Building Worthless Software
Jeff Patton outlines the concepts behind design thinking: clear problem definition, ideation, iteration, and execution plans that emphasize continuous learning, accompanied by real-life examples.
-
The Code is the Design
Mark Haskamp supports the idea that source code is the design blueprint and the entire documentation of a software product.
-
Parallel Programming Patterns: Data Parallelism
Ralph Johnson presents several data parallelism patterns, including related Java, C# and C++ libraries from Intel and Microsoft, comparing it with other forms of parallelism such as actor programming.
-
Savara - Formally Verifying SOA Designs Against Requirements
Steve Ross-Talbot presents Savara, comprising a set of tools enabling enterprise architects to validate various artifacts against other artifacts based on the “Testable Architecture” methodology.
-
Immutable Object vs. Unsynchronized State
Joshua Bennett discusses immutable objects, what they are good for, when they are recommended to be used and when are to be avoided.
-
Parallel Programming Patterns: Data Parallelism
Ralph Johnson presents several data parallelism patterns, including related libraries from Intel and Microsoft, comparing it with other forms of parallel programming such as actor programming.
-
Webmail for Millions, Powered by Erlang
Scott Lystig Fritchie presents the architecture and lessons learned implementing a webmail system in Erlang, using UBF and Hibari, a distributed key-value store, to accommodate a large user base.
-
QCon Keynote: Forty Years of Fun with Computers
Dan Ingalls presents his journey through the world of software developing a number of core technologies over the last forty years, explaining what brought them forth and why they are fun even today.
-
RESTful SOA or Domain-Driven Design - A Compromise?
Vaughn Vernon advocates using DDD’s strategic modeling patterns when integrating services in a RESTful SOA implementation, avoiding one of SOA’s pitfalls: focusing on services rather than the domain.
-
Abstractions at Scale–Our Experiences at Twitter
Marius Eriksen considers that leaky abstractions lead to scalability issues, while those providing narrow access to explicit resources - map-reduce, shared-nothing web apps, big table - scale better.
-
Simplicity, The Way of the Unusual Architect
Dan North talks about the tendency of developers-becoming-architects to create complex systems. He argues for simplicity and offers strategies to extract the simple essence from complex situations.
-
Patterns for the People
Kevlin Henney proposes a new look at design patterns from the perspective of the habitability of code, communication, exploration, empiricism, reasoning, incremental development, and design sharing.