I follow a lot of blogs. I really enjoy gaining information that will help me with the technical and procedural side of architecture, but I also like hearing things I don’t quite agree with that challenge what I think. Greg Arkin at Revit3D.com tends to post in a way that provokes me to thought. .-) I read and responded to this post yesterday, and figured I would repost it here too.
Greg, people hear what they want to hear. If you want to hear people talking about AutoCAD Architecture, subscribe to those blogs. There are a number of them out there, including my own.
Second, it’s not really that difficult to use Project Navigator in ACA, with its Constructs, Elements, Views and Sheet Set. Either that, or I am an outright genius for being able to grasp it. Feel free to pick one, or both.
.-)
Third, whether it’s Revit or ACA, it’s no problem for people to become ‘comfortable’ with using it in a week, but that doesn’t mean they’re anywhere close to fully (or even largely) grasp it. It simply takes time to learn a program enough to know how to handle situations that require something other than the step-by-step procedures you’ve learned in a week. Don’t get me wrong, it’s a necessary foundation, but who declares a building finished after the slab is placed?
Finally, to truly make a software platform shine, you need an expert (preferably in-house) who can develop and evolve processes and support the users in a way that will bring the most benefit to their individual firm. Each company has its own ideas about what its goals are and what are the most profitable processes to accomplish those goals. These processes must be weighed and executed carefully whether your are Architect, Engineer, or Contractor.
Daily Occurrence 