{"id":228,"date":"2006-06-15T21:44:00","date_gmt":"2006-06-16T05:44:00","guid":{"rendered":"https:\/\/www.caddmanager.com\/CMB\/2006\/06\/15\/seven-deadly-sins-of-autocad-users\/"},"modified":"2016-02-11T16:41:41","modified_gmt":"2016-02-11T23:41:41","slug":"seven-deadly-sins-of-autocad-users","status":"publish","type":"post","link":"https:\/\/www.caddmanager.com\/CMB\/2006\/06\/seven-deadly-sins-of-autocad-users\/","title":{"rendered":"Seven Deadly Sins of AutoCAD Users"},"content":{"rendered":"<p>Well at least the first four.<\/p>\n<p>I posted this article in AUGI Hot News for June 2006.<\/p>\n<p>If you look around you can see repeated patterns of CAD troubles. \u00a0People get themselves into trouble often by doing the same things. \u00a0As I observed these patterns of behavior, I came to understand that there is \u201cnothing new under the sun\u201d.<\/p>\n<p>Presented in no particular order\u2026<\/p>\n<p><b>Sin #1: \u00a0Not Reading the Book<\/b><\/p>\n<p>If you have read my stuff before you realize that this is one of my forgotten habits of CAD users. \u00a0Not reading the books and info you can get your hands on is like trying to install a garage door opening without reading the installation instructions. \u00a0Read the articles in the January, February and March issues of Hot News.<\/p>\n<p>&nbsp;<\/p>\n<p><b>Sin #2: Not developing Standards<\/b><\/p>\n<p>By \u201cdeveloping\u201d I mean creating, defining, reviewing, updating and enforcing a CAD Standard.<\/p>\n<p>Everyone has one anyway. \u00a0All users are creating objects in some form of a standard way. \u00a0They may be using their own \u201cpersonal\u201d standard, but they are most likely using one. \u00a0It may be written or just in their head, but they do have habits and processes that they use.<\/p>\n<p>Standards drive the unification of producing CAD files.\u00a0 Standards allow us to share project development better through unified methods, layers, processes, and production shortcuts.\u00a0 We can automate the way something is produced and provide a target for file structure.<\/p>\n<p>They drive the automation of creating data, but they don\u2019t really guarantee that the data will be technically correct or interpreted correctly.<\/p>\n<p>So if you don\u2019t have one \u2013 create one and share it.<\/p>\n<p>If you have one \u2013 review it and refine it<\/p>\n<p>If yours is good \u2013 enforce it.<\/p>\n<p>If it gets in the way \u2013 jettison it (but make sure you come back and correct the bad files \u2013 see Sin #3)<\/p>\n<p>&nbsp;<\/p>\n<p><b>Sin #3: Going overboard on Standards<\/b><\/p>\n<p>Some users are so head strong on Standards that they fail to get the job done. \u00a0They impact project deliverables by spending too much time getting it right. \u00a0Now, before you run me out of town on a rail, understand that I think good standards should not over tax your production flow. \u00a0Automated standards (those imbedded into the software through customization) should work well for speed and accuracy.<\/p>\n<p>But, from time to time you will have to get something out the door in a pinch. \u00a0My thoughts are to stop worrying about the standard to get the job out and then go back and fix the files. \u00a0Most people do this anyway, but often fail to go back and fix the files. \u00a0I think many CAD Standards violations are done with the knowledge that the user is breaking the standard. \u00a0So why not just admit it and get the job complete and go back an fix the files. \u00a0Don\u2019t let them be swept under the rug because someone if \u201ctoo scared\u201d to admit they made some mistakes.<\/p>\n<p>NOTE: Standards can be set aside, but never accuracy. \u00a0The technical content of a file MUST always be exact.<\/p>\n<p>&nbsp;<\/p>\n<p><b>Sin #4: Using the software like it was still a previous release<\/b><\/p>\n<p>We all do this. \u00a0We all have some old habits that are still working for us. \u00a0I do not think we should abandon them all, but some of them are trapped in old releases. \u00a0If you have upgraded, please find out what has changed in the new release and see if you need to start doing something differently.<\/p>\n<p>Autodesk carries a lot of old baggage from prior releases. \u00a0They tend to not remove commands or tools that are long overdue for retirement. \u00a0REDRAW still exists in 2007 even though most of us now can easily do a REGEN in the same amount of time. \u00a0In fact, \u00a0I would have trouble finding a command that was removed in 2007 that existed in 2006 (except the 3d stuff). \u00a0Why? \u00a0Because we all still use the old stuff \u2013 forever.<\/p>\n<p>Now you may say \u201cwhat\u2019s wrong with using old tools that still work?\u201d \u00a0There may be nothing wrong with the command, but you may be handicapping yourself to discovering new tools. \u00a0Watch a new user and see how they work. \u00a0I bet it would be very different from the way you work.<br \/>\nThe real concern is when you move up from AutoCAD to another high end tool like ADT, Revit, LDT, Civil 3D, or Inventor. \u00a0No you may actually be causing problems by using the new tool the same way you used the old one.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Well at least the first four. I posted this article in AUGI Hot News for June 2006. If you look around you can see repeated patterns of CAD troubles. \u00a0People get themselves into trouble often by doing the same things. \u00a0As I observed these patterns of behavior, I came to understand that there is \u201cnothing [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"footnotes":""},"categories":[86,13,4],"tags":[],"series":[],"class_list":["post-228","post","type-post","status-publish","format-standard","hentry","category-augi","category-cad-management","category-tips"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/posts\/228","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/comments?post=228"}],"version-history":[{"count":3,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/posts\/228\/revisions"}],"predecessor-version":[{"id":3522,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/posts\/228\/revisions\/3522"}],"wp:attachment":[{"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/media?parent=228"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/categories?post=228"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/tags?post=228"},{"taxonomy":"series","embeddable":true,"href":"https:\/\/www.caddmanager.com\/CMB\/wp-json\/wp\/v2\/series?post=228"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}