Through teamwork, an agile team can ensure the quality of its project's architecture, code hygiene, and other non-functional requirements by explicitly creating tasks for those concepts in each sprint. Alexander von Zitzewitz explains the importance of this method of agile development and how the use static analysis of code bases can help the "hard sell" of intentional architecture to management.
Learning from past projects, Jeff Gothelf helped synthesize Lean UX into a growing practice within software firms of all sizes, where teams focus on project outcomes and not output. When teams of varying competencies are brought together from the beginning of a project and given ownership, they are able to take responsibility for delivering a great client experience.
Jeff Patton helps teams build better products by helping them understand their users in a more thoughtful manner. By using the principles of comaking, teams begin to take more responsibility for their projects and their outcomes, thereby creating a more streamlined process of meeting their users' needs and having fun while doing it.
Sadek talks about the origins of Playframework, motivations behind 2.0 rewrite and Scala integration. He explains how important is it to have appropriate architecture and programming model while dealing with Realtime. He then reveals some features of the newly released 2.1 version.
In this InfoQ interview, Michael Nygard explores some of the available loopholes in the CAP theorem helping architects to engineer distributed systems that meet their needs. He also discusses new patterns he’s observed since his book, Realease IT and shares his thoughts on continuous delivery, DevOps and ALM.
Jeff talks about the powerful features that come with Grails 2 and how it can be used as a rapid application development framework. He also compares it with Rails and Django and explains how it can be combined with other components from the Spring portfolio.
Ian Robinson discusses Neo4J's design choices for data storage and retrieval, CRUD operations, transactions, graph traversal and searches and HA deployment strategies. He also shares his thoughts on hypermedia controls and the concept of consumer driven contracts for continuous evolution of services.
In this interview we talk with Adrian Cockcroft, the architect for Netflix’s cloud systems team. We discuss how Netflix combines 300 loosely coupled services across 10,000 machines. An interesting revelation is that they fully embrace continuous delivery and each team is allowed to deploy new versions of their service whenever they want.
Enda talks about the challenges his team faced while developing the Enyo framework. He also gives an overview of how it works and how it aims to help developers deliver apps across different devices.