Lesson 0.1Lesson 0.1 · Designing Cities by Rule
From Drawing Cities to Growing Them
For most of history a city was either drawn by hand - a planner's grand plan set down street by street - or it grew organically over centuries without any single author; computational urbanism offers a third way, growing cities by RULE: parametric models whose whole plan re-forms when you turn a knob, and generative algorithms that propose and explore thousands of possible urban forms - a genuinely powerful way to handle the staggering complexity of a city, and a genuinely dangerous one if we forget that a city is a living human system, not an optimization problem
A city was always either drawn by one hand or grown by no one's. Computation offers a strange third way - growing a city by rule.
Think about where the shape of a city comes from. For most of history there were two answers. Some cities were drawn - a single authority set down a grand plan, street by street and block by block, from the gridded Roman colonies to Haussmann's Paris to Chandigarh and the planned capitals of the modern age: a city as one designer's deliberate composition, imposed on the ground. Far more cities grew - accreting organically over centuries with no single author, street by street and building by building, as countless individual decisions by countless people slowly produced the intricate, adaptive, humane fabric of a Varanasi lane or a medieval town: a city as an emergent order that no one designed and no one could have drawn. These two - the planned and the organic, the drawn and the grown - are the poles urbanism has always worked between, and each has profound strengths and profound failures (the grand plan can be inhuman and rigid; the organic can be chaotic and unjust).
Computational urbanism offers a strange and powerful third way: growing a city by rule. Instead of drawing every street by hand, you write the *rules* by which streets, blocks, plots and buildings arrange themselves, and let the computer generate the form. This comes in two linked flavours the course will keep distinct. Parametric urbanism builds a model governed by adjustable *parameters* - block size, street width, density, setback, height - so that changing one number re-forms the whole plan instantly, letting you explore a family of designs by turning knobs. Generative urbanism goes further: algorithms (procedural rules, optimization, increasingly AI) *propose* urban forms themselves, generating and exploring thousands of possible city fabrics against goals you set, surfacing options no human would have drawn. Together they promise something genuinely new for a discipline whose subject - the city - is perhaps the most complex artefact humans make: the ability to handle that complexity computationally, to test many futures instead of one, and to ground design in data. It is a genuinely powerful shift - and, this course insists from the first page, one shadowed by a genuine danger: that in learning to grow cities by rule and optimize them by metric, we forget that a city is a living human, social and political system, not an optimization problem, and that the things which make a city worth living in are largely the things a computer cannot measure.
Drawn / grown / GROWN-BY-RULE. Parametric (tune the knobs) + generative (algorithms propose). Powerful for complexity + exploration. But a city != an optimization problem - defend the unmeasurable + ask whose metric.
The two old ways - the drawn city and the grown city
To understand what computation adds, hold the two classic ways a city takes shape. The drawn city is the product of deliberate design by an authority: a plan conceived whole and imposed on the ground, from the Roman grid to the Renaissance ideal city to Baron Haussmann's boulevards cut through Paris to Le Corbusier's and the modernists' planned capitals like Chandigarh and Brasilia. Its strength is coherence, capacity and intent - it can provide infrastructure, order and grandeur at scale, and realise a vision. Its failure, repeatedly, is that a city drawn whole by one mind can be rigid, inhuman and blind to how people actually live: the grand plan that looks magnificent from the air and is desolate at street level, the superblock that killed the street life it replaced. The grown city is the opposite: emergent order with no single author, accreting over centuries through countless small decisions - the organic medieval town, the dense adaptive fabric of an old Indian city, the informal settlement that houses millions. Its genius is fine-grained adaptation, human scale, mixture and resilience - a complexity tuned to real life that no planner could have drawn. Its failures are chaos, inequity, and an inability to deliver large infrastructure or cope with rapid change.
Urbanism has always oscillated between these poles, and the deepest urban thinkers (Jane Jacobs against the grand plan; Christopher Alexander on pattern and organic order) have wrestled with how to get the coherence of the drawn and the humanity of the grown at once. This tension is the essential backdrop for computational urbanism, because its promise is precisely to bridge them: to let a designer set rules and intent (like the drawn city) while generating fine-grained, adaptive, responsive form (like the grown city) - to *grow* a city that is nonetheless *designed*. That is a genuinely exciting proposition. But the same history is a warning: the drawn city's characteristic failure was imposing a designer's abstract order on the messy reality of human life, and computational urbanism, if used naively, is a spectacularly powerful new way to make exactly that mistake - to impose an *algorithm's* abstract order, optimized for whatever happened to be measurable, on a living city. Holding both the promise and the warning is the whole disposition this course tries to build.
Drawn city (one author, coherent but can be inhuman) vs grown city (no author, humane but can be chaotic). Computation = a third way: grow it BY RULE. Promise + the old warning.
Parametric and generative - two ways to grow by rule
Within computational urbanism, keep two ideas distinct, because they are often blurred and they do different things (Module 0.2 goes deeper). Parametric urbanism is design through an explicit model whose behaviour is controlled by *parameters* - adjustable inputs. You build the model once - encoding relationships like 'blocks are this size, streets this wide, buildings set back this far and rise to this height, density is this' - and then you *tune* it: change the block-size parameter, or the density, or the street-grid angle, and the entire plan re-forms instantly and consistently to match. Parametric urbanism does not invent form; it lets you *explore a family* of designs you have defined, rapidly testing 'what if the blocks were bigger?' or 'what if density rose toward the transit stop?' and seeing the whole consequence at once. It is a knob-turning, what-if machine for a design space you have specified.
Generative urbanism goes a decisive step further: instead of you defining the form and tuning it, *algorithms propose the form*. Procedural rules can grow a street network the way an organism grows; optimization algorithms can search for arrangements that best meet goals you set; and increasingly, AI can generate plausible urban fabric. Generative methods *produce and explore* many candidate forms - hundreds or thousands - often surfacing configurations no human would have drawn, which the designer then evaluates and selects among. Where parametric urbanism explores a space you defined, generative urbanism helps *search a space too large to draw*. The two combine: a parametric model defines the moves, generative search explores them, and evaluation (analysis, optimization, human judgement) picks among the results. Both share the core inversion from the drawn city: you no longer place every element by hand; you specify rules, goals and parameters, and the form emerges from computation. That is powerful precisely because a city has far too many interacting parts for a human to optimise by hand - and dangerous for exactly the same reason, because the rules and goals you encode become the city, including everything you left out.
The honest part: a city is not an optimization problem
No field in urbanism is more seductive, or more prone to a specific catastrophic error, than the computational one, and an honest course names the danger on page one. The genuine value is real: cities are staggeringly complex, and computation lets us handle that complexity - modelling how a street network performs, testing thousands of massing options for sunlight and density, grounding decisions in real data, exploring far more of the possible than a hand ever could. For analysis, exploration and handling scale and complexity, generative and parametric methods are genuinely powerful and here to stay. But there is a trap at the heart of the field, and it must be stated plainly: a city is a living human, social and political system, not an optimization problem, and the things that make it worth living in are largely the things a computer cannot measure. Computation optimizes what is *measurable* - density, daylight hours, travel time, cost, a walkability score. But a great city is made of things that resist measurement: community and belonging, memory and meaning, justice and dignity, the unplanned encounter, the corner where life happens, the fine-grained mixture that no metric captures. Optimize hard for the measurable and you will quietly sacrifice the unmeasurable - producing a city that scores beautifully and is dead to live in, exactly the failure of the worst drawn cities, now automated and given a false gloss of objectivity.
Worse, the choice of what to measure and optimize *for whom* is never neutral - it is a question of power and equity. Whose comfort, whose access, whose land value does the model optimize? A computational masterplan can encode and entrench the priorities of whoever commissioned it, erase the informal city that does not fit its categories, and present deeply political choices as objective technical outputs - 'the algorithm says'. And cities are not machines you can fully model: they are complex adaptive systems full of emergence, feedback and human unpredictability that defeat any model's assumptions. So the competent stance is neither the techno-optimist's ('optimize the city') nor the romantic's ('computation has no place in the humane city'), but the disciplined urbanist's: use computation powerfully for what it is genuinely good at - analysis, exploration, handling complexity - while holding fast to the truth that the city's real life is not in the metrics, that the binding choices are human, political and democratic, and that equity and the unmeasurable must be defended precisely because the model cannot see them.
Computation optimizes the MEASURABLE (density, daylight, travel time, score). A great city is the UNMEASURABLE (community, justice, meaning, life). Optimize hard -> sacrifice what matters. And whose metric? = power.
What this course teaches - and what it defers
This course builds computational-urbanism literacy as a practical, honest, and critically self-aware design skill. You will start with designing cities by rule - from drawing to growing, generative vs parametric, the landscape, the hype (Module 0); then why compute urban form - the complexity of cities, data-driven urbanism, exploring the possible, the caveats (Module 1); parametric urbanism - what parametric means, urban parameters and rules, the parametric model, when it helps (Module 2); generative urban design - what generative means, procedural generation, generative design and AI, evaluating options (Module 3); the rules of urban form - street networks, blocks and density, massing and envelope, mixing uses (Module 4); optimizing the city - multi-objective optimization, sunlight/wind/comfort, walkability and access, trade-offs and Pareto (Module 5); data and analysis - urban data, space syntax and networks, simulation, from analysis to form (Module 6); in the real process - masterplanning with computation, stakeholders and participation, from model to plan, the role of the planner (Module 7); making it real - tools and workflow, computational skills, integration and scale, adoption (Module 8); reality, limits and honesty - parametric-washing, the optimization trap, cities are not machines, equity and power (Module 9); and practice and the future - the urbanist's role, getting started, India, becoming computationally literate (Module 10).
One firm boundary runs through all of it. Generative and parametric urbanism is a set of tools to explore, analyse and test urban form - it supports human and democratic decisions, it does not make them. This course teaches the principles and design judgement, and defers every binding result - actual planning and land-use decisions, statutory approvals, and the social, equity and political judgements about a city's future - to the planning authority, the democratic and participatory process, the affected communities, and the governing planning law and development-control regulations (in India, the master-plan and development-plan process, the applicable development-control regulations and the National Building Code of India). Any tool or generated form named here is illustrative and fast-moving. Studio Matrx is free and not-for-profit, and this course is written to be rigorous and honest - not a computational-design sales pitch but a clear, critical grounding in growing cities by rule, mindful of the Indian context where cities are urbanising at extraordinary speed and scale, where the informal and organic city houses hundreds of millions and rarely fits a computational model's categories, and where top-down, technocratic masterplanning has a long and cautionary history. Understand the drawn-versus-grown inheritance, the parametric-versus-generative distinction, the genuine power for analysis and exploration, and above all the optimization trap and the questions of equity and power - and you will be able to use computation to serve a humane, just city rather than to automate its erasure.
Parametric vs generative
Two ways to grow by rule
Parametric = tune a model you defined (explore a specified family); generative = algorithms propose and search forms (explore a space too large to draw). Keep them distinct. Modules 0.2, 2, 3.
The optimization trap
What computation cannot see
Computation optimizes the measurable (density, daylight, score); a great city is made of the unmeasurable (community, justice, meaning). Optimizing hard can erase what matters most. Modules 5, 9.2, 9.3.
Equity and power
For whom is it optimized
What you measure and optimize for is a political choice, never neutral; a model can entrench interests and hide choices as 'objective'. Defend equity and the informal city the model cannot see. Modules 9.4, 7.2.
The binding choice is democratic
Who decides the city's future
Planning, land-use and equity decisions belong to the planning authority, the participatory/democratic process, the communities and the law - never to the model or 'the algorithm'. Modules 7.3, 7.4.
Workshop — find the measurable and the unmeasurable in a place you love
Computational-urbanism thinking starts with feeling the gap between what a model can measure and what actually makes a place live. In this first workshop you will take an urban place you love and sort what makes it good into what a computer could optimize for and what it could never see - the central discipline of the whole field.
Just a place you love and a notebook. No software - this first workshop is about feeling the optimization trap by hand; the parametric models, generative algorithms and analysis tools come later, and the binding urban decisions always stay with the planning authority, the community and the democratic process.
Goal: a first, felt grasp of the optimization trap Inputs: an urban place you know and love (a street, a neighbourhood, a bazaar) + a notebook Time: ~40 minutes
- 1Name what makes it good: list 8-10 things that make this place genuinely good to be in - be specific and honest, from the width of the pavement to the feeling of the evening crowd.
- 2Sort each one: mark it MEASURABLE (a computer could quantify and optimize it - width, density, sunlight, distance, mix) or UNMEASURABLE (it resists a metric - the feeling, the memory, the community, the life).
- 3Notice the balance: which column holds the things you'd fight hardest to keep? Usually the unmeasurable - which is exactly what an optimization would sacrifice first.
- 4Try to break it: imagine an algorithm optimizing this place hard for one measurable goal (say, density or traffic flow). What unmeasurable quality would it quietly destroy, and why would the metrics still look good?
- 5Write a one-paragraph reflection: what computation could genuinely help you understand about this place, what it could never capture, and why the binding decisions about its future must stay human and democratic - flagged as reasoning.
You’ll walk away with
A one-page sort: what makes a loved place good, split into measurable and unmeasurable, one honest scenario of optimization destroying an unmeasurable quality, and a reflection on computation's real role - framed as reasoning. Keep it; you will put real method behind it across the course.
Three altitudes on the same idea
Read the band that fits you — or all three.
For the architect or urban designer, generative and parametric methods are a genuinely powerful way to handle the complexity of urban form and explore far more options than you could draw - and a genuinely dangerous one if you let the model's measurable goals stand in for the city's real life. Parametric models let you tune urban parameters (density, block size, street width, height) and see the whole plan re-form; generative methods propose and search across many forms; analysis grounds design in data. Use these for what they are strong at - exploration, testing, handling scale and complexity - and keep asking what the model leaves out: community, meaning, justice, the unmeasurable fine grain that makes a place live. Learn the methods and their trap in equal measure. Defer the binding planning, land-use and equity decisions to the planning authority, the democratic and participatory process and the governing law; your job is to wield computation in service of a humane, just city, never to let 'the algorithm says' replace design judgement and public choice.
For the planner or urbanist, computational methods can strengthen your evidence base and let you test scenarios rigorously - but they are most dangerous exactly where planning matters most, because they can dress political choices as technical outputs and erase what does not fit the model. Data-driven analysis, network and space-syntax measures, and scenario testing genuinely help you understand a place and argue from evidence. But planning is fundamentally about people, power, competing interests and public legitimacy, and a computational masterplan can encode whose interests it serves, present contestable choices as objective, and render the informal or organic city invisible. Learn to use these tools to inform and to open up options for public debate - not to close debate down. Keep the binding decisions where they belong: with the statutory process, the affected communities and the law. Your domain is using computation to serve a more transparent, evidence-based and equitable planning process, while defending everything the model cannot see.
Generative and parametric urbanism is one of the most intellectually rich frontiers in the built environment - it sits where computation, design, data and deep questions of justice meet - and understanding it clearly, its power balanced by a sharp critique, sets you apart. Start with this lesson's framing: cities were drawn (one author, coherent but sometimes inhuman) or grew (no author, humane but sometimes chaotic), and computation offers a third way - growing them by rule, through parametric models you tune and generative algorithms that explore thousands of forms. Learn the parametric/generative distinction, what the methods are genuinely good at (analysis, exploration, complexity), and above all the optimization trap: a city is a living human and political system, not an optimization problem, and optimizing the measurable can erase the unmeasurable things that make a city worth living in - while the choice of what to optimize, and for whom, is a question of power. You are not expected to build a masterplanning engine; you are expected to be computationally literate and critically aware. It is a rigorous, values-laden field and a standout portfolio thread.
“Generative and parametric urbanism means we can finally design optimal cities - feed in the goals and data, let the algorithms optimize, and get a scientifically best city plan, free of the biases and guesswork of traditional planning. Computation makes urban design objective and lets us solve cities like engineering problems.”
Do it yourself
No software needed — reason it through.
- 1Contrast the drawn city and the grown city: the strengths and characteristic failures of each.
- 2How is 'growing a city by rule' a third way, and how does it try to bridge the drawn and the grown?
- 3Distinguish parametric from generative urbanism: what does each do, and how do they combine?
- 4Explain the optimization trap: why can optimizing the measurable erase what makes a city worth living in?
- 5Why is the choice of what to optimize, and for whom, a question of power rather than a neutral technical decision?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Urban planning — Wikipedia — Urban planning, 2026.
- 02Parametric design — Wikipedia — Parametric design, 2026.
- 03Generative design — Wikipedia — Generative design, 2026.
To use computation in urbanism well we first need the case made properly - just how complex a city really is, what data-driven urbanism can and cannot see, the value of exploring the space of the possible, and the honest caveats. Next we build that case.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →