.
couple weeks ago in austin, i met up with an old architecture-school buddy who, unlike me, stayed with the profession, and who over the course of a few premium margaritaswhipped up by an equally-premium lil' bartender who couldn't stop talking about how helplessly drunk he got whenever he imbibed tequila, all the while casting significant glances my way (and yeah, he got a big tip)
filled me in on the current state of the art.
while i probably pull down far more coin in my glorified "want fries with that?" job than does said friend in the highly technical and specialized position he's so painstakingly built for himself over the last 20+ years [and for which sorry state of affairs feel free to blame the profession of architecture rather than my lazy, underachieving ass, ok?], our conversation still made me think.
and i mean long and hard--about what i'd walked away from all those years ago, and why.
to the point that when i got home, i set myself to googlin'--and while in my waning twilight years i'll probably never have the time, money, knowledge base and/or attention span necessary to master the current professional standard, i figured i might as well take a shot at google's low-rent alternative.
so i downloaded it.
two weeks ago:
my first model--i was so proud it turned out just like the one in the tutorial that i saved it.
last night:
point of this post: if 3D modeling software had existed back when mkf first contemplated abandoning architecture, the world might be very different today (ok, maybe only mkf's world, but whatever).
as for the half-finished kitchen above (not to mention the rest of the goddam house): more to come.
