Hexagonal Housing
Hexagonal Housing
Hexagonal Housing
CHAPTER 1
INTRODUCTION
GENERAL
In the realm of urban design, hexagonal planning is today virtually an unknown
phenomenon, a mere oddity among a vast array of ideologies, theories and methods.
It regularly goes unnoticed by students of city planning and urban history. Yet, for a
period of almost 30 years, between 1904 and 1934, it caught the attention of various
planners, engineers and architects who saw in it a promising panacea for the city’s
planning ills and a replacement for the uniform rectangular street grid. Striving to
establish visionary and idealistic schemes for a perfect physical environment that
would also improve social conditions, these individuals advocated their ideas in
papers and professional presentations for over a quarter of a century. Yet none were
able to build their plans on a large scale. Why was this so? Was it because in reality,
as on paper, hexagons looked too far-fetched to be a workable solution? What about
the theory’s suggested cost-effectiveness and efficient land use pattern; were not
they an incentive for construction? Such idealized geometrical schemes for city
design often remained theoretical. There have been many more ideal cities on paper
than on the ground. When they were built, these ideal communities were often
short-lived in their pure state. They were overtaken by the reality of the way in
which people behave under normal conditions. As Lynch (1984, p. 48) suggested, ª
Settlement form is the spatial arrangement of persons doing things, the resulting
spatial wows of persons, goods, and information, and the physical features which
modify space in some way significant to those actions, including enclosures,
surfaces, channels, ambience, and objects.
Hexagonal Architecture is a form of application architecture that
promotes the separation of concerns through layers of responsibility.
Outside of the inner core you have layers of ports and adapters that
capture messages from the outside world and convert them to appropriate
procedures to be handled inside of the application. The resulting message
from the application is then passed back through this layer of ports and
adapters as an appropriate response.
This means the inner core of the application has no knowledge of the
outside world and so the direction of dependency will only flow outwards.