Pace Layers: What Urban Planning Knows About Your Software Boundaries
A boundary rule stolen from urban planning: sort by rate of change, push irreversibility down, point dependencies at the slow layer.
Architects across different subject areas - like civil engineers, urban planners, and hardware designers spent decades on problems we keep rediscovering every few years under new names. The habit of looking sideways at “older” or, simply, “other” disciplines and asking what they have already solved has done no less for my architectural instincts than any single framework. Learn to spot the borrowings and steal them well, and you get better at the job in a way that outlasts whatever stack you're on this year.
This isn't my first time leaning on that habit in public. I once wrote about how mental models and mathematics helped me design a hotel room-cleaning scheduler— the solution only clicked after I looked at how IMDb ranks its Top 250 and how CSS...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
