Skill vs Power: Learning BIM
If you have six minutes, please do yourself a favor and watch this video. But instead of thinking about video games, think about BIM adoption in firms. Specifically think about people learning ArchiCAD, Revit, or one of the other BIM authoring tools out there.
Here’s the best analogy from the video, or an approximation at least. If you’re under 40, you’ve probably played Street Fighter II. Or something very similar. In Street Fighter II, there was this dick move you could do with just about any character. You’d move towards your opponent hit something like up,down,A+B and you’d kick your opponent down. By the time their character stood up, you’d have moved forward and already pressed up, down, A+B again. With no opportunity to react, your opponent would get knocked down again. This was repeated until you’d won and your friend was angry. The move took no skill, but it was very powerful. As long as you were fighting other people who were of equally low skill, you’d always win. But this move became completely useless once you fought the kid who knew to roll when his character stood up; or knew to stay crouching; or I don’t know, I wasn’t that good at Street Fighter II.
The point being this: a move like that is about power, not skill. It’s good against low skill or low complexity opponents.
Learning BIM (and BIM applications) is no different. You might have early successes with basic or crude moves, but if you just rely on these early techniques you are are going to fail in the end. To move down the path of BIM from lonely little bim to Social BIG BIM your skills need to improve. You need to learn how the programs work; how to think BIM; how your models need to evolve; how your documentation needs to evolve. This is the paradigm shift everyone talks about. It’s easy to model. It’s also VERY easy to model in a fashion that works but creates a bloated, slow model. A model that does not create profits for the firm; a model that can not be used for higher dimensional extraction (time, cost, energy, sound, touch); a model that can not support augmented reality. Or more simply a model that is difficult to document and useless for rendering or real-time exploration with the client. That basic failure is due to modeling through brute force and power. A model done with skill might be harder to do at first, but easier in the long run to change and much more robust.
If you’re not focused on developing your skills, you will hit a wall which is impossible to surpass. Power not rooted in skill will always fail you when things get tough. We’ll need to revisit this topic in the future because isn’t this also at the core of why we all need to learn BIM?
Power is easy. Skill is hard.
If you’ve played role-playing games (especially early Dungeons & Dragons) then you are probably familiar with the phrase “I disbelieve.” This declaration was a form of meta-gaming-of doing something that the character shouldn’t know, but that the player does. The classic example was when a party came to a dead end corridor in a dungeon or castle. Nothing but stone all around them. The characters had no reason to believe that anything was amiss. But the players had run through plenty of adventures before. They knew that the wall had to be an illusion. There had to be magic hiding the route. The result is everyone would yell “I disbelieve!” They were declaring that they were willfully ignoring the reality of what was presented to them because they knew it was false.
When people say “I know people who…” followed by some poor practices that back up their views-like modeling in another program and using ArchiCAD only for 2D documentation-I want to yell “I disbelieve.” When people tell me that “They know what they’re doing” followed by “ArchiCAD just can’t do X, Y, or Z well”, I want to scream into the phone “I disbelieve.” When people tell me that “They are using everything ArchiCAD has to offer, or most of it at least” and then continue ‘And quite frankly SketchUp is taking the lead”, I want to walk away then holler “I disbelieve.”
The next time you are struggling to learn a new program, tool, or process, stop and think “am I trying to force my way to success through sheer power or am I taking the time to learn the skills I need to succeed?” And if you look around and see people failing all around you, claiming that whatever they want to do is impossible or beyond the capabilities of a fine program like ArchiCAD or Revit or SketchUp, pause for a moment. Proclaim “I disbelieve” and look past the illusions they have built around themselves.
If you could do it over again, would you go to school and study video game design instead of architecture? I probably would. But there’s no time machines for us to use. So instead, follow Shoegnome on Facebook and Twitter for more on being an Architect in the 21st Century.
Andrew Dwight
I hear what you are saying Jarad but I have not seen any of your designs that have been carried through to construction. I gather you know a lot about Archicad and Revit but I have not seen one of your models or one of your projects would you share one with us all?.
There are many needs for BIM yet there is a big restriction when it comes to BIM in the industry and that is time and money. Sure better methods reduce the time and size to create a model but these methods have to be learned. Creating a bloater is a real no no yet creating a higher poly model on a small project is not a deal breaker. On the other hand creating a heavy hospital room and recreating it 500 times is a massive issue and eventually a redraw by a more experienced operator.
It may be a good idea to explain how you recommend to keep from creating a bloater. My personal opinion is using components with the correct level of detail required. There is no point drawing every nut bolt or screw in anything never mind a light fitting. This is not even required when doing a render of a room. A larger model such as a hospital only really requires components that are adequate to recognise the actual PC item. Low resolution images or textures are a huge contributor to bloating the same way ridiculous amounts of geometry are in an easily recognisable item such as a toilet. You can find some examples that we did of components in Archicad Revit & Sketchup on RubySketch.
All programs Revit, Sketchup and Archicad all have a threshold for the amount of information they can handle efficiently and all of them have their own advantages and deserve to be part of the tool kit of a professional architect, designer or builder. I like you “Disbelieve” that the current state of Sketchup is taking the lead but I do think that it has the potential to do so. There are Sketchup users and there are Sketchup users. The biggest “knockers” are the Sketchup users that are lower in knowledge base therefore making their opinions should I say unbelievable….
Regardless of what software a designer uses the end result should fit the client brief and the paper work that is required from the model. It is up to the individual to make this decision and make mistakes as they go. The key is to learn from the mistakes you made and seek the answer through appropriate channels. An even better way is to learn from other people mistakes. I encourage the use and training of all three packages as each have their strong points.
One thing I think that is truly disappointing in the BIM industry is the the so called “BIM experts” that flex their muscles and feel it their god give right to slam and ridicule people for making mistakes or incorrect statements. I bet my right testicle most of these people have made the same mistakes and the ones who have not probably don’t even know what they are talking about. I thought bullying was for children in the school yard but it appears as the Linkedin has a couple of tough bully boys flexing their week little fingers behind a key board getting their jollies out saying look at me look at me. Pathetic in my view.
Thanks for your Blog Jared I read it when I am not designing, building or BIMing. I hope to give more input when I can
Kind Regards Andrew Dwight
AAD Build
RubySketch
Jared Banks
Andrew,
Great comments. If you are interested in expanding some of these points into a guest post, I would be all for that. I’m sure this all ties into your mission over at RubySketch? Model complexity as it relates to final deliverables is an awesome topic.
I know a lot about ArchiCAD; I’m just an observer of Revit. From an academic standpoint, I’d be very interested in learning Revit, but I don’t have the time/the time I have should really be spent doing other things… My work (descriptions, explanations, and images of) is all over this site and http://blog.graphisoftus.com/author/jared, among other places. Both here, but increasingly so over at the GSNA blog and my ArchiCAD tutorial youtube channel http://www.youtube.com/shoegnomellc I’ll definitely continue to share my methods and thoughts on smart ways to work in ArchiCAD. And that includes keeping bloat down. This is definitely a huge topic and one that has parts that are program specific, project-type specific, and general theory (which is what this post is about). Also as it’s related to all this, I think project scale is the wrong focus; it’s complexity that matters more: http://blog.graphisoftus.com/concept-design/its-not-about-scale-its-about-complexity
For clarity, I’m not knocking SketchUp in that one example, more pointing out that I don’t believe the person talking to me really knows the program they claim to be an expert in. Two completely different situations. SketchUp can do some wonderful things. I know I have a tendency to default to SketchUp bashing and I really don’t mean to. After years of fighting with coworkers about why we need to stay focused on improving our ArchiCAD skills instead of defaulting to another solution when things get tough, it comes a little too naturally. That is for a separate series of posts. But again that’s exactly one of the points I’m hoping to make here. Until we’ve invested in developing our skills within Program A, it’s dangerous to get too rosy eyed about what else is out there. Or more to the point, dangerous to condemn the solutions we claim to focus on until we’ve genuinely put in the effort.
There’ll always be bullies, sadly. Hopefully those of us working to share openly and honestly in a manner that aims to help others will continue to trump their negativity. Or that’s what I keep telling myself!
Glad you’re enjoying the blog and I look forward to more of your thoughts. Thanks.
RubySketch
Well said Jared.
It has been a while since I posted this and to my embarrassment I had not seen the video as I was on my phone when I read it.
The video is a great analogy and it leads to a lot of the issues that relate to BIM. Unfortunately getting anyone’s head around BIM creation is a time consuming ordeal that many decide to stay away from as it eats into productivity in the short term.
To all of those who feel this way don’t be discouraged there is a light at the end of the tunnel. Many of us have decided to take on the task and for this reason may be more successful in the future. In saying this the age old issue of technology may hamper efforts for some yet increase usability for others (EG 8 track, records, tapes, cd’s, MP3 and Spotify) All I can say is try not to put all your eggs in one basket. It takes many tools to complete a task and Archicad, Revit and Sketchup are soem of the more powerful.
As I mentioned in another post I am doing what I can to create a unique BIM platform (on top of Sketchup) that may appeal to the masses in a more simple and cost effective form. It would be untruthful to say I have it down pat, although I believe (Beta testing will tell me more) I have incorporated an easier to use interface in a lower price bracket. I encourage you all to try it and give me your feedback while it is still free. Currently Australia is getting the first trial and few chosen individuals around the world. By all means register for BETA testing on our website if you would like to be involved.
I thank you Jared for your well written and informative blog and I would love to become a guest blogger or help answer question when I can.
Regards Andrew Dwight
Jared Banks
Andrew, sending you an e-mail now!
Jonnel Mamauag
If I could turn back time, I’d still study Architecture – love it to bits! But this time make the most of it, and work smart along with working hard. Sooo much time wasted on just following what my professors are saying. And find internships like a hound!
Video games are fun though …
Jared Banks
Jonnel, well said! I’d definitely do things a little different if I where to do Architecture school again too. Or at least I’d like to think I would. 🙂
Probably should write about that…
Antonio Tort
Great post Jared. What you say is absolutely true. Particularly when you talk about people telling you that “They are using everything ArchiCAD has to offer, or most of it at least”.
Well, I’m just in the opposite site. Since that old ArchiCAD 4.5 until now, the more I use this incredible architectural tool, the more I know how far am I to imagine where is the limit.
Jared Banks
Same here… for every trick I discover, it opens up three that I need to learn. It only seems to get worse the deeper into ArchiCAD and BIM I explore.
Pingback: Do you love your BIM software too much? » Shoegnome
Pingback: Of Bows and Arrows and Machine Guns » Shoegnome
Nofal
Great video Jared! I am also an avid gamer and still use the noob sawed off on GOW3! hahaha. However, I think gaming and architecture require different cognitive skill sets. In gaming it is mostly about hand-eye coordination, quick reflexes and tons of practice. In architectural design, it is more about imagination, creativity, patience, public speaking and so much more. I have been designing for seven years and too many times I have seen bland designs come out from what are otherwise superior platforms.
Jared Banks
Thanks. Before you sell games short, you should check out some more Extra Credits videos: http://www.penny-arcade.com/patv/show/extra-credits
While I agree that practice, quick reflexes, and hand-eye coordination are central to many video games, mastery involves something more. Patience, creativity, imagination, problem solving, etc.
Pingback: Roommate Test of Manhood - Shoegnome