Little Architecture Huddle

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

" Mike Rozlog discusses the need for software audits, proposing five code reviews that every developer should use: Numerical Literal, String Literal, god Method, Shotgun Surgery and Duplicate Code. "

" Mike Lee considers that a software engineer makes great applications not because he follows good rules but because he has a better way of looking at the world and he learns from experience. "

"If your team develops software through agile methodology, taking a whole-team approach is vital to getting the most out of agile practices. RelatedVendorContent Kanban for Agile Teams 3 Companies Share how they Implemented a more Collaborative Process to Deliver Software Quality Avoiding Mediocrity in Agile Adoption to Produce Tangible ROI Immediately Ten steps to better requirements management The Agile Tester Related Sponsor In today's hyper-competitive world, later may be too late to adopt Agile development and this Roadmap for Success will help you get started. Download "Agile Development: A Manager's Roadmap for Success" now! Whole-team approach - the agile practice in which the entire team works as a unit of generalizing specialists to share responsibility for producing high-quality software - is a kind of "glue" practice: It holds a lot of the other agile practices together. For example, whole-team approach is #1 on Lisa Crispin and Janet Gregory's list of "key success factors" for agile testing."

" Kevlin Henney promotes live architecture through refactoring, recovery, re-envisioning, retrospection, re-engineering, repair, rewriting, reduction, reuse, reaction, re-evaluation and remembering. "

"Traditional contract models were designed for commoditized products and services. They are brittle and do not readily embrace change. This is because the products and services are defined upfront, and any change to this definition requires an amendment to the contract, which is usually governed by the change control mechanism. Instead of the change control mechanism embracing change, it is generally regarded as fettering and inhibiting change."

" John Davies addresses some of the difficulties dealing with FIX, FpML, SWIFT and integration in financial services software industry, challenging some of the canonical models existing today. "

"When building larger scale applications, message queues are often very helpful for both distributing and aggregating workloads. Distributed workloads are a natural fit for message queues, simply having multiple readers attached to the same queue is often enough. Aggregation, usually implemented with one reader and multiple writers, is used to bundle lots of small updates into a large block. This facilitates the use of advanced database techniques such as the use bulk inserts instead of individual insert/update statements."

" Ulf Wiger advocates for a programming model change based on the actor model which more accurately reflects old human concurrency patterns that we have used in our daily lives for thousands of years. "

" Stuart Halloway discusses how we use a total control time model, proposing a different one that represents the world more accurately helping to solve some of the concurrency and parallelism problems. "

"It looks like that CQRS has finally "made it" as a full blown "best practice". Please accept my apologies for my part in the overly-complex software being created because of it."

" I've been hearing from people that have had a great deal of success using the Domain Event pattern and the infrastructure I previously provided for it in Domain Events - Take 2. I'm happy to say that I've got an improvement that I think you'll like. The main change is that now we'll be taking an approach that is reminiscent to how events are published in NServiceBus."

"The purpose of this post is to provide an introduction to the Model-View-ViewModel (MVVM) pattern. While I've participated in lots of discussions online about MVVM, it occurred to me that beginners who are learning the pattern have very little to go on and a lot of conflicting resources to wade through in order to try to implement it in their own code. I am not trying to introduce dogma but wanted to pull together key concepts in a single post to make it easy and straightforward to understand the value of the pattern and how it can be implemented. MVVM is really far simpler than people make it out to be. "

"The purpose of this post is to provide an introduction to the Model-View-ViewModel (MVVM) pattern. While I've participated in lots of discussions online about MVVM, it occurred to me that beginners who are learning the pattern have very little to go on and a lot of conflicting resources to wade through in order to try to implement it in their own code. I am not trying to introduce dogma but wanted to pull together key concepts in a single post to make it easy and straightforward to understand the value of the pattern and how it can be implemented. MVVM is really far simpler than people make it out to be. "

" Billy Newport explains the fundamental differences between SQL and NoSQL, creating awareness that NoSQL is not suited for many cases, and people should make informed decisions before buying into it. "

"SourceMaking - is the best information source on the Web on such software development topics as design patterns, refactoring and UML. A lot of information freely available through the site's pages, so feel free to use bookmarklet to leave interesting chapters for further reading. You may start browsing the site by following one of these topics:"

" Guy L. Steele Jr. believes that it should not be the programmer's job to think about parallelism, but languages should provide ways to transparently run tasks in parallel. This requires a new approach in building languages supporting algorithms built on independence and build-and-conquer principles rather than on linear decomposition of problems. "

" In this interview Ryan discusses Clojure with author Chris Houser. They cover Clojure's approach to classes, comparing and contrasting it with Java. Chris delves into they type of programming problem sets Clojure is best suited for, especially in relation to parallelism as the number of cores in computers increases and Clojure's applicability as or research language. "