Tuesday, October 21, 2008

Revit Semantics, AND a job change!

I discovered something in Revit tonight, when a colleague asked me a question about a specific command, and then i realized i hadn't been here in some time. More so, i realized that my last couple of posts here have all said that i would come back to expand on them, and that i never had. It hasn't been lack of wanting, but in both Revit and Architecture: it has been a long few months.



It started with the tool of Revit, but it didn't end there. Still, in my first post here i indicated this would be more on the journey as i perceived it using Revit, and less of a "how to" in using the tool. There are far smarter people than me to teach you all. :) What transpired isn't all tool related, but since Revit began the journey: Here is my story.



A funny thing happens when you start to use Revit. Well, i digress. If you're using it the way *I* think it should be used, something interesting happens: You either fail, or you learn how things get built. You cant model correctly if you don't know what you're modeling. So, being fairly green in the profession, i asked a TON of questions, and learned rather fast. As the knowledge started to grow (due MAINLY to the two men i worked directly under, who were fantastic for my career growth. Thanks NCG and DEC!) i started to be able to move on my own. I learned the ARCHITECTURE.

As YOU all know, aside from THAT venture, once you start to progress your architecture, you start to see shortcomings in the organizational structure of your REVIT... Maybe in your revit strategy. You modify, you refine, you progress the PROCESS, WHILE you progress the architecture.

You realize you need conventions where your office has none, you need instructions where your office has none. You start to use tools, and that means teaching. You start to brainstorm with collegues, and that means testing. You guys are figuring things out, and talking to the people in charge. There are more meetings, there is more implementation, and on it goes.

But after a while, something interesting happened. I had learned enough from my superiors to move ahead, and help them do more... And on the Revit side, i had started pushing the office pretty hard. I was teaching them more tools, wanting more from the model. The client wanted more from the model, and i knew we could do it... But, as you ALL know, not everyone shares that dream.

Suddenly, something else started creeping in to the workplace: Resentment. Bullying. Sabotage. Infantile, maybe, but after a while we tire of the fight. For a long while i tried holding on to my somewhat advanced position in both architecture AND Revit, but there was a time when i knew it was detrimental to my mental well being to remain.

For a short while, as i considered a job change, it looked very much like i may have been throwing in the Revit Towel, as jobs in the area aren't aplenty using Revit, and with my house purchase and general state of content in the area, I'm not keen on moving. I'm not done here.... YET.

But i lucked out, and have transitioned to another Revit house. I am learning as i go that "Everywhere you go, there you are..." and that every day is a different fight. What i do know is this: I love this tool, and more than that i love doing Architecture. the new gig aside, there are some other things in the works that will hopefully assure that i ALWAYS stay involved in Revit and Architecture... So we will see.

For now, ill let go of my more frustrated tone, and hope to get back in to the geekishly interesting!

3 comments:

RobiNZ said...

As we transition it's interesting that much of the Project/Object management we established for ACA (before Revit happened) is migrating nicely to Revit.

The biggest pain point was choosing "-" as a Name/Field delimeter way back in 2000. ACA handles it fine in formulas but Revit wants to subract stuff!

Malleristic-Revitation said...

The offices that worked together in the past to come up with their solutions will undoubtedly be successful in their transitions...

Sadly my journey has shown that offices with hierarchy for the sake of hierarchy are the ones that have a long battle ahead.

Understanding the semantics of using Revit is a quarter of the battle, making everyone else understand it is about half, and (in some cases) that last quarter is getting them to listen to you once they understand what youre saying! LOL!

Steve G. said...

Good Luck with your new employer MR. Your insights here are much appreciated.