Hacker Newsnew | past | comments | ask | show | jobs | submitlogin
Things an architect should know (readingdesign.org)
81 points by bookofjoe on Oct 23, 2018 | hide | past | favorite | 71 comments


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 material choices and consequential effect on both the planet and the building's inhabitants.


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


>the energy embodied in aluminum

See here: https://en.wikipedia.org/wiki/Embodied_energy

>the rate at which that carpet you specified off-gasses

I think the general idea behind this one is know that the materials you select can have an adverse effect on those who have to live with them. Carpet is one example to illustrate the point


I every much think it's the point of this, if you haven't understand the meaning behind the texts then you didn't know those concepts.


IMO the point _should be_ to educate, and not to belittle readers. The list looks very interesting, but it's too terse to take away anything from it.


It's how much the carpet will smell after you install it.


While this is a little... excessive and dare I say a slightly indulgent list, I think it communicates a concept with merit.

Architecture is creating form which exists in a very complex system. Thats a concept that we could at least extrapolate and apply to other industries.


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.


My wife is an architect and the one that resonated most with me -- both on behalf of her (especially given architects' pay), and for me as a founding engineer of a software startup 7 years in:

80. The reasons for their tenacity.

Reflecting on this can be enlightening, and like many enlightening things, uncomfortable


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.


I thought it was basically impossible to get a decent architecture job without being exceptional/connected. That's what turned me off from the field.


It's not far from reality and it only applies during bull markets. During bear markets being exceptional/connected might not be enough.

As an anecdote, in 2009 when construction plummeted - downturn is a bit delayed, investors finish ongoing buildings but don't start new ones - the company where I was working downsized from 75 to 10 employees in a few months. In small offices (with smallish projects) was even worse.


I've tried a lot. I've also done movies, internet ISP, race car engineering, ... but SW engineering is the most interesting by far.


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.


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.


I am in a fly-over and there are "upcoming" areas - pockets between the city and the suburbs, within 10 mins of downtown and other "prestigious office areas" that are almost sure to take off, but total ghetto now. It's not worth risking $200,000 to build a fancy house there, but it's worth $15,000 land, $15,000 tear down, and $20,000 pre-fab.

At least, that's my very-limited POV.


>I can't have a Soviet concrete-block box-house built [...] //

They're competing with you buying a pre-built house. There's no need to charge that little, in addition people will often pay more to have their own house built, and new carries a premium. So there's no pressure pushing them to make houses low cost. Buy the land, hire a builder .. they'll still charge you too much because your alternative is still to have a pre-built house.

Rent-seeking ftw.


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


Yea, it's expensive to tear down, usually almost double that even in cheap areas. It's part of the problem to the point where some of my friends discussed setting up a tear-down company rather than trying to mess with conventional real estate.

Edit: Also totally unrelated, but I have always wanted to know what the raw cost for a basement/foundation usually is.


Regulation is certainly part of the cost.


How much?


Don't know, depends on the country. I can give you an example from Europe. Switzerland is one of the highest income highest cost countries in Europe. If it weren't for different regulations mandating Swiss level salaries for foreign workers, import tariffs, taxes (and probably a bunch of other stuff I don't even know about), it would easily be possible to pay only 10-20% for a prefab compared to a non-prefab.


Which "regulations mandating Swiss level salaries for foreign workers" are you talking about?


They are called (in German) "flankierende Massnahmen".


link?


Well, I cant find one in English. [Here](https://www.personenfreizuegigkeit.admin.ch/fza/de/home/aufe...) is one in German, if that's all right with you.

Basically the first sentence of the first section defines it:

"Das Entsendegesetz verpflichtet ausländische Arbeitgeber zur Einhaltung von minimalen Lohn- und Arbeitsbedingungen gemäss den anwendbaren schweizerischen Vorschriften."

Google translate gives this:

"The Posting Act requires foreign employers to comply with minimum wage and working conditions in accordance with the applicable Swiss regulations."


In reality this law is not needed or applied, if it wouldn't be there, nothing would change. The minimum wage is not enforced but is in place implicitly, at least this is what I observe.


Are you saying that i can employ bosnians for 20% of minimum wage to build me a 100k home in switzerland and no one would complain?


> The relevant sections of the Code of Hammurabi.

Nice. Like: If a architect (builder) build a house for some one, and does not construct it properly, and the house which he built fall in and kill its owner, then that architect shall be put to death.


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.


Please do one. Even if short. I'd love to read it. I'm a industrial engineer researching healthcare systems. I'm firmly of the opinion that people with decades of experience have truly valuable knowledge locked within. Even a small list would probably delight many here, me for certain at least.


1. Which end the skull is

2. Where the bricks are kept


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


I thought the hack went "make us a list of one" with the hope that once they're over the hump of making a list that inertia will push them to do more.


OK, OK... how about 10? Can you live with 10? 'Cause I just made this for you: https://www.bookofjoe.com/2018/09/10-things-an-anesthesiolog...


Note: I published it to my blog using a date in the past because it was the fastest, easiest way to create a permalink to use here. I did indeed just create the list (and subsequent post) in response to the comments preceding it. In case you were wondering...


>>The first thing to do upon arriving at a Code Blue is to take your own pulse.

Can you expand on this item, please? I interpret it as "don't just arrive and immediately begin taking action, but take a moment to fully assess the situation because an extra 15 seconds is a worthwhile cost to avoid a mistake". Curious to know if I'm on track.


Exactly.


#7 will make you laugh!

Why in the hand?

Also, when I was in hospital (diverticular disease) they put the first IV in my non-dominant arm (at elbow), then the second in my dominant arm .. the second one ended up staying in much longer. I wonder how often that happens; whether in some areas [ER?] it might be sufficiently often to warrant reversing the rule-of-thumb?


Re: #7: it's true! Why in the hand? Because if you put it in the antecubital fossa, you force the patient to keep their arm straight so as not to cause the IV to infiltrate by bending the elbow — this effectively makes the arm unusable. By putting the IV in the back of the hand, you enable full use of that arm. In regards to your hospital experience with the two IVs you had: it's impossible to predict how long an IV will remain functional. In regards to which side to place the IV, in the ER you can omit this nicety: as we/they say, "any port in a storm."


It was always a hit and miss with IVs for me. Sometimes they installed it perfectly, other times it started hurting within an hour. I guess it also highly depended on the nurse - some also had a lot of trouble taking my blood, others consistently got it done within 15 seconds.

I was never asked about hand dominance so during surgery they actually put the IV in my dominant hand and hit a nerve. I couldn't use my dominant hand for a month.


In my state you can't call yourself and Architect or Engineer unless you are actually registered as such. I keep meaning to ask what they call someone who drives a train.


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


Is this meant to be art? Why should an architect know Shakespeare and QWERTY?

Should a welder know about quarks and neutrinos?


There's a lot of architecture in Shakespeare. The non-Aristotelian structure of his plays, the highly stylized language, the iambic pentameter, the stage directions. You could endlessly examine the structural characteristics of his works.

The list obviously plays with leaving things vague, ambiguous, uncertain. It's funny how this seems to enrage certain people.


I was wondering the same thing. Many of these don't have any context. Found a blog which expands informationally on some, but still no whys: https://adamachrati.wordpress.com/category/sorkin-250/


There are a few themes in the list, one is sound. That is why I think Shakespeare is recommended. Even native english speakers have trouble with the old language, but the sound of the words conveys even when the diction fails.

An architect should know QWERTY because it is a form and pattern that people are familiar with. One part of architecture is informing people how to use spaces without instructions and to do so, an architect must understand the patterns they are already familiar with


> Why should an architect know Shakespeare and QWERTY?

Well why not? QWERTY could refer to just being able to type. An artist could possibly do well to be able to use a computer? It could also refer to the placement on old style typewriters where the type bars could get jammed if letters used often in the English language were typed in quick succession. (Myth maybe? But interesting to think about anyway for someone that is going to design things for other people to use.)

As to Shakespeare, it has been suggested that people that read fiction/literature of this sort develop empathy and makes you a "better" person.


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 convenient for the sake of sale presentations in the early years...


>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.


> This theory [jam avoidance] could be easily debunked for the simple reason that “er” is the fourth most common letter pairing in the English language

Argh, no. E and R are separated by D, 4, and C. It would be nice if someone writing about typewriters actually looked at one.

The bar-adjacent letter pairs, from most to least frequent¹, are MI BY CR NU HN XE HM AZ DC GB ZW VT FV SX.

¹ https://gist.github.com/lydell/c439049abac2c9226e53


But if you're an architect skilled in designing vomitoriums, or whatever, then how does adding the mythological QWERTY design add to that.


I take it as a bit of a meta piece about how the knowledge of an individual in an industry should never be limited to only that industry.

As computer programmers, this is perhaps even more important (since we're rarely writing programs for the sake of writing programs), but it's valuable to every industry to have a well rounded and well educated individual.

More specifically, a welder who learns about quarks and neutrinos shows curiosity beyond "an electrical arc creates heat and melts metal", a trait present in individuals who strive to better themselves and their craft.


I think that one should know deeply about its craft.

Architecture is about design so it's fair to think that an architect should know about art and (some kind of) product design.

The analogy that I can think would be something like - A developer should know about network and how the user will use software, this concepts are important even if the programmer do not work directly with this things.


Architecture is the vessel for all of life and work and has a direct affect on the way we live, move, and think. . Architecture is about all of life and this is why architects need to be more than engineers. They must be poets, philosophers, and lovers.


Its clearly not a practical guide.

It was also posted 16 hours ago and sunk without trace, presumably because nobody wanted to say 'this is stupid' incase it was genius and they appeared thick.

It is pretty stupid.


I'm glad it was reposted, because I found it intriguing and inspiring for the reasons mentioned in the current top comment: https://news.ycombinator.com/item?id=18282678

It may not be _genius_, but I don't think it's stupid, and especially not because it's an artistic rather than practical guide.


I dunno, if feels like an invitation to attach contextual meaning to a selection of random phrases.

You could present this as a list of things ${profession} should know, and somebody somewhere would find it a refreshing thought experiment.

I would question if those mental gymnastics reflect on the source, or on the individual who created the meaning?

Without context its just a list of stuff with indeterminate intent - any artistry is the result of the reader willing it into existence.


Believe or not, this fits very well as the informal curriculum of my Masters degree in Architecture and is not random at all.


>It was also posted 16 hours ago and sunk without trace OT you touch on something that's always puzzled me about HN, namely often something I posted days ago — that quickly disappeared into the ether — suddenly appears on the leaderboard posted by someone else with hundreds of points and comments. I just chalk it up to my bad karma.


> How to unclog a Rapidograph

My fingers just started spontaneously doing the unclogging motion when I read that, and I haven't touched a Rapidograph in 30 years.


Is there something in there about knowing optimal working conditions for knowledge workers?

Because the modern office building as designed by current architects isn't it.


The architects would likely chafe at this complaint and grumble something about interior designers, client budgets, and clients' mistaking a trend for good design


1. How to arrange for air flow through office bathrooms

2. That interior light reflected on the inside of a window ruins the view of the sunset


"How the pyramids were built"? Don't we get a monthly article on Yahoo about the latest guy who claims to have cracked the mystery? :)


So how do you unclog a rapidograph? I've been wondering my whole life! -- No sarcascm, real question!


What I do is to submerge the tip assembly in alcohol overnight / for a couple of days.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: