Category Archives: Interview

The BLADE video watchlist

I did my third and final (for now) BricsCAD Unplugged webcast about BLADE last Wednesday. Here’s the video:

Before I dig into DCL, I start with a brief description of an absolutely brilliant feature that was added to BLADE in V19. If you code in LISP, you’ll love this feature.

Then I move on to some ancient history. Did you know that we can thank the far-sightedness of some slightly renegade Autodesk OS/2 developers in the early 1990s for the dialog boxes we use today? Did you know that you could program dialog boxes for AutoCAD for Mac in 1993 but you can’t today? Can you spot the items of interest in the background?

The rest of the video is dedicated to describing DCL programming and debugging, and I explain how BLADE is the best tool for that job using examples.

If you want to watch all three of the BLADE videos in a row (that’s 1 hour 49 minutes of viewing), Matt Olding has created a YouTube playlist for this series.

It has been an absolute pleasure working with the Bricsys people in putting this series together. Torsten Moses has informed me about yet another bunch of enhancements that are coming very soon to BLADE, so maybe you haven’t heard the last from me on this subject on BricsCAD Unplugged.

More BLADE videos

As mentioned previously, In December I made a guest appearance on the BricsCAD Unplugged webcast series to discuss the LISP development environment, BLADE (YouTube link).

I made another appearance last week describing debugging using BLADE (YouTube link):

If you’re dealing with LISP code for AutoCAD and/or BricsCAD, you really should be doing it in BLADE. It’s the best development environment for AutoLISP/Visual LISP that you’re ever going to get.

I have another appearance scheduled for later today (13 February) in which among other LISPy things, I will be discussing using BLADE for DCL programming. Again, even if you’re AutoCAD-only, I believe this is worth a watch. BLADE is better for DCL programming, too.

Even if you’re AutoCAD-only and not a programmer, you might find my brief ancient history lesson of interest. Did you know that BricsCAD for Mac users can thank a far-sighted early 90s Autodesk OS/2 team for the dialog boxes they use today?

The BricsCAD Unplugged webcast broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube. Today’s session will start at about UTC 14:15 (2:15 PM) on Wednesday, 13 February 2019 (click here for your local time)

Link

My Real World BricsCAD series of posts on the Bricsys blog continues with more from the in-depth interview at Schrack Seconet.

Part 1 | Part 2 | Part 3 | Part 4 | Part 5 | Part 6

 

I hope when people read these things they can see that I’m probing for problems, issues, difficulties, and so on. That’s the sort of thing that those people who are considering switching to BricsCAD are going to want to know about before diving in.

I’m grateful that Bricsys is OK with me covering their products like this on the Bricsys blog. Some CAD companies only allow super-positive things to ever be uttered about their products from their corporate sites. Bricsys is different.

Video – who is that masked man?

Last night I made another guest appearance on the BricsCAD Unplugged webcast series. This time I was discussing the LISP development environment, BLADE. Here’s the video:

Bonus points will be awarded for identifying three items of interest in the background. No, not counting my dog Sunday asleep at lower left.

Despite going way over time, there was still nowhere near enough opportunity to describe the full LISPy awesomeness that BLADE represents. I am therefore scheduled to return for another two or three episodes beginning in February. In those, I’ll be doing more of a step-by-step demonstration rather than the overview and V19 new feature description I did in this episode. If you have any particular requests for what you want covered, please comment on this post.

I also showed how the tools in BLADE (e.g. the (inspector) function) are still worth having for any DWG-based CAD Manager or power user, even if you’re not a full-on LISP programmer. If you have to work out what’s going on with dodgy DWG files, you’ll want to have (inspector) in your set of tools.

The BricsCAD Unplugged webcast broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube. This was the last episode for 2018 because of Christmas and New Year.

Wielding BLADE on BricsCAD Unplugged

In September I was the special guest on the BricsCAD Unplugged episode BricsCAD Unplugged – Steve Johnson 5 surprises moving to BricsCAD. Next Wednesday I will return, this time to wield BLADE, the best thing to happen to CAD LISP in nearly 20 years. I’ll be introducing it and demonstrating a few things, including the new features that came with V19.

These live broadcasts are run on the Bricsys Facebook page and are then quickly transferred to YouTube. This broadcast will start at UTC 15:00 (3 PM) on Wednesday, 19 December 2018. Here’s that time in a few handy time zones:

Location Zone Time
San Francisco PST 07:00
Minneapolis CST 09:00
New York EST 10:00
London GMT 15:00
Brussels CET 16:00
Moscow MSK 18:00
Mumbai IST 20:30
Perth AWST 23:00

My Real World BricsCAD series is coming soon on the Bricsys blog

In February, my first Bricsys blog post appeared:

Inside Bricsys: Interviewing the creator of BLADE – the new Visual LISP IDE in BricsCAD V18.2

This was an amalgamation of my two similarly named posts on this blog where I interviewed BricsCAD’s Torsten Moses about BLADE, the LISP IDE that arrived with BricsCAD V18.2.

Today marked my first original-material post on the Bricsys blog:

Real World BricsCAD Series Coming Soon

I encourage you to hop over to the Bricsys blog to check it out. I’ve been interviewing real people about their use of BricsCAD and will be reporting what they have to say.

Disclosure: Bricsys is paying me to interview these people and produce these pieces.

Bricsys is not, however, paying me to sugar-coat anything. I’m being left alone to interview who I like and write it up as I see fit. A quote from today’s post will give you some idea of what’s in store:

The posts in this series aren’t going to be your average corporate-waffle puff-pieces. I mean, who reads those things anyway?

If you have used BricsCAD and are willing to be featured in this series, I would love to hear from you. Please contact me using this form and I will be in touch. In addition to the interviews in the pipeline, I have already had my first response to this invitation. A site in Austria with 70 users and lots of custom programming sounds like something I can get my teeth into.

Video – Steve on BricsCAD Unplugged

Following on from Lynn Allen and Robert Green’s guest appearances on the BricsCAD Unplugged webcast a couple of weeks ago, this time it was my turn.

Last night (my time) I was the special guest on the episode BricsCAD Unplugged – Steve Johnson 5 surprises moving to BricsCAD. I’m introduced at 2:12 and appear at 3:30. Here’s the full video:

In this week’s episode, you’ll witness:

  • Me discussing the five biggest things that pleasantly surprised me about BricsCAD. (I have more than five, but time was limited).
  • Don Strimbu bribing me with drinks containers.
  • An actual printed copy of Cadalyst magazine from 1995, complete with my old column Bug Watch (1995-2008).
  • The excellent euphemism, “You’re generally pretty conservative in terms of your praise.”
  • Don throwing me a curveball by introducing my points out of order!
  • The announcement that I’ll be at Bricsys 2018 in London and possibly participating in the BLADE session.
  • Me saying, “No. I’m wrong.”
  • Me drinking a glass of wine (parental guidance advised – alcohol consumption depicted). If you care, it’s a Shiraz (that’s Syrah if you’re American) from South Australia’s Limestone Coast region.
  • Total lack of coordination from everyone in raising our drinks at the end.

Thank you to the Bricsys crew for the invitation, it was a blast! If you ever want me on again, I’ll be happy to oblige.

For future reference, these live broadcasts run on the Bricsys Facebook page and are then quickly transferred to YouTube.

Mac users rejoice – at long last, a LISP IDE comes to OS X

CAD’s best LISP development environment has come to the best “AutoCAD for Mac”. It should come as no surprise to anyone that this has occurred without Autodesk’s involvement.

What’s happened?

With the release of BricsCAD (Mac) V18.2 (currently V18.2.23-1 to be precise), BLADE (BricsCAD’s much-superior equivalent to VLIDE) has been added to BricsCAD

See here for the release notes and here to download. Make sure you select the Mac version:

Significance

This is pretty significant for anybody serious about using DWG-based CAD on the Mac. AutoCAD without LISP is hardly worthy of the name, which is why I’ve never been keen on AutoCAD LT from the moment LISP was yanked out of it just before release in the early 90s. There has never been an integrated development environment for AutoCAD for Mac (either in the first iteration in the 1990s or the second attempt in the 2010s) and I think I can safely predict that there’s never going to be one. I expect AutoCAD for Mac’s LISP to remain forever in 1990 mode.

Compatibility

One problem a small number of users may face when developing for Mac with BLADE is that of downward compatibility. In case you’re wondering, BricsCAD (Mac) to AutoCAD for Mac is very much a downward direction, particularly in the area of LISP. The LISP in AutoCAD for Mac is famously half-baked with large portions of functionality missing, including no ability to control dialog boxes. BricsCAD (Mac)’s LISP is very much more capable, so while compatibility between AutoCAD for Windows and BricsCAD (Mac) is strong, you can’t say the same for LISP compatibility between AutoCAD for Windows and AutoCAD for Mac.

