Live data from Hacker News

Things an architect should know

readingdesign.org

51–60 of 74 posts

Re: Things an architect should know

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

1. Which end the skull is

2. Where the bricks are kept

Re: Things an architect should know

#52
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…

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

Re: Things an architect should know

#53

Earlier quoted context omitted.

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.

Re: Things an architect should know

#54

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

Re: Things an architect should know

#55

Earlier quoted context omitted.

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.

Re: Things an architect should know

#56
post #20

Earlier quoted context omitted.

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

> 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

Re: Things an architect should know

#57

Earlier quoted context omitted.

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

#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?

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.

Re: Things an architect should know

#58

Earlier quoted context omitted.

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

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

Re: Things an architect should know

#59
post #50

Earlier quoted context omitted.

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.

Re: Things an architect should know

#60

Is this meant to be art? Why should an architect know Shakespeare and QWERTY? Should a welder know about quarks and neutrinos?

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.
Post reply on HN