4 ms·
I find unconstrained designs a bit pointless. Competition's problem statement is at https://www.e-architect.co.uk/competitions/evolo-2020-skyscraper-competitio
by contingencies 6y ago
I find unconstrained designs a bit pointless.
Competition's problem statement is at https://www.e-architect.co.uk/competitions/evolo-2020-skyscraper-competition https://www.e-architect.co.uk/competitions/evolo-2020-skyscr... ... remember architects are not engineers. It's much easier to break than to build. What would you have proposed?
- nickff 6y agoI probably wouldn't bother to enter these sorts of competitions, even if I were an architect, as anything realistic would lose. I mostly design plastic enclosures, and assemblies for electronic products, and have to keep manufacturability top-of-mind.
- lmm 6y agoThe problem statement is the problem - it's way too broad and vague to yield useful results. If the aim is to find a solution to a specific problem (e.g. using less water), that should be the problem statement. If the aim is to find a novel improvement over the "standard" skyscraper, it should start with a reference design and then ask for an improvement subject to some reasonable constraints (e.g. improve one of the listed areas for at most a 10% cost increase).