Half of the stuff you write for AutoCAD in Windows is just going to fail when you try to run it in AutoCAD for Mac. Much more of it is going to work in BricsCAD (Mac). While you can now write, debug and run your LISP code efficiently in BricsCAD (Mac) and it’s practically guaranteed to run just fine in AutoCAD and BricsCAD for Windows, it will be very easy to write stuff in BricsCAD (Mac) that doesn’t work in AutoCAD for Mac. Of course, the same downward compatibility problem applies to writing stuff in AutoCAD for Windows using VLIDE.

If you’ve moved on completely from AutoCAD for Mac to BricsCAD (Mac), that’s not going to be a problem. Bircsys building a notably better product that’s significantly more compatible with the main game is not something anybody could reasonably condemn. However, but it’s something to bear in mind if you are hoping to write code that runs on both AutoCAD and BricsCAD for Mac.

Summary

That caveat aside, it’s all good news for Mac CAD users. You already had a product available that would run a much higher percentage of the huge library of LISP out there than AutoCAD for Mac would. For the first time in history, you now also have access to a professional LISP development tool. Lucky for you, it’s the best such tool on the market.

IPoC interview – Lynn Allen – part 3

This is the third in a series of interviews of Interesting People of CAD (IPoC).

Lynn Allen is a legendary figure in the CAD world and really needs no introduction. I’m very happy that she agreed to be interviewed for this series. Here is the third and final part of Lynn’s interview. Learn about Lynn’s departure from Autodesk, people’s reactions to the news, and what Lynn thinks about Heidi Hewett going to Bricsys. Also, Miss Tiffany.

Steve: So after all these years, you’re no longer with Autodesk. Was that a shock to the system?

Lynn: After 24 years, it is so hard to train myself to say “they” instead of “we”… I’m still working on that. People who know the inside scoop know that I’m much happier now that I’m on my own. And I’m looking forward to possibly taking my skills, expertise and followers to another company, especially if I can find one that is truly focused on the customer. Or perhaps I’ll continue doing what I’m doing, working as a consultant.

Steve: Many of your long-time colleagues and friends also parted ways with Autodesk at the same time. Do you have any idea why so many highly experienced people were chosen this time round?

Lynn: I think that Autodesk Management would need to answer that question.

Steve: In my career I’ve been through several work experiences where people were being made redundant around me, and it was never pleasant. What was the atmosphere like at Autodesk while the redundancies were being processed?

Lynn: It’s not unlike other companies – it is always a painful process. I’ve been through it close to a dozen times at Autodesk – it’s always sad. And it’s just as hard, in many ways, for the people who are left behind. That survivor’s remorse. It can take a long time for a company to course-correct.

Steve: Even before this latest reduction in force, I have had people expressing their opinion to me that Autodesk has an ageist hiring and firing policy, and that once people get to about 50 they’re marked for deletion. Do you have a view on that?

Lynn: I can’t really respond to that either. I think you know my views on that, Steve.

Steve: What has the reaction been like from people outside to the news of you no longer being with Autodesk? Have people been supportive?

Lynn: People were shocked – plain and simple. And I spent so much time consoling customers and employees I didn’t have much time to process it myself. I literally had people calling me up and sobbing on the phone – what am I supposed to do with that? I felt just horrible that so many people were upset. I had to talk many people off the ledge. I had people swearing to get rid of their Autodesk products… it was insane. People have been amazingly supportive otherwise – I just can’t emphasize that enough. So many have reached out to me… it gets to me just thinking about it. I feel very fortunate that way (and I can’t thank everyone enough)

Steve: The way I see it, Autodesk stands a good chance of losing out twice in removing experienced, skilled and well-liked people. Not only does it lose those attributes, but there’s a good chance that a competitor will gain them! We’ve already seen that happen with Heidi Hewett going to Bricsys and Brenda Discher going to Siemens. Is it safe to say that Autodesk’s main competitors have all been in touch with you?

Lynn: Yes indeed! And let me say I was insanely flattered. I’m still listening and hoping to make the right decision here. We will see.

Steve: Of course you worked with Heidi for many years. She seems to have taken to her new role at Bricsys like a fish to water! Were you happy to see her land that job?

Lynn: You have no idea how happy I was for her. Heidi is brilliant and one of the most amazing people I’ve ever worked with. Bricsys is so lucky to have her on board. And Heidi is happy – and that makes me happy!

Lynn and Heidi back together again, doing their things.

Steve: It was fun seeing you turn up at Solidworks World before your departure had been made public and getting people guessing! You’ve just returned from Gent in Belgium, I see. Did you enjoy that visit?

Lynn: I have enjoyed all opportunities to spend time with companies in the software design industry. They each have their unique offerings for the design customer and I’ve enjoyed getting to know the various companies better. I have also greatly appreciated those companies who have approached me and their amazing “hospitality” if you will.

Steve: I love Belgium. Great people, wonderful beer. Some pretty impressive software, too! Anyway, I see you have been keeping an active presenting schedule going, mostly attending independent Autodesk software-based events. At one of them you got to share the stage with Sophia the creepy robot torso woman. How was that?

Lynn: She is indeed creepy Steve! It was a unique experience I’m not likely to forget in quite some time. I can tell you that I’m certainly not worried about robots taking over the world any time soon – she kept stepping on my lines!

Steve: It’s good to see you’re keeping up the Cadalyst videos. Is it just me or are you getting a little more, er, carefree lately? Or is that just the cold medicine?

Lynn: I’ve definitely been getting a little more carefree (I must admit the cold medicine sent me over the edge though). Even in my live presentations I’ve noticed I’m more carefree and personally I think I’m a better presenter now – because I can just be me.

Steve: Do you expect to expand your presenting repertoire to cover non-Autodesk software in future?

Lynn: Anything is possible!

Steve: Last question. What question do you wish I’d asked you?

Lynn: Wow, what a question! How is my dog Tiffany? She’s doing great, thank you for asking!

Miss Tiffany doing her thing.

IPoC interview – Lynn Allen – part 1
IPoC interview – Lynn Allen – part 2

IPoC interview – Lynn Allen – part 2

This is the third in a series of interviews of Interesting People of CAD (IPoC).

Lynn Allen is a legendary figure in the CAD world and really needs no introduction. I’m very happy that she agreed to be interviewed for this series. Here is the second part of Lynn’s interview, which includes discussion of travel, gender issues and a nasty poster.

Steve: As Technology Evangelist for Autodesk for over 20 years, presentation was a big part of your job. You have a comedic, apparently casual approach to your presentations that is very popular. How much preparation do you have to put in to make it appear so casual?

Lynn: You have no idea how much planning and preparation I put into my presentations! Those on the inside think I’m a little insane I rehearse so much – but I need to in order to feel confident about my presentations. If I’m not confident – I can’t be myself. All that comedy comes from relaxing and just treating the audience like family.

Steve: Your job involved a vast amount of travel, and I see you haven’t stopped. I once remarked that I didn’t know if you had the best or worst job in the world! Which is it?

Lynn: It’s a little of both, Steve! I love spending time with users all over the world… but the travel can really get to me. It always sounds so much more glamourous than it really is. I really do love being home!

Steve: What are some of the travel difficulties you have had to face?

Lynn: Again, oh boy! How long do you have? I’ve had some real travel nightmares. Missed connection nightmares that turned into very painful sagas. I’ve lost my luggage more times than I can count. And I’ve had food poisoning too many times – ended up in the hospital once as a result. Definitely not very glam.

Steve: Are there any countries you still have left on your bucket list?

Lynn: Absolutely! Greece and Iceland. I’ve been to over 75 countries but would really like to add these two countries to my list.

Lynn, smart as ever, enjoying a well-earned vacation

Steve: One of the things I’ve always admired about you, and I think one of the reasons you’re so popular, is how much of a straight-shooter you are. Of course there are limits to how critical you can be about your company’s products. But you never seemed to shy away from saying things like, “That’s a bit annoying” or, “I don’t know why they did it that way, that doesn’t make much sense to me.” Did you ever get into trouble for being too honest?

Lynn: Good question. While I may have been a straight shooter, I wasn’t saying anything the users weren’t thinking! And I also praised the products like crazy so there was certainly more positive than negative. I don’t remember getting into trouble… the teams I worked with were very willing to take my feedback and try to do something about the issues and concerns. No software product is perfect.

Steve: As a female in a male-heavy field, I know you didn’t have to line up for the toilets at AU too often. But you must have faced some difficulties over the years because of your gender. Can you share some of those, and how you dealt with them?

