The detailing of many important and essential aspects of a building are initially neglected and thought of as a last step before the completion of a project, starting with the large scale working down to the small scale. They’re usually treated secondary and the general scheme is prioritized. Superficial and assembled rather than detailed and how it’s assembled. This creates a dilemma when necessary elements of a building begin to be considered how to be built and are treated as a problem, when it should be considered as an opportunity. More often than not, the product of a detail is a solution to a problem that was created. Not meaning the problem could’ve been avoided, the problem still needed to be solved regardless, but it was solved out of necessity and not as an asset to the project. This project was not about working backward, starting with a detail and working outwards to create a whole, to assemble fragments without any real sense of bearing. I didn’t use the detailing of the project just for the sake if it, to solve a problem that perhaps didn’t need to be solved. Instead embrace the challenge of a given situation as a seed from which a design process can grow. By briefly zoom in on a specific situation I hoped to develop a common language of the building as a whole. To create something that belongs to the building and not considered as an addition.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:kth-261647 |
| Date | January 2019 |
| Creators | Carlsen, Alexander |
| Publisher | KTH, Arkitektur |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
| Relation | TRITA-ABE-MBT-1947 |
Page generated in 0.002 seconds