Barbara Fusinska presents ideas and approaches for developing a system as a whole, explaining the latest patterns, practices and architectures used in modern day mobile and web offline apps.
Kevlin Henney examines seven coding habits that are not as effective as many programmers — whether working with Java, .NET, native or scripting languages — might believe, and suggests alternatives.
How Can We Use Our Creative Power and Technological Opportunity to Address the Challenges of the 21st Century?
Gyorgyi Galik discusses our urban future and explores new possibilities to create projects and materials that change the environmental effects of art and design practices.
Deepak Nadig discusses how PayPal’s API Platform evolved both internally and externally, the principles and patterns used, and how it is enabling the future of Money.
Jutta Eckstein discusses how pedagogical patterns and corresponding tools can help individuals improve themselves, making them better mentors and therefore help their teams improve continuously.
Gareth Rushgrove explores patterns and practices useful to implement continuous integration in an infrastructure-as-code environment.
Mike Amundsen reviews patterns in developer practices and trends in services and libraries that emphasize the idea that in the end "Clients Matter, Services Don't".
Kurt Schrader explores patterns and practices used to build polyglot projects, when to add a new language and what to do when things seem to get out of hand.
Oliver Gierke introduces Spring Data repositories along with best practices and implementation patterns, followed by guidelines for integrating repositories with Spring MVC and REST web services.
Roman Pichler shares insight on Agile practices that can improve innovation, discussing the innovation stages and how product ownership, process, and project setup are influenced by uncertainty.
Christof Ebert discusses technical debt including a Netscape vs. IE case study and provides a framework with practices for managing technical debt.
John Allspaw discusses pitfalls to be avoided while troubleshooting failed systems, comparing web operations at scale with practices in aviation and nuclear power industries.