Lynn: You know – I have always been pretty easy going about the gender issue and have actually been treated with a great deal of respect since joining Autodesk. Let’s remember that Autodesk had one of the first female CEOs and I think Carol Bartz’s presence permeated throughout the company. And it was difficult for someone to challenge my AutoCAD knowledge… just since I’d been doing it for so long and was one of the industry leaders so that usually shut people down as well.

Now before Autodesk – well that was another issue! I once had an ATC professional student insist I go get him some coffee (before class began on the first day), treat me clearly as a subordinate, complain that the instructor was late – only to be shocked to find out I was actually the instructor and was going to be so for the next 4 days. He wasn’t very happy about that!

Steve: You once had a “Win a date with Lynn Allen” thing sprung upon you without your knowledge or consent. I must say that horrified me when I heard about it! How did it go down with you?

Lynn: Well, I’d say they probably thought it was amusing in the grand scheme of things but of course it was totally inappropriate! I didn’t have to deal with it as others came to my aid and put an end to it before I had much of a chance to react. I can’t even remember how we fixed it. I believe whoever won was invited to join a big group of us to dinner. It is funny now!

Steve: Were there any other unpleasant surprises like that?

Lynn: Well the biggest horror by far was the poster size version of my face that was put out by Autodesk Marketing! I freaked out when I saw it – especially when the marketer told me it went out to 250,000 customers! I cried in my office for hours. They didn’t even bother to touch it up – it was awful! My boss was so very sweet – he went straight to the top to complain about it and eventually the person who put out the poster “went on to pursue other opportunities” (it wasn’t his first major marketing mistake). I was traumatized for ages. I’m still traumatized when someone tells me they still have one or they ask me to sign it. Burn your Lynn Allen posters… please!

IPoC interview – Lynn Allen – part 1
IPoC interview – Lynn Allen – part 3

IPoC interview – Lynn Allen – part 1

This is the third in a series of interviews of Interesting People of CAD (IPoC).

Lynn Allen is a legendary figure in the CAD world and really needs no introduction. I’m very happy that she agreed to be interviewed for this series. Here is the first part of Lynn’s interview. Topics include life before Autodesk, that AU wig and user groups, especially AUGI.

Steve: Can you tell me a little about your background before you started with Autodesk? Have you always been involved in teaching and training?

Lynn: I started using AutoCAD with Version 1.4 at American Honda. I then went to one of the first AutoCAD resellers in North Hollywood where I did a little bit of everything, but primarily training. I moved to yet another Autodesk Training Center (ATC) where I became the manager of three ATCs. I also taught AutoCAD at the local Junior College along the way.

Steve: When did you start at Autodesk and what did you do initially?

Lynn: I joined Autodesk in 1994, working in their training dept. Shortly thereafter I became the Training Department Manager.

Steve: I first saw you at AU in 1995 and you were well known and liked then. How did you manage to build up such a following?

Lynn: Well, I like to believe people liked me because I genuinely tried to help the AutoCAD/Autodesk community out. I was involved in AutoCAD since the early days, had a column in Cadence/Cadalyst magazine for over 20 years (before the internet when people used to read for information). I had written several books on AutoCAD and thanks to my job as Autodesk User Group Manager I had a chance to present to Autodesk product users all over the world. I am friendly, I mean well, and I think that shows through in my presentations. I made it a point to never be too busy to stop and listen – I really want to help. I don’t think can’t fake that – people can see you for who you really are on stage.

Steve: What was the story behind the wigs?

Lynn: Well, there was only one wig… a blonde one. At one point I dyed my hair brown and boy did people complain! It was such a sticking point with everyone (it was really unbelievable how upset people were about it). So I walked into one AU and put a blonde wig on the monitor and said “Here you go people, here is your blonde hair!” It got a big laugh, but I do believe it got my point across.

Steve: You were the Worldwide User Group Manager for a while, what did that involve?

Lynn: That was the best job ever! I had the opportunity to work with local user groups all over the world as well as AUGI. My job (as well as my team) was to help them all be successful – support them – be there for them. I had a wonderful team, we all loved our jobs.

Steve: I know Autodesk put a lot of support behind AUGI. What forms did that support take?

Lynn: They provided monetary support, physical support (we helped them with their newsletter as well as other promotional marketing), various events, their website, and made sure they had a big presence at AU since they were instrumental in getting AU off the ground.

Steve: What do you think Autodesk gained, and still gains, from supporting AUGI?

Lynn: Who wouldn’t want to promote an organization full of passionate users? That said – Autodesk has really dropped off of AUGI support (and local user groups) in the past decade or so…it’s really made me sad. For years I stepped in as a volunteer Autodesk rep because they had no one to work with… it was rough.

Steve: I know there were some real characters among the people running those early NAAUG/AUGI boards. Do you have any fun stories you can share about them?

Lynn: Oh boy! Too many to tell… Although I do love the time when AUGI president David Harrington ordered vanilla ice cream (at a very nice restaurant) and they accidentally brought him the one from the dessert tray which was actually Crisco… the look on his face when he took the first bite was priceless! We still laugh about it today.

We had a president we had to impeach because he took the Autodesk software we gave him for User Group door prizes and sold it. That wasn’t cool… We had our fair share of trials and tribulations but it was all worth it in the end. I still have a massive soft spot for user groups!

Steve: I’ve heard from David Kingsley about one side of the controversy over whether AUGI should have been run using a professional management group. Do you have any insights on what went on there?

Lynn: Well, there are pros and cons with that story. AUGI did get some amazing benefits when SolidVapor was working with them as they did so much of the legwork and heavy lifting. They couldn’t do it all for free – they had quite a staff supporting all of their efforts. I also understand how AUGI felt about the situation. I can totally see both sides of the situation.

Steve: I’ve run an Autodesk user group myself, and I know it’s very difficult when volunteers have different ideas about how things should happen. What lessons could be taken from that whole experience?

Lynn: While working with a passionate group of volunteers can be challenging – they are all in it for the better good of the organization. Trying to keep that in mind definitely helps.

Steve: So if you had any advice for somebody starting up a big user group from scratch, what would it be?

Lynn: Find passionate individuals who have the time to dedicate to getting the organization off the ground (a Board if you will). These individuals need to put in a fair amount of time to do the job right. Meeting face to face at least once a year is also essential in my mind – filled with head-down brainstorming and detailed planning. Plus people get to know each other better and become more tolerant of each other. And as a corporation – definitely treat these Board members well! Spoil them a little – they’ve earned it! I have to give SolidWorks (and Richard Doyle) some kudos here – they really understand the value of user groups and have dedicated resources to help them be successful. I love that!

IPoC interview – Lynn Allen – part 2
IPoC interview – Lynn Allen – part 3

IPoC interview – David Kingsley – part 3

Welcome to the second in this series of interviews of Interesting People of CAD (IPoC).

David Kingsley has had a long and interesting career, was present in the early days of CAD adoption, and served as an AUGI board member for years. Here is the third and final part of David’s interview. This was the most interesting part of the interview for me, but unfortunately much of the more hilarious anecdotes and other discussions were off the record so I can’t share them. I hope you enjoy what’s left!

Steve: What are you most proud of achieving with AUGI?

David: I have to say AUGIWorld magazine and the website. That’s where the group really took off and looked professional.

Steve: If you could go back in time, what would you do differently with the benefit of hindsight?

David: As you get older you learn a few things. I’d probably be a bit more diplomatic about the changes that they went through, and try to resolve things in another way. I don’t know that it would have done much good. I got pretty arrogant about their turnover. I tried to stick to the facts without getting personal; I would always try to do that. I would try to convey factual information but I went a little over the edge with the campaign against what they were trying to do.

I really have no regrets about anything to do with getting the magazine and website started, and how we set up that agreement with SolidVapor. I think that really put a professional face on AUGI at that point.

Steve: What value do you think Autodesk has received from AUGI? Is it a marketing tool…?

David: Yes and no. Having worked directly with the engineering people, I felt they genuinely wanted to know what the users wanted, at least at that point in time. They used us as a filter, so to speak. We were out there gathering information and we were supposed to put it into a filtered and cohesive form for them to use. That’s what I remember as the mission of the group, which is to be the mouthpiece of the user community to Autodesk.

[Some discussion on Robert Green’s AUGI involvement]

I message with Robert often on Facebook and he’s been to visit my house.

Steve: I finally got to meet Robert after all these years, about six months ago in Paris when we both got invited to the Bricsys Conference. It means I’ve finally got to meet some people I haven’t managed to meet on my travels in the past.

[Some discussion about user group names]

David: The original name of the group was NAAUG (North American AutoCAD User Group) and we switched over to AUGI when we went international. Looking for the new name, we came up with a number of variations and one of them I remember was DAUGP (pronounced Dog Pee)!

