Dan North talks about the tendency developers-becoming-architects have to create bigger and more complex systems. Without trying to be simplistic, North argues for simplicity, offering strategies to extract the simple essence from complex situations.
This week, the fourth annual QCon London is in progress. Starting on March 8th with tutorials and ending on March 12th with a "meet the speakers" social, there will be a lot happening. This article describes the many ways that readers can follow along with the events at QCon as they are happening.
This article presents the main takeway points as seen by the many attendees who blogged about QCon. Comments are organized by tracks and sessions: Keynotes, Tutorials, 2015 Software Development, Agile Evolution, AlphaGeeks on .NET, Architectures You've Always Wondered About, Pragmatic Cloud Computing, Cool Stuff with Java, Dev and Ops: A single team, Software Craftsmanship, NoSQL and many more!
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.
Ian Robinson considers that programming for the web requires a different architectural approach than for applications: clients are interested only in URIs, clients are responsible for the integrity of a sequence of requests, and one should implement application protocols as protocol resources , not domain resources.
Aino Vonge Corry reviews a number of well known design patterns showing that their implementation is simpler in functional languages because such languages have pattern-based constructs.
Ralph Johnson and Joe Armstrong discuss their ideas about parallel programming - whether shared memory is harmful, the place of message passing, fault tolerance, the importance of protocols and more.
Ralph Johnson and Joe Armstrong discuss the state of OOP, what Smalltalk got right/wrong and the image concept. Also: Joe decides he likes OOP as long as its done the Erlang way: focused on messaging.
Dan Ingalls explains the ideas that went into Smalltalk, how it was developed at Xerox PARC, the ideas that went into Squeak, and his latest project the browser-based Lively Kernel.
