Live data from Hacker News

Things an architect should know

readingdesign.org

21–30 of 74 posts

Re: Things an architect should know

#21
post #13

I'm not an architect (well, technically my job title is "Architect", but I'm not that kind of architect). But I'd be curious to see a list like this for some other professions, just because it tickles my curiosity.

I'm tempted to create one for anesthesiologists (I'm a retired [38 years of practice] neurosurgical anesthesiologist — I certainly have the time! But I'm too lazy.

do it! i'd love to see one for other fields. maybe just a list of 25 to start ;-)

Re: Things an architect should know

#22
post #5

I feel like this would be improved with hyperlinks for context. Many of the points seem to cryptically refer to dangers like "the energy embodied in aluminum" presumably referring to how dangerous aluminium cladding is when on fire. I'd like to know, for instance, what the context is for "the rate at which that carpet you specified off-gasses"

"embodied energy" means the energy needed to create the material. So that involved in mining aluminium, refining ore etc, moving it around the world until it's built into a building. Carelessly specified new carpets will off-gas VOCs to the detriment of the local air quality (until there's none left in thecarpet material). In both cases he's saying that an architect should be aware of the wider context of their mater…

Refining aluminum is a particularly energy intense activity - much more so than iron.

Re: Things an architect should know

#23
Most here are not trained architects. Well, I am a trained architect and also worked as architect for over a decade. That's what we learned at school. That what was considered important. And much more BTW. Architects are generalists. Many architects went on to work in engineering, civil engineering, social studies, informatics/computer science, physics, politics, literature, stage design, city planning, movies, ... You name it, we did it.

Re: Things an architect should know

#24
post #20
post #16

Earlier quoted context omitted.

The placement of keys in such s way that they had a low probability of jamming (whether effective or not) has heavy parallels in designing building entries and exits, planning emergency exit capacity etc. Basically if you’re planning an exit also consider human usage statistics of the connected rooms.

> The placement of keys in such s way that they had a low probability of jammin It's highly debatable, and arguably a myth. The QWERTY design predated any potential jamming problems. Perhaps it was so foreseeing? It's really hard to believe general ergonomy was the top priority, as all the characters of the word TYPEWRITER are placed in the top row, which could have hardly happened by sheer coincidence, but was very…

>The QWERTY design predated any potential jamming problems. Perhaps it was so foreseeing?

https://www.smithsonianmag.com/arts-culture/fact-of-fiction-...

Apparently it was partly publicity stunt, partly defined through feedback received from actual users.

Re: Things an architect should know

#25
What I really want to know is why I can't have a Soviet concrete-block box-house built in the US for $20,000 yet.

Is it because you are really mostly paying for the land?

But still, building a house still runs at $100,000+. Why though.

Are any of the pre-fab companies taking off?

I want to buy a run-down house, tear it down, and build pre-fab on it for $20,000, damn it.

Sorry, off-topic, but it seems like such an opportunity area for someone with some capital.

Re: Things an architect should know

#26
post #23

Most here are not trained architects. Well, I am a trained architect and also worked as architect for over a decade. That's what we learned at school. That what was considered important. And much more BTW. Architects are generalists. Many architects went on to work in engineering, civil engineering, social studies, informatics/computer science, physics, politics, literature, stage design, city planning, movies, ... Y…

Architect here. I also have a background in computer science.

What made you switch from architecture to software development?

Re: Things an architect should know

#27
post #13

I'm not an architect (well, technically my job title is "Architect", but I'm not that kind of architect). But I'd be curious to see a list like this for some other professions, just because it tickles my curiosity.

Are you aware of one for the kind of "Architect" you are? I'd definitely like to read that.

Re: Things an architect should know

#28

What I really want to know is why I can't have a Soviet concrete-block box-house built in the US for $20,000 yet. Is it because you are really mostly paying for the land? But still, building a house still runs at $100,000+. Why though. Are any of the pre-fab companies taking off? I want to buy a run-down house, tear it down, and build pre-fab on it for $20,000, damn it. Sorry, off-topic, but it seems like such an opp…

We spent 7K to tear down a house in probably the lowest cost area of the USA

Re: Things an architect should know

#29
post #23

Most here are not trained architects. Well, I am a trained architect and also worked as architect for over a decade. That's what we learned at school. That what was considered important. And much more BTW. Architects are generalists. Many architects went on to work in engineering, civil engineering, social studies, informatics/computer science, physics, politics, literature, stage design, city planning, movies, ... Y…

Architect here. I also have a background in computer science. What made you switch from architecture to software development?

Another architect here. I didn't do it yet but I'm really considering a career change. Why? Less exposition to market cycles. Architecture is a _terrible_ field to be during downturns. I passed through one, I won't repeat the experience.

Re: Things an architect should know

#30

What I really want to know is why I can't have a Soviet concrete-block box-house built in the US for $20,000 yet. Is it because you are really mostly paying for the land? But still, building a house still runs at $100,000+. Why though. Are any of the pre-fab companies taking off? I want to buy a run-down house, tear it down, and build pre-fab on it for $20,000, damn it. Sorry, off-topic, but it seems like such an opp…

But, how much will the run-down house cost you? In my area there are so many more buyers than houses available that people are buying shacks for many hundreds of thousands of dollars.
Post reply on HN