Steve: [Spits coffee] That’s a good one!

David: I didn’t think that was a good one.

[Some discussion of user groups in general, Bricsys and BricsCAD]

David: I always like to stay on top of these things, you know? I read Ralph Grabowski’s newsletter all the time and he’s been talking about it [BricsCAD] a lot lately.

[Some discussion of the then-forthcoming bundling of AutoCAD and most verticals and Autodesk’s move to subscription only]

David: I know they’re trying to emulate Adobe’s subscription model. It’s going to be painful for a while but I think they’ll eventually get there. It’s just got to be affordable. But you know, people scream about the price and when I looked into it the cost was about $1.00 to $1.50 an hour based on 2000 hours a year. If you can’t afford $1.50 or $2.00 an hour overhead, you’re in the wrong business!

Steve: Yeah, but every business likes to reduce its overheads and doesn’t like to pay extra overheads. Autodesk is doing what it can to reduce its costs; it’s just sliced its workforce by about 23% in two stages. Nobody likes paying more money than they have to.

[More discussion about perpetual licenses, subscription, maintenance and ADN]

Steve: Do you have any fun stories to tell about your AUGI days?

David: I remember checking in to the MGM Grand for AU and being there for nine days, never even leaving the hotel. We would go in and start setting up AU and we would man the booth and teach classes and then break it down and do a debriefing. I remember one time all of us in a conference room and we all just fell asleep. We folded our arms on the desk, put our heads down, a couple of people got tired and a couple of people kept talking, a couple of people dozed off and sooner or later it was everybody. We were all just flat exhausted. We all woke up and said, “What are we doing here?”

I lived in Denver for many years, a ten hour drive to Las Vegas. It was worth taking the car for a nine-day stay. I think I did that 5 or 6 years running. I remember a few of us had to find a laundromat midweek, and I was the only one with a car. One year I arrived at the MGM about seven one night after this long drive, and it was just jammed to the hilt. I couldn’t even get off the street. I had a lot of stuff and decided to get a valet, because Autodesk would expense stuff like that for us, but I couldn’t get one. It took me an hour to check in. Turned out the Rolling Stones were playing the MGM Grand that night! I was there about two hours before show time.

On the way to my room there were people walking around the arena trying to sell tickets for $350 a seat! I like the Stones but I wasn’t ready to pay that and I’m sure my wife wouldn’t have been happy either.

Another time, I went to a hospitality party with the executives. The suite there had all this dark wood and it looked like a cabin in the Rocky Mountains somewhere, up on the 15th floor of the MGM Grand. All sorts of hors d’oeuvre and wine, I’m sure they paid a bundle for that!

Steve: Yeah, the parties were always fun.

I have a falling asleep story too. I was at AU 2006. I was with Owen Wengerd and we were hanging out at a bar until 1 AM and we were just about to head off to bed when we saw Tony Peach walk past. He was a great guy, passed on a few years ago, but Owen and I both knew him from earlier times. We ended up at a bar talking and it was about 4 AM before we called it a night. The next morning I had a class, I was hoping to learn .NET programming for AutoCAD. I got there and sat down and my eyes glazed over and it was the old dropping off and neck-jerking wake-up thing. That’s the reason I never became a .NET programmer in AutoCAD! I just slept through the class. It was too hard. I gave up.

[We swap a bunch of really funny off-the-record stories – I wish I could share them!]

David: [About Lynn Allen] How can you axe a person like that? She’s kind of the face of the corporation.

Steve: Yup. I don’t understand it. Maybe it’s personal.

David: Yeah. Also there was this thing about age discrimination. A lot of the older folks are wondering whether this had something to do with age. Who knows? Inevitably as you’ve been there a long time your salary climbs and you get expensive after a while, but they probably generate a lot more revenue than they cost.

Steve: I’m sure Lynn generated a lot more revenue than she cost.

David: Yeah. I can imagine next year when some guy in a suit shows up, they’re not going to be happy!

Steve: Well, she’s a drawcard, that’s for sure. And I guess she’s likely to be somebody else’s drawcard soon.

David: That’s true. I understand she’s got offers or at least approaches from all the competitors. Solidworks in particular.

Steve: I wonder if she comes as a package with Heidi Hewett? I understand Heidi wrote a lot of the material.

[Note: this interview took place before Heidi’s move to Bricsys]

David: Yeah, That would be a real coup. Hiedi was her cohort there. I remember watching Heidi teach a class and the software was acting up. I blurted out that a number of mathematicians throughout history have had numbers associated with them like Avagadro, Reynolds and so on. I want to create a Kingsley Factor, as follows: “The efficiency of a piece of software is inversely proportional to the number of eyes looking at the screen.” It always screws up when 50 people are looking at it.

Steve: The curve will show a dip at two people observing, based on my experience in support. I would get a call out about a certain problem and the two words that were guaranteed to fix it were “Show me.”

David: Heidi and her husband Nate lived close to us. We would catch up with them at the local pub from time to time.

Steve: I remember Nate got the shaft [from Autodesk] in about 2009 in an earlier “culling of the unwanted”.

David: Earlier than that, there was another big reduction-in-force and we were there [at Autodesk] and we knew it was going to happen.

Immediately after our board meeting, we left San Rafael and relocated in San Francisco for AU. As I recall that was the year of four AUs. One young Autodesk employee was with us and said, “Well, I got laid off. But! I have a job to finish off through Autodesk University and they didn’t take away my American Express card. So we’re gonna party this week!”

IPoC interview – David Kingsley – part 1
IPoC interview – David Kingsley – part 2

IPoC interview – David Kingsley – part 2

Welcome to the second in this series of interviews of Interesting People of CAD (IPoC).

David Kingsley has had a long and interesting career, was present in the early days of CAD adoption, and served as an AUGI board member for years. Here is the second part of David’s interview which covers his involvement in AUGI, the controversy over how it was managed, and how that ended his involvement.

Steve: What was your first involvement with AUGI or NAAUG? At what stage did you get involved?

David: I think it was NAAUG in Philadelphia. Paul Jackson came up to me and said, “We would like you to get involved with the board. He asked me to attend the board meeting right there. So I started hanging out. That may have been the first time I met Lynn Allen. David Harrington was there, Dave Espinosa-Aguilar, Donnia Tabor-Hanson… that was kind of the formation of a very early AUGI Board. They had a board, but they were looking for different people.

I first ran for the AUGI board and was elected in 1996. I was on the Board from 1996 to 2002. We didn’t have a web site in 96, not many small organizations did yet, so I was involved in the first AUGI website ever. It was pretty crude! I remember we just kind of talked about it, Carol Bartz waved her hands, and we had money! She would sit in for a couple of hours every time we met in San Rafael. We would spend three or four days at Autodesk and that’s when we would develop our annual plan and funding requirements.

They were throwing a lot of money at us – $150,000, $200,000 a year just to support the user community. So we had a pretty healthy budget. A lot of people bungled it though. I remember one year we had budgeted $80,000 for something. It was what became the Exchange, where everybody traded their apps. We were supposed to develop that and we completely failed. We directly experienced the wrath of Carol Bartz for that.

The AUGI Board was a really difficult thing to make work because everyone was a volunteer, and they were all over the country, and there were no consequences for failure. People would sometimes just blow stuff off and wouldn’t do things. We were unable to accomplish things. They lacked the skills, or desire, or didn’t have the time, so there were some really rough years there where we were supposed to get things done and we didn’t. We had a couple people who openly stated they were just there to get NFR software.

That was when Rich Uphus and SolidVapor became involved. I believe Carol Bartz set us up with them to give us some kind of essential management. That was when AUGIWorld magazine came out. When we got involved with them, Uphus rebranded his “A” magazine as AUGIWorld and started to plan all of the CAD Camps. At that point, Autodesk ceased funding AUGI directly.

Steve: Is this the quarterly CAD Camps?

David: Yes, but I think there were 40 of them one year. Yoshi Honda and I were kind of the key AUGI people who negotiated that with Rich Uphus. We did most of the conceptual development and business arrangement between AUGI and Uphus. SV put together the first workable AUGI website with our input. All of that happened because of SolidVapor.

The plan was that AUGI provided the technical content and SV built and maintained the infrastructure – the website, the magazine, the organization behind the CAD Camps. When you start to think about the expense of that – If you went up to some hotel and said, “I’d like to have five breakout rooms, I’d like to serve lunch to 200 people, for a day and a half,” they would say, “Well, put down $200,000 and we’ll reserve a spot for you.”

For one or more years, CAD Camps had more attendees per year than Autodesk University. So SolidVapor had to come up with a lot of capital – millions of dollars. SV was going through $2.5 to $3 million a year. I’m sure they were making a profit; that’s what businesses are about. But they were pretty much backed by Autodesk.

