Things an architect should know • Hacker News Board

Re: Things an architect should know

#61

Post by galfarragem » Tue, Oct 23, 2018, 4:46 PM UTC

ry_ry wrote: post #15

monadgonad wrote: post #11

Earlier quoted context omitted.

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…

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

Re: Things an architect should know

#62

Post by s3nnyy » Tue, Oct 23, 2018, 5:33 PM UTC

hikari-boulders wrote: post #59

twic wrote: post #50

Earlier quoted context omitted.

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?

Re: Things an architect should know

#63

Post by twic » Tue, Oct 23, 2018, 5:37 PM UTC

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

Re: Things an architect should know

#64

Post by ry_ry » Tue, Oct 23, 2018, 7:12 PM UTC

galfarragem wrote: post #61

ry_ry wrote: post #15

Earlier quoted context omitted.

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…

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

Outside of my area of expertise, so honestly I've got very little to contribute beyond a glib shitpost and some elaboration.

I'm fully prepared to admit my ignorance here, but in the case of a masters surely the value comes from demonstrating your thought process is sound through review? Without those checks and measures is it not just mental masturbation?

Re: Things an architect should know

#65

Post by amanaplanacanal » Tue, Oct 23, 2018, 8:22 PM UTC

mcherm wrote: 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.

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.

Re: Things an architect should know

#66

Post by evasote » Tue, Oct 23, 2018, 10:12 PM UTC

gnode wrote: 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"

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

Re: Things an architect should know

#67

Post by rurban » Tue, Oct 23, 2018, 10:23 PM UTC

brenschluss wrote: post #26

rurban wrote: 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?

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

Re: Things an architect should know

#68

Post by lalala1995 » Wed, Oct 24, 2018, 3:26 AM UTC

gnode wrote: 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"

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.

Re: Things an architect should know

#69

Post by veli_joza » Wed, Oct 24, 2018, 11:03 AM UTC

lalala1995 wrote: post #68

gnode wrote: 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"

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.

Re: Things an architect should know

#70

Post by hikari-boulders » Wed, Oct 24, 2018, 7:49 PM UTC

s3nnyy wrote: post #62

hikari-boulders wrote: post #59

Earlier quoted context omitted.

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