Many things I can author. Few others, I cannot. However, I can usually
head somebody in the right direction in order to find what he or she seeks.
Actually, I wouldn't mind starting an independent business in my area for
customization for architects and designers.
--
_________________________
Bill DeShawn
bdeshawn@nospamsterling.net
http://my.sterling.net/~bdeshawn
"pkirill"
wrote in message
news:5566930@discussion.autodesk.com...
I would make a small mod to one of james' comments: You can't properly
automate what you *don't understand*. I am not an engineer or architect but
I provide automation for both. The trick is in being able to
identify/understand the need in the way it is explained by an arch or eng.
That is not to say it wouldn't be a huge benefit to be able to author it -
sure would save me some time...
"James Maeding" wrote in message
news:5562761@discussion.autodesk.com...
Actually, if you have enough people doing production, a CAD manager can be
worth more than an architect.
You get a medium sized firm that lives and dies by customization, and that
programmer becomes valuable.
I do feel that you can never properly automate what you cannot author.
If you cannot do the plans, you cannot create automation that is really top
notch.
You can automate what the designers think they need, but will not be able to
mold things to what your experience tells
you can be done.
Many times just being able to support and fix existing automation for new
acad versions is enough though.
Bill DeShawn
|>Your CAD duties no matter how complicated or specialized, will ALWAYS play
|>second fiddle to your architectural abilities. I'm not cut out to be an
|>architect and the architect I work for is not cut out to be a CAD manager.
|>Some (like Dean, for example) don't think I should even ATTEMPT to be a
CAD
|>manager. However, I'm the best that the architect is willing to pay for.
I
|>do wish I had better programming education. I don't like to "just get
by".
|>So, sometimes I spend hours upon hours trying to get what I want out of a
|>relatively long routine, when somebody else would have had it done in 20
|>minutes. Persistence pays off, however, and I must admit that I've done
|>some pretty good work. Much of the work I've done has been made
meaningless
|>as new features become standard with the program. Boy, do I digress!
Back
|>to your comment: An architect is NEVER going to pay a CAD guy as much as
he
|>pays himself, no matter HOW much talent he has. But that's all the more
|>reason I do that much more for him. The more he makes because of the
|>productivity enhancements I create, the more I make. The more I am able
to
|>do, the faster the money will flow.
James Maeding
Civil Engineer and Programmer
jmaeding - at - hunsaker - dotcom