AUGI generated no revenue at all. They were actually an expense. Autodesk flew us out to San Rafael for a week twice a year and we just partied! They took us out to nice restaurants. But we also provided a lot of good information from the user community, so we were the mouthpiece of the user community to Autodesk.

Later on there was a faction within the AUGI board that didn’t like the arrangement that we had with SolidVapor. They felt that AUGI was no longer in control – that SolidVapor was doing all the stuff that AUGI should be doing. There was a real split. My position was that it became that way because the model we had earlier didn’t work. Autodesk was giving us money and we were failing, so they put a real organization, an experienced business, in place to accomplish what they wanted. We were in a position where we drove that organization but we didn’t manage the money, we didn’t really manage the projects.

AUGI chose to terminate the contract with SolidVapor. Some may say otherwise, but the fact is they offered SV a deal they could not accept. I tried and tried to make sense with them, tried to tell them early on that… first of all, where is your money going to come from? Autodesk has told us they will not fund AUGI like they did before, they will only be another ad buying customer. All of this cash flow is going to go away when you end this relationship. Don’t tell me that you’re going to come up with $2.5 to $3 million a year, it’s just not going to happen. You guys don’t know how to do it, you’re working full time jobs, and you’re already unable to fulfill many of your responsibilities to AUGI. You expect to, all of a sudden, on a part-time basis, raise $2.5 to $3 million a year and put together a dozen CAD Camps, publish a magazine and keep a website running. It’s just isn’t going to happen.

But they went ahead and did it anyways. That’s when I left AUGI. I didn’t want to be involved with what was going to happen. I don’t have any personal grudges against people but there were a couple of people I really bumped heads with. Let’s just say we didn’t talk to one another after that.

I remember going to Autodesk University after they had terminated the relationship with SolidVapor and I knew they were in serious financial trouble. They had relatively no financial backing or sales, they had no viable plan. That’s when CAD Camps ended, AUGI World magazine ended, and the website stumbled really badly for a couple of years. It was in pretty bad shape. AUGI has pretty much gotten themselves back on track now, but at a much smaller scale than it could have been.

Steve: Wasn’t there some legal wrangle over who had rights to the forums and the contents?

David: Yeah. AUGI didn’t have any direct revenue. They had not invested anything. SolidVapor managed all the money, and the agreement was that SolidVapor would provide the infrastructure. So SV built the website, invested all the time, they were paying for the servers, paying the programmers, all that stuff. I tried to tell the AUGI board that they had no power whatsoever. Sorry, but power is money. You don’t control any money. You haven’t invested in this so you really don’t have a right to it. You provided the content for the forums, yes. The position of SolidVapor was, if you sue us for the forums and win, you’ll take responsibility for the whole thing. You’ll be totally responsible for funding and operating the website, the servers, the programmers.

AUGI was never restricted about what we could publish or what we could do, other than technical limitations. They would do pretty much whatever we wanted to, within reason. But we never paid for anything so we never had any power there.

I was pretty much against the whole AUGI position at that point, I thought they were unrealistic. They all had full time jobs, some of them were highly placed in engineering departments, but no one really had any business experience.

A lot of the things they wanted to do were just not practical or cost-effective. So we had some real head-butting with SolidVapor about what AUGI wanted to do. SV said, “We can’t do that, we can’t afford it,” or “Come up with a budget for it.” AUGI was just kind of waving their hands around and asking for things and they didn’t think about how much it was going to cost or how it was going to get paid for.

So they struggled for a while. I’ve been out of touch – I’ve really not been involved with AUGI since 2008 when they terminated the SV relationship. That’s when I said adios.

Steve: I still have the document that you produced with all your record of that I can now refer to. It’s still on my blog!

David: Oh really? I think it would pretty much corroborate what I just said.

Steve: If you remember, you published that on the AUGI forums and that was removed and so I published it on my blog for people that wanted to read what you had to say. I don’t know if you remember that or not but it’s still there!

David: Yeah, yeah!

Steve: I just downloaded it for my own blog to read it!

David: I think there are a few people who can remember those days. I had very few supporters. I actually got some hate mail. I was amazed at the lack of understanding in the community at what was going on. Nobody got it. I had a few communications with people shortly afterward but not many. It was surprising.

AUGI survived, it just went to a much smaller scale. You’re probably pretty familiar with that whole scenario then?

Steve: Yeah, I came on it fairly late and I didn’t really understand what was going on either, except that there was there was a bit of a constitutional crisis with the board and who was supposed to be on the board, and who gets to say who’s on the board. There was an election and the election was cancelled or postponed or moved and people weren’t allowed to put themselves up for election and all sorts of stuff happened.

David: Yeah. I kind of went over the edge a little bit with some stuff at that point. I did have a really serious discussion with the board, because I’d been off the board for a number of years and I decided to go back and put myself up as a candidate. They wouldn’t even allow me to run as a candidate. It might have been ’08 or ’09. I said I’d like to run and they said no. That didn’t really get any press. That was kind of a private thing between me and…

Mark Kiker and Richard Binning were the two people I really butted heads with. They were the two that really spearheaded this transition, so they told me flat out, you’re not running. You’re not going to get on the board. That was where the noise about who gets to be on the board came from. They were pretty dictatorial. It was pretty interesting to watch.

Steve: Within AUGI, when you were actively involved in it, who are you dealing with at Autodesk? I know you mentioned Carol came to the meetings. Were there other people that you were interacting with?

David: We dealt directly with a lot of the engineering department there. I dealt with Buzz Kross a lot. During the weeks that we spent at Autodesk, we would work directly with the engineering people. It was timed such that they could talk to us directly about what was coming up and we were tasked with thinking about how to introduce that to the user community. We were tasked to provide feedback to them, that’s where the wish list originated. We were tasked to become the mouthpiece of the user community.

Carl Bass was still in engineering management, so we dealt with him a lot. Then there was Lynn. We worked with her a lot. Lynn was the one who worked the internal politics and made things happen for us. We gave her the official title of “AUGI Sweetheart”.

I just thought about this a couple of days ago. I lived in Denver, very close to Columbine High School where there was that big mass shooting where two kids shot up the High School and killed 19 people. A couple of kids on my street went to that school, but we didn’t have any children there. I remember sitting down in Carol Bartz’ office; I’d asked for a private meeting with her. I talked to her about the effects of violent video games and what influence Autodesk might have on that. We actually came to know one another at a more personal level at that point. It was an interesting relationship after that.

We used to sit down with all of the top management people. There would be a formal meeting every time the AUGI board met. All of the big kids would show up and all of the AUGI kids were round the other side of the table. We’d sit there for two, three or four hours and have a really nice long discussion about the product and the future. They’d tell us about future developments, what was coming up and we all had NDAs so we couldn’t talk about anything outside.

IPoC interview – David Kingsley – part 1
IPoC interview – David Kingsley – part 3

IPoC interview – David Kingsley – part 1

Welcome to the second in this series of interviews of Interesting People of CAD (IPoC).

David Kingsley has had a long and interesting career, was present in the early days of CAD adoption, and served as an AUGI board member for years. Here is the first part of David’s interview, which covers his career.

It’s a long career, so this is a loooong post! Strap in tight for a candid discussion of solar plants, a couple of US Presidents, primeval Autodesk University, Autodesk before and after Lynn Allen, a personal opinion of the current CEO, sailing on an America’s Cup yacht, the Hubble telescope and an inappropriate discussion of hard nipples.

Steve: You’re retired now, right?

David: I’m 67 soon and pretty much retired, but I’m still keeping up with AutoCAD and Inventor, my two primary things. I use Inventor pretty regularly. We’re going to build an addition on the house and I’m still up to speed on it. I’ve been on ADN (Autodesk Developer Network) for years and years; I’m still doing that. But yeah, I’m retired. I say I’ve become unemployable!

Steve: Can you give me a brief outline of the main things you’ve done during your long career?

David: I started out on a drafting board in 1970 and had 10 or 11 years of experience with that. I grew up West of Detroit; the whole southern part of Michigan is automotive industry. You know, Detroit iron. I worked a lot in automotive tooling, all on paper and pencil.

Then in ’78 I moved from Detroit to Denver, Colorado and was there for 40 years until just last month. In 1976, then-President Carter commissioned a Solar Energy Research Institute and I went around and visited all of the candidate cities for this new Institute and it ended up in Denver. I had visited and interviewed with the company there, and this was even before the Institute had been officially commissioned and opened. So this company called me back and moved me all the way across the country and I went to work for them. They built equipment, so the Institute is like a think-tank and they contracted out to manufacturers around the area. We built a lot of hardware. So I was building solar energy R&D stuff back in 1980/81.

