Highs and Lows
Sorry to the lack of posts...as the ride from inspiration high has been stuck in a low for a bit, I find myself confounded by my project - or, rather, the lack of any ideas about how to push my project forward.
This is, inevitable. On the roller coaster ride of creativity, you are bound to find a lull, where, no matter what, you produce crap. And it's not even interesting crap - crap that inspires you to reimagine your work, rethink your ideas, opens the flood gates to greatness, or at least better crap.
It's come down to deadlines, and sometimes you just have to take motivation from any source. So now, as I push toward making a critical leap, I do so without a good sense of how far the fall might be.
Inspiration is coming. I think. Or I might just have to get my ass out of the rollercoaster car, push it up the next big hill before I can enjoy the ride again. Which, gasp, means I might be spending some quality time with my computer, making sweet, sweet love to the tutorial sessions included in various software programs. Ahh...this...this is architecture.
This is, inevitable. On the roller coaster ride of creativity, you are bound to find a lull, where, no matter what, you produce crap. And it's not even interesting crap - crap that inspires you to reimagine your work, rethink your ideas, opens the flood gates to greatness, or at least better crap.
It's come down to deadlines, and sometimes you just have to take motivation from any source. So now, as I push toward making a critical leap, I do so without a good sense of how far the fall might be.
Inspiration is coming. I think. Or I might just have to get my ass out of the rollercoaster car, push it up the next big hill before I can enjoy the ride again. Which, gasp, means I might be spending some quality time with my computer, making sweet, sweet love to the tutorial sessions included in various software programs. Ahh...this...this is architecture.
posted by the silent observer at
6:58 AM
8 Comments:
I'm sorry, but that is not architecture. Architecture should be a process that you develop yourself in order to come up with the best solution for a problem. This is why each architect is different and why a client would choose one over another.
And, I take, that you have never been in a situation where you've had to make a deadline the motivation for moving forward? Then, sir or madam, I commend you. As for me, this is, for now, part of my process...and as my project has self-defined parameters, it is up to me to decide what the problem is before I can find a solution. Oh, and the last sentence was a bit facetious...but, true enough for my situation.
Architecture is deadlines - I've been in practice for years now and as a licensed professional I just want to say cut the crap
I'd love to cut the crap. Suggestions? As I see it, right now, as I explore some different ideas, I produce stuff that I don't necessarily feel has potential or merit once it's actually sitting in front of me. It's a dead end. But I had to at least try. And so the crap is part of my process. If you have another way, I am all ears...
silent observer, being a student in thick of academia, i think is allowed some dead ends, rumination of crap before him/her, etc. as a means to develop him/herself.
besides, i doubt that these thoughts that silent observer shares with us on this very personal blog comprise the bulk of his/her everyday conversation. in studio or on the street. it is an archi-hell blog. he/she would not have come this far as a complainer. as a blog, i'd imagine thoughts here are honest and uncensored. and to me silent observer sounds like a lot of other students, in a variety of disciplines.
crap is always a part of life. and in the instance that you tell someone to cut it, offer up another solution in dealing with it (we'd all like the advice, I'm sure) and at least have the cajones to attach a name to it.
here are some of my suggestions; not knowing any specific problems they are as general as the problem stated. Go with your gut instinct, don't over-think things - try to develop the simplest, first idea that you come up with. Don't over complicate anything- layering is good but at basic concept level it should be so utterly simple that you might even be embaressed to present it in class - if it is a good solution ( as it probably is ) any good professor should recognize this and maybe help offer suggestions to lead you in the right direction. I always appreciate my student's being honest with me and not layering the crap on top of a simple, basic GOOD idea / concept. Not sure what your relationship with your professor ( or if there is one ) is; undergrad may be more simple. This is my general suggestion at cutting the crap - simplify it down to it's basic concept to present and work FROM it -not adding additional layers / concepts / ideas
And in the end -it's just school, not life or death - it's not the grade that matters but the learning process. Try to enjoy this because in practice it's quite different.
Thanks for the explanation...I understand what you mean by cutting the crap now...and I appreciate you offering some insights.
It's a graduate program, so I am completing a thesis...here, they place an emphasis on the framework we have created to investigate architecture. That has been much of the struggle...defining the conceptual framework. So, now, as I more clearly ground some ideas I have, I am starting to get a sense of what I need to do...
Thanks for reading and commenting. I hope you've found my experiences somewhat familiar...
Alas, I never attended grad school and even though it was about 20 years ago it all sounds oh so familiar. Keep up the good work and the interesting blog!
Post a Comment
Subscribe to Post Comments [Atom]
<< Home