martinfowler.com, as data

Software development is a young profession, and we are still learning theIf there's a theme that runs through my work and writing on this site,it's the interplay between the shift towards agile thinking and thetechnical patterns and practices that make agile software developmentpractical. While specifics of technology change rapidly in ourprofession, fundamental practices and patterns are more stable. Sowriting about these allows me to have articles on this site that areseveral years old but still as relevant as when they were written.As software becomes more critical to modern business, software needs tobe able to react quickly to changes, allowing new features to beconceived, developed and put into production rapidly. The techniques ofagile software development began in the 1990sand became steadily more popular in the last decade. They focus on aflexible approach to planning, which allows software products to changedirection as the users' needs change and as product managers learn moreabout how to make their users effective. While widely accepted now, agileapproaches are not easy, requiring significant skills for a team, but moreimportantly a culture of open collaboration both within the team and with aThis need to respond fluently to changes has an important impact uponthe architecture of a software system. Thesoftware needs to be built in such a way that it is able to adapt tounexpected changes in features. One of the most important ways to do thisis to write clear code, making it easy to understand what the programis supposed to do. This code should be divided into modules which allowdevelopers to understand only the parts of the system they need to make achange. This production code should be supported with automated tests thatcan detect any errors made when making a change while providing examplesof how internal structures are used. Large and complex software effortsmay find the microservices architectural style