Then Regan got elected and he was anti-solar and he cut all of those programs so I ended up being out of a job after a couple of years. So I ended up in aerospace. There were two or three big aerospace companies in Denver. Long story short, I ended up working on the Hubble telescope. That was still working on paper and pencil!

In ’81 we got CAD training, they brought in a big CAD system. I got pretty adept at that. It was about ’84 or ’85, AutoCAD started to pop up and PCs were just starting to appear. Literally showing up on people’s desks. I immediately took off on that; I could see that was where everything was headed.

I hooked up with my first Autodesk University in, was it 92? One of the really very first AUs, and I remember it was in the parking lot, there on McInnis Street. They had a little tent; there were only a couple of hundred people there.

Steve: Sorry David, which city was this?

David: This is in San Rafael, right at the Autodesk headquarters, there on McInnis Street [Parkway]. Ever been out there?

Steve: Yes.

David: And everybody stays at that Embassy…?

Steve: Embassy Suites, yes. Good breakfasts!

David: Yes, and this was in that parking lot. They had a tent and grilled hamburgers and hot dogs and ten classes. I don’t think Lynn Allen worked there yet. I can’t remember her being there.

Steve: Wow!

David: I remember Autodesk before Lynn Allen! Now we’re in a world with an Autodesk without Lynn Allen.

Steve: Yes, it’s bizarre, isn’t it?

David: Yes. It’s like the company’s got a whole different… have you spoken with Lynn? Chatted with Lynn about any of this?

Steve: I’ve been in touch. I haven’t spoken to her personally but we’ve sent messages back and forth.

David: It’s pretty ugly. There are a bunch of people who are pretty pissed off. This Anagnost, the new CEO, a lot of people think there’s a vendetta going on. There’s a lot of people he… I don’t know if you know anything about this Anagnost or have met him before, but I worked with him over the years. He was an OK guy but he was just a real cold… you know, I don’t know how to describe him. But a lot of people think there was a lot of animosity, that he’s kind of venting, getting rid of people he didn’t like. Because he came up through the ranks, he’s been there many years.

So anyway, back about me!

Steve: So you went to the first AU at San Rafael?

David: The very first or one of the first. I also remember going to the one in San Francisco, and Phil Kreiker was the President. I remember him making a bunch of rude remarks: an inappropriate monologue! I guess you had to be there. It was the kind of stuff you wouldn’t have expected to hear from somebody…

Steve: I may have actually been there. I went to the ‘95 one in San Francisco at the Moscone Center.

David: I remember one being at the Bill Graham Center. The one where he said he was so excited his nipples were hard! I always remember that.
Was that the one where they brought him in, in a straitjacket?

Steve: Ah, great. No, I didn’t see that, that sounds fun!

David: So you’ve been around this stuff for a long time too?

Steve: Yeah, Version 1.4 was my first AutoCAD. I worked for an AutoCAD dealer, the first AutoCAD dealer, here in Western Australia as the demo jock and sales support and specialist and so on. Yeah, that was ’85.

David: I bought AutoCAD 11. I’d been working on a big mainframe system. Computervision was the big player at the beginning, and they had a model space/paper space paradigm and that was the first thing I worked on in 3D, and it was model space/paper space and AutoCAD was just a flat 2D tool. When they came out with 11, that was when they first came out with paper space. That was a paradigm I was comfortable with, so I ended up buying 11 and left my cushy aerospace job.

I had been there ten years and I had the same job the day I left as the day I got there. It was a big company and it was really difficult to move forward. At that time the IT guys were managing the CAD system. Because it was a computer, you know? And they weren’t figuring out that a CAD Manager and an IT Manager were not the same thing. There were no CAD Managers, they didn’t understand the whole business yet.

So I proposed that I become the first CAD Manager in the place because I saw the job and everybody else kind of saw it, too. So I had to politic for that job for about three years. We were really struggling, we had these IT guys who didn’t know… they just couldn’t support us. We were just floating around, trying to figure out our methods and operations and the IT guys weren’t any help at all.

So finally after three years, my boss got a promotion and I got a new boss and he immediately said, “I know what you’re talking about and I’m going to go to Human Resources and fight for this position.” So they posted it, interviewed three people and gave the job to somebody else!

So I just threw up my hands, went and bought AutoCAD 11 and struck out on my own. We had some guys who spun off from the company earlier and one of them at the time was… the company I worked for, their speciality was optical sensing. They built a lot of Earth observation satellites. They built (and still) some of the most advanced satellite on the planet. As a matter of fact, right now every instrument on the Hubble telescope was built by this company. So the last four or five contracts they have won every contract to replace every instrument. Ball Aerospace.

Anyway, a couple of people had spun off that company and I went to work for them. Half a dozen consultants, you know, a small company. This one guy won a contract with the Italian America’s Cup sailing team. His specialty was wind shear detection. He developed a system where the vector and velocity of the wind could be mapped up to 2 km ahead of the craft, and he sold it to the Italians. We were trying to build this thing and put it on the Italian boat. This was in San Diego in ’92 or ’93.

Shortly before the race, the sanctioning body ruled it out. We spent all this money and they said, “Nah, you can’t do that.” Apparently the rule was, you couldn’t communicate with the boat. So they couldn’t communicate ship to shore. What I remember is that we were gathering our own data autonomously. But they said, “Nah, you still have such an advantage.” I actually got on the boat for a short time. I learned very quickly that if you’re not part of the racing team you’re just in the way. There’s no place for you to be.

So after that I ended up hooking up with the dealer network in Denver, the Rocky Mountain region. This is in the 90s. I would go around and do training with the dealer network. On several occasions I would go in on a long term contract. They would have a big sale, a big installation of a dozen or so seats, and I would go in and be an employee on a contract basis. I would go in and be there like everybody else for three or four months. I’d get them up to speed.

That was always bizarre. There would be a political nightmare. There would be people who didn’t want to be on CAD, or didn’t like this software, they would rather have SolidWorks or something else, and they fought tooth and nail, and it was crazy. There were people who really didn’t like me, just because I represented, I was trying to teach them this software. I told them, “This is not about me! Your management made this decision. If you want to work here you’re going to have to live with it! I’m not the cause of your problems.”

That’s pretty much how I ended my career. I just got tired of that, I didn’t need to work any more and my wife’s career bloomed later in her life, about 45 or 50 and she had a great career from 45 on, so for about 20 years she was really the breadwinner, so I was really the playboy.

Steve: You were a “kept man”!

David: Yeah, I really said that. But I was still working.

I had a couple of really bad experiences at the end. Just a bad employer. We had a solar company that established their North American engineering center in Denver. They built the world’s biggest solar power plant in Arizona. A Spanish company with a North American engineering office. They built several really big solar power plants, but that was a really horrible place to work. We were micromanaged from Spain and they had some of the worst CAD implementations I’ve ever seen. I tried to turn them around, and it was just unbelievable what they were doing. You’re familiar with the technology. Are you civil, or electrical, or…

Steve: Mostly mechanical. I have worked for an architect but my background is in mechanical engineering. I actually started my career at a drop forging company that made a lot of automotive parts, so fairly similar to your start.

David: In my really early days, I worked in a General Motors plant. It had been a bomber plant during World War II, making bomber aircraft. Right underneath my office was a drop forge. It just sat there all day, just WHAM! WHAM! WHAM! My cup of coffee was always wiggling! It was never still, it always had a wave in it.

Back to this company, they were managing Inventor files like AutoCAD files, with the revision letter changing the file name. That broke the assembly in Inventor, but they couldn’t get that concept. There was this confrontation thing and they quietly walked me out the door. They gave me a really nice letter that basically said, “Just go away.”

I said, “I really don’t want to do this any more” so I stopped working. That was about 2011.

There was one more job I had after that. I worked in a company that was using Inventor and made ambulance helicopters. They would take a standard helicopter, fully fitted, with every component certified, and tear it apart, strip it out. We would build new panels and fit all this medical equipment. That was probably the best paying job I ever had! But that’s when I got tired of it. That was a young man’s job and I was 62 or 63. They wanted me to work 60, 70, 80 hours a week and I just couldn’t do it.

So I gave it up!

IPoC interview – David Kingsley – part 2
IPoC interview – David Kingsley – part 3

IPoC interview – Heidi Hewett – part 3

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

First up, Heidi Hewett. Heidi has a long CAD history and is well known for being outstandingly good at her job. She made big news recently by shifting camps from Autodesk to Bricsys. Here is the third and final part of Heidi’s interview.

Steve: Did you go to Gent? What were your impressions of the people at Bricsys?

