News for hackers. Stuff that matters.
Re:Top Ten Reasons You Are Not an Architect by hobb0001 on Friday March 27, 2009 @10:28AM (#535098)
Not that I've worked with building architects, but I have worked in an HVAC engineering firm that does work with architects. My sense is that the original author's view of a real architect's life is shaped by whatever is shown on TV. In contrast to fictional architects, a real building architect owns her own hard-hat for the almost daily visits to the job site. When something goes wrong with the build, she's involved with coming up with a solution, whether it's really an architectual problem or not. (Example, the cement contractor got a bad batch of cement that isn't curing right. It would take a month for him to get the right aggregate to fix it. Instead of delaying the build, could we make the walls less thick and add in supports elsewhere?)

Also, most real-world architects rarely get to build from scratch. Those types of jobs are the dream jobs and tend to be taken by the owners of the architectual firm.

Re:Top Ten Reasons You Are Not an Architect by mixmax on Friday March 27, 2009 @10:42AM (#535116)
I have a close friend that is an architect, and what you're describing is pretty accurate.

Also I can attest that this is wrong - "An architect can reasonably expect to sleep through every night of the year without a call from work" Architects get just as many ood-hour calls as sys-adms.

Re:Top Ten Reasons You Are Not an Architect by timcederman on Friday March 27, 2009 @04:52PM (#535706)
About what? I come from a family of architects, and while they work long hours, they certainly don't get odd-hour calls. What type of building architect are you referring to?
Re:Top Ten Reasons You Are Not an Architect by mixmax on Friday March 27, 2009 @06:04PM (#535784)
His customers are often private, and they tend to call him in their freetime - evening and weekends. He also has to do a lot of planning meetings off-hours for the same reason.

Maybe we have a difference definition of odd-hours? He never gets calls in the middel of the night though.

Re:Top Ten Reasons You Are Not an Architect by catone on Friday March 27, 2009 @10:09AM (#535075)
Er, architect does have more than one definition...

I.e., "the deviser, maker, or creator of anything: the architects of the Constitution of the United States" (definition #3 on dictionary.com)

My guess is that the word architect in the author's job title refers to something closer to that defintion than to the literal "designer of buildings" definition.

Re:Top Ten Reasons You Are Not an Architect by swombat on Friday March 27, 2009 @10:14AM (#535080)
Top 1 reason this article is mis-titled:

* 1. The title should be "Top ten unimportant and uninteresting reasons you are not a building architect"

Re:Top Ten Reasons You Are Not an Architect by ams6110 on Friday March 27, 2009 @10:21AM (#535089)
Also, you're probably not an Engineer. A real engineer is someone who is trained and certified to sign or "stamp" engineering documents and takes legal responsibility for their correctness.
Re:Top Ten Reasons You Are Not an Architect by tom_rath on Friday March 27, 2009 @10:28AM (#535096)
I think the author is attempting to take the analogy a bit too far.

If "computer wizards" and "programming rock stars" faced the same measure, I would expect them to teleport to their groupie-filled release-parties.

Re:Top Ten Reasons You Are Not an Architect by hairsupply on Friday March 27, 2009 @10:58AM (#535145)
Main reason I am not an architect: I favor Judging to Perceiving.