BookenDeX — Better Discovery eXperience
Cover of How Architecture Got Its Hump
Book details

How Architecture Got Its Hump

by Roger Connah

Published 2001184 pagesISBN 978-0-2625-3188-7

"In How Architecture Got Its Hump, Roger Connah explores the "interference" of other disciplines with and within contemporary architecture. He asks whether photography, film, drawing, philosophy, and language are merely fashionable props for architectural hallucinations or alibis for revisions of history. Or are they a means for widening the site of architecture? Connah shows how these disciplines have not only contributed to new developments in architectural theory and practice, but also have begun to insinuate new possibilities of space. Sometimes seamless, sometimes awkward like the hump acquired by the camel in one of Rudyard Kipling's Just So Stories, these disciplines have had their own responsibilities and excesses grafted onto architecture, just as architecture has tried to shake off their limitations.". "Taking interference a step further, Connah also considers the implications of philosophical incongruity and architectural nest. He asks how architecture loses its head, transcends the dead language it now entraps, and houses meanings it wants to contest. Hardly bleak questions, suggests Connah, for they point to ways for architecture to rescue itself."--BOOK JACKET.

Beyond its central premise, the book can be read through the connected lenses of Philosophy. Those themes offer useful points of attention as the characters, ideas, or world develop, especially where the book complicates the expectations of its primary category.

As an Amazon Associate I earn from qualifying purchases.

Full BookenDeX details

What the reading experience may hold

A fuller profile for choosing with more confidence—not just another copy of the preview.

Themes to notice

Philosophy

Use these as starting points rather than limits; the most memorable books often stretch beyond their catalog labels.

Content notes

Catalog signals suggest warfare and conflict. These notes may not be complete; consult a publisher or reader-supplied guide when detailed warnings matter.

These notes are inferred from available catalog information and may not be complete. Check a publisher or reader-supplied guide if you need comprehensive warnings.

Reading experience

Dark tone · Measured pace

Works well for a focused weekend or a few concentrated sittings.

Who it may suit

A good fit if…

Readers who want a thoughtful experience and enjoy noticing the connections beneath a book’s surface story.

At a glance

This book's DNA

A visual estimate based on this edition's categories, description, and length. Select a star to explore the signals.

ToneDark
LuminousDark

This signal is descriptive, not a rating. It helps compare the kind of reading experience this edition may offer.

No plot details

Spoiler-Free Emotional Arc

A broad estimate of the book’s emotional rhythm, shown without story events or outcomes.

Spoiler-free
12345
PeakRelative emotional intensity
How Architecture Got Its HumpRoger Connah
Powerful5/5

This visualization is an interpretive estimate based on catalog description, categories, tone, pace, and content signals. It does not describe specific scenes.

Before you choose

A quick reading snapshot

Edition facts and catalog signals to help you decide whether this book fits what you want to read next.

Reading lengthA shorter read184 pages in this edition
Publication eraModernFirst published or edition dated 2001
Primary categoryPhilosophyExplore similar books below
ISBN-13
978-0-2625-3188-7
Language
English
Edition record
OL10237995M
BookenDeX editorial lens

A more thoughtful way into this book

This guide uses the edition details and category signals above to help you choose deliberately. It does not replace the author's work or a full review.

Good to know

Works well for a focused weekend or a few concentrated sittings.

Begin with its place in Philosophy, then notice where the book resists that label.

Try this reading approach

Read for connection, not completion.

Mark one passage that sharpens the book's central concern and one that complicates it. That tension often reveals more than a quick summary.

Three questions to carry with you

  1. What question is the author really asking beneath the book’s main argument?
  2. Which claim challenges one of your familiar assumptions?
  3. What remains unresolved—and is that uncertainty useful?

Editorial framework by Wesley Bryan, BookenDeX Founder and Editor.