Heidi: Yes. After my initial discussion with Don Strimbu, he invited me to Gent to visit Bricsys headquarters and meet the team. While I wasn’t yet ready to give up my newly earned real estate license, who can turn down a trip to Europe? Don met me at Heathrow airport and accompanied me to Gent from there.

As soon as we arrived at the office, Don introduced me to Erik, Bricsys CEO, and other executive staff including Patrick, Mark, and Sander. I went into the office with Don every day that week as he arranged for me to meet and get product demonstrations from people across the organization. They were all incredibly welcoming and treated me as if I was already part of their team.

Several things about the office environment got my attention. The first was that nearly all the conference rooms were empty. And it was very quiet. People were sitting at their computers working, not sitting in meetings! They’re a team of dedicated people that know what they need to do and how to get it done. But they also know how to have fun.

A chiming sound ringing through the quiet office indicates an important event. One afternoon it signalled everyone to meet in the kitchen for Portuguese wine and cheese tasting hosted by Carlos, who was visiting from his office in Portugal. Each Friday at lunch the chime reminds everyone to head to Pinocchio’s for weekly pizza and wine. And I heard rumor that company hardware policy enables employees to keep their old computers when it’s time to upgrade. In exchange, the employee leaves a few bottles of wine in the community kitchen, which, coincidentally is right next to the rec room with ping pong table.

Steve: How about Gent itself?

Heidi: When I wasn’t in the office, I was exploring Gent and nearby Bruges, with my gracious hosts from Bricsys. It’s a beautiful city with so much to see. I look forward to the opportunity to return!

Steve: How have your former colleagues reacted to your move? Have they been supportive? How about the reaction form the CAD community in general?

When I decided to join Bricsys after all my years of working on and promoting AutoCAD, I was a little concerned about the reaction I’d get from the AutoCAD community, whether internal or external to Autodesk. But my concerns were unfounded. Immediately following the announcement that I joined Bricsys and for at least a week following it, I was bombarded with responses through social media and direct messaging. Names were scrolling by so fast that I couldn’t keep up. Former colleagues and customers that I haven’t talked to in decades as well as those I worked with just a few months ago. Many names I’ve never seen but suspect they belong to AutoCAD users somewhere around the world that have attended my presentations or read my posts.

I was truly touched by the kind words of respect for my past achievements and the enthusiastic support for my new endeavors. It made me realize this global CAD community is incredibly small and tight. And, even if we’re developing or using different CAD software, we have the same goal… to design amazing things. I’m proud to be part of it.

Steve: I’m sure you’re deeply immersed in learning everything you can about BricsCAD and related products. What has surprised you most so far about the software?

Heidi: It’s a little surprising how much there is to learn about a product that feels so familiar to me. I’m confident that I can jump in and immediately start using BricsCAD the same way I use AutoCAD. That’s reassuring but it’s not enough. The challenge for me, as it is for most CAD users, is to push beyond the old and familiar ways of doing things to take advantage of the software’s most powerful functionality. What I found most surprising about BricsCAD, is that it allows me to create 3D solid models in a way that’s intuitive and familiar yet with more intelligence than I thought possible in a DWG-based drawing.

Steve: What are you most looking forward to in your new role?

Heidi: When I met with Erik and team at the end of my week in Gent, he asked if/how I wanted to work with Bricsys. He knew that my career had been headed in a different direction, away from CAD, so he left it up to me to decide if I wanted to work part-time, full-time, consulting, whatever. After what I’d seen and experienced at Bricsys, I knew I couldn’t be any less than fully committed! There’s just too much to show and talk about and demo and teach.

I can’t come up with a single thing that I’m most looking forward to. That’s what attracted me to this role. What I’m most looking forward to are the Endless Possibilities.

IPoC interview – Heidi Hewett – part 1
IPoC interview – Heidi Hewett – part 2

IPoC interview – Heidi Hewett – part 2

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

First up, Heidi Hewett. Heidi has a long CAD history and is well known for being outstandingly good at her job. She made big news recently by shifting camps from Autodesk to Bricsys. Here is the second part of Heidi’s interview.

Steve: Did you have much involvement with AUGI?

Heidi: I haven’t had a lot of involvement with AUGI aside from presenting at CAD Camps they hosted almost a decade ago. I thought they were great events and was sorry to see them fade away.

Steve: What do you think the benefits have been for Autodesk in helping to support AUGI over the years?

Heidi: While I haven’t had a lot of experience working with AUGI, I think any opportunity a company has to get closer to their customers is worth pursuing.

Steve: How much presenting did you do at events like AU and others? Did you enjoy that?

Heidi: During the first half of my career at Autodesk I did a lot presenting at AU, CAD Camps and many other events. My kids were young then. As they got older, I didn’t want to miss all the big things in their lives. So, while I was always willing to travel to events, I didn’t seek them out. Instead, I did more webcasts and limited most of my travel to train-the-trainer events. I especially enjoyed the train-the-trainer events because I felt like I was sharing my knowledge globally without spending all my time on airplanes. Instead, I traveled to a few Autodesk sites in Europe or Asia to train a group of employees and partners from various countries in that region. Then, they would take what they learned, and the materials I provided, back to their countries where they could present it to customers in their local languages.

Steve: You and Lynn Allen worked closely together for many years, right?

Heidi: Yes, I met Lynn soon after she started at Autodesk. She was in the Training department and I wanted to join their team. That’s where we first worked together and became friends almost a quarter of a century ago. I think she’ll back me up when I say we were both 5 years old at the time!

Since then our paths have crossed many times. Each year when I was ready to present the newest AutoCAD functionality, first to employees, I reached out to Lynn so that I could schedule my training session around her busy travel schedule. And, as she was traveling the world, receiving more presentation requests than she could schedule, she referred the AutoCAD ones she couldn’t cover to me. On more than one occasion I’d be at some international event and a customer would bring Lynn’s Tips and Tricks book to me for an autograph, thinking I was her. Or they’d insist that they met me at that same event several years before even though I’d never been there before. Being mistaken as Lynn Allen is certainly flattering!

Steve: It’s kind of bizarre that such a successful team was thought to be no longer required. Do you have any idea what was behind that?

Heidi: I don’t have any insight on the thinking behind it. But, I try to believe things happen for a reason. I wasn’t sure what that reason was, until now… and I’m thrilled!

Steve: You’ve now joined Autodesk competitor Bricsys, which is something of a coup for them. Who contacted you initially? Was it Erik [De Keyser, Bricsys CEO]?

Heidi: Ironically, the first contact I had about Bricsys was from Lynn Allen. Not because she was working for them. But because Vince Aman (formerly from Autodesk, now working for Bricsys) had been trying to reach me through LinkedIn. I was attending a real estate class at the time, in preparation for what I thought was my next career. I received a text from Lynn telling me to check my LinkedIn messages. After speaking to Vince, briefly, I reached out to Don Strimbu, VP of Communications at Bricsys. I’ve known Don since my first years at Autodesk and wanted to hear about his experience at Bricsys.

IPoC interview – Heidi Hewett – part 1
IPoC interview – Heidi Hewett – part 3

IPoC interview – Heidi Hewett – part 1

Welcome to the first in this new series of interviews of Interesting People of CAD (IPoC).

First up, Heidi Hewett. Heidi has a long CAD history and is well known for being outstandingly good at her job. She made big news recently by shifting camps from Autodesk to Bricsys. Here is the first part of Heidi’s interview.

Steve: You’ve been doing this a long time, but was there a pre-CAD part of your career? What did you do before Autodesk?

Heidi: I didn’t have much of a pre-CAD career. I started college at Colorado State University as a Computer Science major. One day I stopped by the Industrial Design lab to meet one of my friends. He was taking a drafting class and had just been introduced to AutoCAD. He wanted me to see it. Using a stylus, he drew an ellipse on the tablet (not today’s kind of tablet, of course). The ellipse appeared in green on the monochrome monitor… like magic! That’s all it took. I was hooked! I realized I didn’t want to program computers, I wanted to draw with them. So, I checked around to see what majors would best let me combine my interest in math with my interest in AutoCAD. The next semester I transferred to the University of Colorado for Architectural Engineering.

After graduating, I moved from Colorado to California to take an engineering position with an MEP firm in San Francisco. They worked exclusively on drafting boards and I soon realized that what I enjoyed most about my engineering education wasn’t engineering, it was using AutoCAD! Within the first year I managed to convince my boss that we needed AutoCAD (I was a horrible manual drafter)! While working with a local reseller to set up our new CAD lab, I learned that the company that makes AutoCAD was located right across the Golden Gate Bridge, in Sausalito. Less than a year later, I was walking down the hall at Marinship Way, passing people like John Walker and Amar Hanspal (my hiring manager). I was in awe that I actually worked there.

