December 13, 2019

258 words 2 mins read

Software-defined culture

Software-defined culture

Conway's law tells us that "organizations which design systems. . .are constrained to produce designs which are copies of the communication structures of these organizations." What if we turn Conway's law around? Timothy Gross explores how to make technology choices that improve the culture of your organization.

Talk Title Software-defined culture
Speakers Timothy Gross (Joyent)
Conference O’Reilly Velocity Conference
Conf Tag Build Resilient Distributed Systems
Location San Jose, California
Date June 20-22, 2017
URL Talk Page
Slides Talk Slides
Video

Conway’s law tells us that “organizations which design systems. . .are constrained to produce designs which are copies of the communication structures of these organizations.” Unhealthy organizations “ship the org chart,” producing software that reflects dysfunctional practices. When organizations are healthy and dynamic, adaptability and high-quality software result. What if we turn Conway’s law around? Can bad software choices create new rifts? Are we selecting tech that disempowers developers and keeps operations up at night? Is our software architecture secretly encoding new divisions between our teams? Can technology choices improve an organization’s culture? Drawing on his experience running containers in production, writing microservices, and operating all manner of infrastructure, from established favorites to the latest hipster trends, Timothy Gross explores how all the usual technological suspects (and maybe a few surprising ones) can shape the organizational culture in startups and enterprises alike and explains how to make technology choices that improve the culture of your organization. Timothy covers four principles for building software systems that have a positive influence on the culture of the organization that builds them:

comments powered by Disqus