Steve: You were with Autodesk for 26 years, right? Were you a Technical Marketing Manager all that time, or did you start at Autodesk with something else?

Heidi: I started in Product Support, as a support technician answering calls from resellers. It wasn’t a good fit for me. Nobody ever calls product support (at any company) to talk about how much they love their product. They only call when there’s a problem and they need help. And, most of the questions weren’t about how to use the software. They were about how to configure plotters and digitizers. I loved AutoCAD and wanted to share my knowledge about how cool it was. So, aside from my first few years in Product Support, my career at Autodesk was focused on educating users on what they could do with AutoCAD. My titles included Illustrator (back when we had printed manuals), Training Specialist, Marketing Support Engineer, Senior Applications Engineer, and Technical Marketing Manager.

Steve: What did a Technical Marketing Manager do, exactly?

Heidi: It’s kind of funny, Technical Marketing Manager was my title for more than half my career, but it was probably the least descriptive of what I did. I was technical and worked under the Marketing organization. But I did the same thing in that role that I did in all my previous roles aside from Product Support. I was a Learner and a Trainer. I worked with the AutoCAD development team to learn what was coming in the next release of AutoCAD. Then I created documents and videos such as the Preview Guides and Launch Demo Videos to help educate Autodesk employees, partners, and customers on the new functionality. Regardless of my official title, it was the perfect job for me because I got show people how cool the software was.

Steve: What did you enjoy most about that job?

Heidi: There were many things I enjoyed about the job so it’s hard to narrow down. I enjoyed working directly with the development team to be one of the first people on the planet to understand and use the newest AutoCAD functionality. And I enjoyed travelling around the world to share what I learned with our partners and customers.

Steve: I’ve noticed that your written materials always show a very high standard of clarity and correctness. What would you put that down to?

Heidi: That’s quite a compliment and I appreciate the acknowledgement.

I graduated from college without having taken a single English class. Back then it wasn’t required for Engineering majors and I was thrilled because I hated to write. As I got further into my career, I realized how crucial writing skills were, even for a math-minded person. That was around the same time I realized my true passions were around training and education. So, after a little research I found two relevant graduate programs at the University of Colorado, Denver. One was a Master in Technical Communication (so I could finally learn to write) and the other was a Master in Information and Learning Technologies. I couldn’t decide between them, so I did both! Having two young children and a full-time job with a lot of travel, it took me almost 7 years to graduate but it was worth it! The technical communication skills that I learned gave me the confidence to write publicly and I launched my original AutoCAD Insider blog, as one of my class assignments.

Steve: Would you say you’re obsessive about the quality of what you put out?

Heidi: Yes, I’m definitely obsessive about what I produce. There are many times I wish I wasn’t because it can be time-consuming. But, if I make a statement (written or oral) I want to know that what I’m saying is accurate to the absolute best of my ability. A perfect example is one of my first blog posts for Bricsys. It started as a quick and simple post about installing the trial version. How complicated could that be, right? But for me it’s not just writing about what I see, it’s understanding it. Writing that simple little blog post produced a string of emails between myself and the BricsCAD development team. Most of the information I learned didn’t make it into the blog post but it helped me fully understand and believe what I was writing.

The greatest value I get from writing is learning. If I want to learn something, I write about it. Because, until I can clearly explain it to someone else, I probably don’t really understand it myself. My first and best experience with the value of writing was when I wrote about sheet sets for AutoCAD. It was such a new, big, and overwhelming topic that I just couldn’t grasp it. Not after discussing with members of the development team and not after trying it for myself. The only way I could fully understand and communicate sheet set functionality was to write about it step-by-step. And so, Sheets Happened!

IPoC interview – Heidi Hewett – part 2
IPoC interview – Heidi Hewett – part 3

Interesting People of CAD interviews (IPoC)

A new series is going to be introduced to this blog very soon: Interesting People of CAD, or IPoC for short. I have interviewed two very interesting people already, with another big name in the pipeline and more to come later.

The first instalment will be published within hours. This person has a long CAD history, is outstandingly good at the job they do and has made big news recently. Want to take a guess who it might be?

If you want to suggest other IPoC to interview, please add your comments to this post. If you think you have an interesting story to tell and want to volunteer to be interviewed, feel free to comment here or contact me privately.

Interviewing the creator of BLADE – CAD’s best LISP IDE – part 2

This post continues my interview with Torsten Moses about BLADE, the new LISP IDE that arrived with BricsCAD V18.2. See here for post 1.

Steve: I’ve noted before that BricsCAD execution of AutoLISP and Visual LISP is several times faster than AutoCAD’s. How does the new technology affect that performance?

Torsten: All the new BLADE-related stuff doesn’t really affect normal LISP execution outside the IDE and debugger. The connection is made by a few callbacks, which take zero time in normal processing. Therefore there is also no chance of breaking things. The BLADE implementation is very safe, and performance remains high for normal usage. For the debugger and the synchronization, it is all home-brewed stuff, optimized for best performance even when debugging, and minimum system and LISP memory usage.

In the course of implementing the debugger and internal versus external synchronization, I also removed most emulations and implemented that as core OpenLisp functionality. That has the side-effect that the (repeat), (foreach) and (vlax-for) functions now run about five times faster at the loop construction. So rather than slowing things down, creating BLADE has actually speeded things up!

Steve: Will the Mac and Linux versions also get this feature?

Torsten: Yes, it is fully compatible. This is due to the implementations of WxWidgets and my own stuff. I have already verified BLADE running under Linux. There are no differences; even the implementation code has no Windows-specific stuff.

Steve: Can you give a simple example of the workflow of a debugging session?

Torsten: First, don’t pre-load any LISP file into BricsCAD. Such code loaded outside the debugger is fully functional, but it can’t be used for debugging. The special connection between internal and external representation is only established when loading the LISP code under a debug state.

Next, in BLADE open an existing FAS or VLX project, and/or a “Named Session”, or simply any LISP file you want to start debugging with.

Now you can select Start Debugging from menu or toolbar, or hit the F8 hotkey. The special Debug Toolbar will appear. You can either activate AutoBreak, which stops at first executable code, or activate the LISP source where you want to start debugging and place some breakpoints.

Then load the dedicated LISP file, either by the normal Load into BricsCAD function, or from the Load button in the Debug Toolbar. Now that loaded code is debug-enabled and you will see the file and debug-enabled functions in the two right tabs.

When the debugger halts at the first breakpoint, all debug-step modes are enabled in the toolbar, and you have all the usual debug step modes. More than in AutoCAD’s VLIDE, actually. You can set the watches (observed and tracked variables) as “Data Break Point” by activating the checkbox. Then, whenever that value changes, the debugger also stops automatically at the related LISP statement.

Steve: What if your code calls code in other files you haven’t loaded?

Torsten: Don’t worry about that. The debugger recognizes this and will ask to load the related LISP file on-demand. In normal LISP, you would get an unknown function error but the debugger catches this upfront. In fact, this is one of the high-end features – only load the primary LISP file, any further debugging into other files resolves by loading during the debugging session. This is very handy for dealing with complex apps – there’s no need to preload any other LISP source. I’m sure you’ve experienced Murphy’s Law, where the particular function you need is the one that’s not loaded. You won’t have that problem in BLADE.

Steve: Where to from here? Is this job done or is there still room for improvement?

Torsten: As BLADE is still a very young product, there is definitely a lot more to come. So far, the main target was to provide good debugging features, and a somewhat reasonable handling of projects, but not so much focusing on plain editor capabilities.

My to-do list still has a number of major key features to be implemented. We want to add a hotkey editor, because every developer loves his own keystrokes and learning others is a nightmare! We also want cross-reference checking on a per-file and per-session basis, mainly for bigger LISP applications.

Then, over time, the editor capabilities will be extended and improved, providing more features. One example is to provide an editor tooltip that shows a function signature and short help when hovering over a LISP function name.

And of course, I’m aware that when people start using this in production, a lot of feedback will arrive from developers in the form of wishes, hints for improvements and bug reports. It’s very likely there will be many wishes to implement several details to make BLADE resemble AutoCAD’s VLIDE more closely. This could be a bit difficult sometimes, and is also not the main target. I hope that developers will be open to a slightly different workflow, given the big advantages they get in return.

In general we are very open to developer ideas, needs and requirements, as we are with BricsCAD itself. In the end, it’s the developer who needs to work with BLADE, as easily and productively as possible. Even the initial release of BLADE is based on important feedback from beta testers such as Martin Drese (CAD Wiesel).

Steve: I can certainly attest to how well you respond to feedback. I’ve seen bugs I’ve reported fixed in a very short timeframe.

Torsten, thank you for your time. This has been very illuminating.

This interview is also available in one post on the Bricsys blog.