Yearly Archives: 2017

Teresa from Autodesk in subscription interview

3 Replies

As a follow-up to the Pixel Fondue video I posted about earlier, Greg from Pixel Fondue conducted a follow-up interview with Teresa Anania, Autodesk’s Senior Director, Subscription Success.

Greg and I asked for your questions for Teresa and I passed on several of my own to him. A word of warning: don’t do as I did and watch through all 54 minutes waiting increasingly impatiently for those questions to come up. They don’t. Anyway, thanks to Greg for conducting this interview and to Teresa for participating.

Greg has now posted the video. Here’s the TL;DW (too long; didn’t watch) version:

  • Greg came up with some suggestions for making subscription more attractive (mainly to entertainment and media customers) and Teresa seemed open to those suggestions.
  • Teresa doubled down on a bunch of the spin that has been thoroughly skewered by myself and many others.
  • There was a rehash of the pricing information we already had a couple of months ago using the same figures Teresa provided in this blog post.
  • The one new piece of information was that somebody who switches from maintenance to subscription will be able to retain access to all prior versions held during perpetual license ownership. This could be interpreted in several different ways and it wasn’t clarified, so I guess we’ll have to wait for something in writing.
  • Despite what Teresa has apparently told some customers on the phone, there was no mention of a less unattractive subscription offer that involves keeping your perpetual license. Indeed, Teresa made it clear that trading in your perpetual license was very much still part of the deal.
  • Future costs for maintenance and subscription were as vague as ever but Teresa thinks it’s pretty impressive that Autodesk put out three years of pricing when asking customers to make a decision with decades-long implications.
  • Teresa wants you to give Autodesk a year to prove how wonderful subscription will be, and is very confident that subscription is for “the greater good”. (Andrew Anagnost also did the “give us a year” thing on Twitter so I guess we’ll see that theme repeated in an attempt to buy more time).
  • She has solemnly stated that Autodesk is never going to gouge its customers and wants to start building better relationships.
  • Teresa wants to hear from you and suggests the Autodesk Moving to Subscription forum as one way of getting in touch.

Here’s the video:

The big Bricsys interview 7 – the applications ecosystem

1 Reply

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

In this post, Erik discusses the Bricsys efforts to work with and assist third-party developers. He does this without being prompted by a question – it’s obviously very important to him.

Erik: For our future growth it’s very important, the ecosystem of the applications we have now. We have talked a lot about what we are doing and about our own products, but we should maybe have spent more time on the importance of the ecosystem. The worst thing we could do is forget the application market for us.

We will not, and we are not able, to develop another HVAC system or a [inaudible] system. We are limited in our resources and focused too much in our development. We believe that if there are five or ten HVAC packages, one in Germany, one in France, one in the US and one in Australia, all those guys understand their local markets and it’s very difficult to take an HVAC package made in America and sell it in Germany. The last thing we want to do is destroy that diversity of the application market. On the contrary, we’re going to encourage it. Therefore we will continuously provide APIs to the application market and invite and encourage them to become more professional. This support is so important. That’s where we can make a difference with many of our colleagues, and we should bring the application market to the same level of professionalism. That’s where we are investing as well. They can use all our systems for free.

It would be a great and a wonderful world if you as a customer if you come to our website or you go to an application website and finds the same systems and buys something, and communicates… if there’s a problem, it’s our problem. He can tell us, the application partner can tell us, if it’s an application problem we will tell them or the customer will tell them. But that kind of trio between the customer, us and the application market is so important. We need that.

We need those kind of applications working with our system. And they are there! For over ten years they have wonderful applications. The point is, they lacked, for the moment, the technology to grow into IFC and the BIM market. That’s what we are developing for them now. Right now we need the apps, and we’re delivering to them. But it’s a very important thing for us, that ecosystem. And again I think that’s another difference between us and many, er, alternatives (laughs).

Steve: Not saying “the A word” there…

Erik/Mark: (laughs)

Steve: It’s something I’ve noticed for years, actually, that you guys look after the third-party developers whereas Autodesk sees them as a revenue source.

Erik: Absolutely. We are convinced we need them. They have to say they need us as well. That’s a very good symbiosis. And the top of that is Intergraph. For us, it’s an application partner, right? There’s scalability a bit more than before.  If Intergraph takes this step, let us invite every other application developer to do the same.

This is the complete set of links to this interview series:

Autodesk products are falling like parrots

22 Replies

Autodesk is killing off products at such a rate I can’t keep up with it all. The latest ones to fall off the perch and join the choir invisible are Structural Detailing and Advance Concrete.

I think. As I said, I can’t keep up.

Despite the recent departures, Autodesk still has way too many products and it’s inevitable that the cull of Carl’s acquisitions and creations will continue. It’s just too bad if you’re one of the people using a product that Autodesk feels isn’t profitable and/or exciting enough, you’ll just have to learn to live without it.

Although 2017 has been particularly brutal for End Of Life experiences, Autodesk killing off products is of course nothing new. Autodesk is even named after a dead product (well, stillborn).

Trace back through Autodesk’s history and you’ll see a long and bloody trail of product corpses and wailing orphans. Maybe you’re one of those orphans. Tell us all about your experiences if you think it might be cathartic. Were you looked after?

What sort of product does Autodesk kill off? Let’s narrow it down.

Autodesk kills new products, old products, cloud products, desktop products, mobile products, free products, paid products, full products, add-on products, large products, small products, products that were bought just to kill off for anti-competitive reasons, products that have been ignored to death, and products that Autodesk hyped to the heavens as the best thing ever and if you didn’t get on board you’d be left behind with all the other Luddites and look silly and old-fashioned as your competitors strode off arm-in-arm with Autodesk into a wonderful bright future.

You name it, Autodesk has killed it. It would seem that almost nothing is safe.

To give you some idea what I mean, I’ve resurrected my Autodesk Graveyard page. I tried this a few years ago but it was too big a job to create and maintain it so I killed it (ironically enough). Thanks to Edwin Prakaso on Twitter for inspiring me to have another go at it, with a bit less detail this time so hopefully it’s manageable.

Image of war graves by Arne Hückelheim.
No disrespect intended to those who gave the ultimate sacrifice. Lest we forget.

The Autodesk Graveyard is by no means complete and what’s there may not be 100% accurate. Additions and corrections can be made by letting me know in the comments on this post. If you could provide references that show the birth and death dates of the products you know about, that would be ideal, but all feedback is welcome.

The big Bricsys interview 6 – lean and focused

7 Replies

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, the dynamic duo explain the mystery of how Bricsys can sell smaller numbers of a more capable product than AutoCAD for a fraction of the cost – and still make money.

Steve: It’s kind of interesting that your product is so much cheaper than AutoCAD, and more capable. They’re making a loss and you’re making increasing profits. How does that work?

Erik: I think it has to do with being lean and being focused. I mean, we’re talking about Autodesk, and we’re talking about AutoCAD and Revit and Inventor, but did you have a look at all the products they have? The managers that have to work on those products… I don’t study the detail of their annual figures, but I think it’s obvious that if you have that ton of products, not all of those products are profitable. Of course, not all of them are losing money, but you can’t call it lean.

What we are doing is… we are forced to be profitable. We force ourselves to be profitable. And then we have to be lean. We have four developers that constantly automate our systems, and that four will be extended again. That pays off big-time. It’s an investment; continuous, continuous, continuous. To invent new things where we can improve to be lean as well.

Mark: Stressing again that Autodesk has one hundred products, we basically have one product. We can see for mechanical, we can see for BIM, basically it’s one product.

Steve: It’s the same core.

Mark: It’s the same core, absolutely. So when we started to develop BIM, we used the same toolset as we used for sheet metal; exactly the same. Of course it’s tweaked to be used in BIM or sheet metal, but in the ground it’s the same.

This is the complete set of links to this interview series:

Props to Bricsys for supporting education

2 Replies

Some time ago I raised a glass to Autodesk for supporting students and educators by making its software available free. I have been remiss in neglecting to point out that Bricsys also does this.

So I raise a glass of dark, tasty and ridiculously strong Belgian beer to Bricsys for doing this. Cheers!

The big Bricsys interview 5 – perpetual licensing and choice

Leave a reply

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

In this post, Erik confirms the Bricsys commitment to perpetual licensing. That’s a statement important enough to preserve, so here’s the recorded audio for posterity.

We also learn what proportion of CAD customers choose perpetual licenses over rental when given fair pricing and the choice. Hint to Autodesk: it’s not 0%.

Steve: Are you committed to the perpetual licensing model?

Erik: Yes, yes. We are committed to choice. If somebody wants another way of licensing our stuff, that’s fine as well. I mean you can hire our stuff, you can pay per month, it’s possible.

Steve: That’s not in all markets, is it?

Erik: We don’t promote it, but it’s possible if somebody contacts us, no problem. It’s choice, and we believe in choice. It’s not up to us to impose how people work with our stuff. But perpetual, it’s fair, I think. Somebody buys software, it’s always been like that, and we have to continue that. And we will continue that. Read my lips! We will continue.

All: (laughs)

Cyrena: Speaking of choice, can you talk about the type and portion of users who go for rental rather than perpetual?

Mark: Of course the vast majority go for perpetual.

Erik: 95% buyers.

Mark: When you see these clients in Russia that have these big oil projects in Siberia for six months or whatever, then it [rental] might make sense. But with the channel… 95, 97, 98% is just perpetual.

But what we see more and more is people are asking about it [rental] more and more, because of course in the Autodesk world there is no other option. So of course people just want to compare apples with apples.

Steve: So they’re just asking for the numbers?

Mark: Yes, for the numbers, “What would it be?” That’s the feeling that we have, ultimately when they make a decision they’re going to go for perpetual.

Erik: Because the price is acceptable as well, I think. It’s not that high a price for a substantial amount of software, so it’s not a problem.

Mark: Our price levels are completely different, of course. It’s affordable.

This is the complete set of links to this interview series:

Clearing up the Autodesk rental / subscription / maintenance naming confusion

3 Replies

Some people are confused by Autodesk’s naming terminology about subscription, maintenance and rental. This is entirely Autodesk’s fault, because it took a name (Subscription) which had a long-established meaning (including perpetual licensing) and used that name (but without its initial capital) to mean the opposite (no perpetual licensing).

There was a brief period, only last year, where the S word meant both things at the same time and differentiation between the opposing meanings was achieved using different prefixes.

Confused yet?

I’m not sure whether it’s kinder to view Autodesk doing something so obviously confusing as merely incompetence in communication or a deliberate attempt to confuse and deceive customers and/or the share market. Or maybe it was an inspired choice and I’m too obtuse to comprehend its genius. Choose whichever explanation you prefer.

In an attempt to clear things up, but at the risk of confusing matters further, Autodesk’s naming history goes something like this. The years shown below are approximate and some of them varied for different products and markets.

Year
 Name for perpetual license + pre-paid upgrades Name for rental
1997-2001 VIP Subscription Program –
2001-2003 VIP Subscription Program Rental
2004-2012 Subscription –
2013 Subscription Rental
2014-2015 Subscription –
2016 (briefly) maintenance subscription desktop subscription
2016- maintenance subscription

The current rental regime, which has run under two names to date but is currently called ‘subscription’, is the third attempt Autodesk has had at rental. The first two attempts failed in the marketplace because the vast majority of customers prefer perpetual licenses.

The big Bricsys interview 4 – thank you, Autodesk

Leave a reply

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, we learn that Autodesk’s move to all-rental has helped drive BricsCAD sales higher and continues to do so.

Cyrena: Backing up just a step to sales, were you able to track any impact on your sales numbers with the chronology of Autodesk’s announcements of ending perpetual? Did you see an effect that you could map to that?

Erik/Mark (together): Yes.

Erik: We see that especially with large companies. I hear it from Mark always!

Mark: That’s what I wanted to explain this morning too, although we have an indirect sales channel, we have our resellers at work out there, especially with the large deals, we are involved always. So there’s always one of our guys, a business development manager together with the local sales person in touch with those larger corporations.

In the last few weeks, we have received tons of emails from large corporations; of course it’s hard to disclose them, but… [names a corporation]. It doesn’t mean they will switch right away, but we have meetings where they say that, “Our contract with Autodesk ends in July, August, whatever, that’s the time we will not extend it. We will not renew it, we will not go to subscription, and we are looking for alternatives.” These are really big, big, corporations. So yes, yes, we see an impact.

Erik: When it comes to alternatives, and with all respect to our colleagues [competitors], we are not the only alternative, but I think we are in a good position. If you see what we have to give people a perspective beyond AutoCAD, well…

If we would only be an AutoCAD clone, and AutoCAD stops further development, it would mean the clones stop further development more or less as well. And all of a sudden the market is going to 3D mechanical, 3D BIM, etc., then it’s a problem. I think that’s where we can play an important role.

The DWG market, the DWG community, if they really want to move on slowly, slowly (and everyone makes his own choices about staying on 2D AutoCAD-based, fine as well), but at least there is a growth path. And I see that BricsCAD is the only product that goes in that direction. All the other alternatives more or less stay around what Autodesk is presenting, with a few differences here and there.

But it’s not really mainstream that there is investment in R&D or really a big jump of other stuff than just being compatible with AutoCAD. It makes a difference.

This is the complete set of links to this interview series:

Schrodinger’s CEO – Autodesk top job speculation

Leave a reply

In an earlier post, I asked for your votes on a pair of polls regarding Autodesk’s replacement for Carl Bass as CEO.

Here are the final results from those polls. Although the details of who voted and for what will remain strictly and permanently confidential, I found it interesting to see a number of votes logged from IPs that originate from a well-known software company. I will get no more specific than that.

First, here’s who you think is most likely to be appointed:

Amar’s well ahead in the “person most likely” poll. But note the contrast with who you actually want to be the next Autodesk CEO, where outsiders get bigger numbers. Anyone would think people reading this blog aren’t happy with what the Autodesk candidates have been doing and would like to see a change.

Despite Elon Musk’s popularity, I suspect he may be a little too occupied right now to take on the Autodesk job and give it the attention it deserves.

Among CAD notables I talked with in Ghent, the general view was that the delay in the appointment of a CEO is bad news for current co-CEOs Amar and Andrew; if the Autodesk board was going to give the job to one of them that would have already happened.

I’m not so sure about that. The board might be so happy with the job A & A are doing that they feel there is no rush, but who knows? Maybe the board is struggling to find somebody else with a name where (wcmatch ceoname “Car*l Ba*”) returns T. Maybe one of the dynamic duo has already filled out the deed poll forms and will emerge as Carmel Bartholemew or something.

The big Bricsys interview 3 – looking after people

4 Replies

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, I learn about Bricsys’ astonishingly good staff retention record and the reasons behind it.

Autodesk likes to periodically pat itself on the back for being a great employer, but history shows it’s a company that discards about 10% of its workforce every few years to keep the share market happy. I suspect another round is coming up soon, unfortunately. There’s a stark contrast between a company that disposes of its chattels in that way and one with a CEO that says, “…every time somebody leaves the company that’s really, really bad.”

You as a customer may not think that matters to you, but it does. I believe there is a direct correlation between Autodesk losing knowledgeable staff and Autodesk repeating old mistakes and breaking things. If today’s developers don’t know why some things in the software are the way they are, or why most changes should automatically come with an off switch, or why some things shouldn’t be done at all, or even how a feature can be maintained (e.g. Visual LISP), then the product suffers. AutoCAD users have to deal with the consequences of those knowledge holes with every release.

As in so many other areas, Bricsys proves to Autodesk that it doesn’t have to be like that; there is a better way.

Steve: Speaking to your people, they appear to like working here and they stick around. What’s your staff turnover like?

Mark: It’s very low, very low.

Erik: Job-hoppers, you mean? People who leave? I think in the last fifteen years… maybe five, six, something like that?

Steve: Wow.

Mark: I remember the reasons, maybe two or three times here, maybe having to leave to move to another city or another country. There as well, we try to find solutions.

We really have a good team atmosphere and if those people can work, if they’re a developer for example, people can work from remote areas. We have a guy who has been working for us for years who is now working from Turkey. That was the discussion we had, “I have to leave because I’m moving to Turkey now.” No, you don’t have to leave, just work from there.

Erik: I will add that in Novosibirsk (Bricsys Russia) it’s more difficult to keep the people. We are growing very fast there. We started when we took over the LEDAS team with 3D modelling, we started there with six or seven people. We now have thirty. Along the road for the last four or five years, maybe five or six left. In percentage, that’s way more than we have here. We are stopping the bleeding now!

Steve: That’s still fairly low!

Erik: That’s still fairly low but every time somebody leaves the company that’s really, really bad. We are investing a lot in making it comfortable for our people. To give you an idea we have a culture here of every Friday, we go to the pizzeria for lunch here. We have our own floor there in the restaurant every Friday. Sometimes we talk about software but sometimes we talk about politics and sometimes just rubbish and nonsense and a lot of fun.

Mark: Mostly!

Erik: But we give a budget to all our teams. In Novosibirsk they do that as well. So they have a budget and we force, well, encourage them very strongly to do that.

Mark: Same in Singapore, [inaudible], all our teams.

Erik: Every year, with all the families, we go to a chateau near Paris for three to four days. In Novosibirsk they have a budget to go for a trip with their families once a year, if there is a special occasion. That’s investing in your people.

If anyone has a problem, everyone knows that all doors are open, that we will try to find a solution to make you comfortable. We always say to our people here that the last thing we want is if they are stressed. It doesn’t work for developers and for a company like ours. No stress.

I was really sorry with Dieter yesterday [one of the presenters at the press event]. They only told him the day before to give a presentation! He’s not used to doing that. He was really good about it as you all saw, but he was really stressed. We will avoid putting him in that situation ever, ever again. It doesn’t work.

But for the rest, even with deadlines, we change priorities then, but we don’t want people stressed. And that has a very good result. If you see where we are coming from, what we have, in fifteen years, millions and millions of lines of code, of testing code as well, it’s a ton of development that is done, quality that we have developed. So far, so good, without stressing our guys. Why would we change that?

Mark: Also, the transparency we show to the outside world with the bug reports and so on, that’s also done internally. Everything here is open. On a quarterly basis we get everyone together, we show the numbers, it’s no secret at all internally. So everyone knows how the company is going, how things are moving, new projects that we are doing, and that feels nice with people.

This is the complete set of links to this interview series:

Minority interest in keep-your-perpetual Autodesk subscription idea

1 Reply

It’s undeniable that the vast majority of Autodesk’s customers don’t want to give up their perpetual licenses to sign up with Autodesk’s subscription (rental) model. I’ve gone through the evidence for this in an earlier post.

To bring that up to date a little, here are the final results from the poll “Autodesk is ending the sale of perpetual licenses. This is: (Good/Bad)”:

People are clearly attached to their perpetual licenses, regardless of what Autodesk does to manipulate prices.

A while ago I floated the idea that Autodesk might possibly come up with a better offer; one that lets you keep your existing non-upgraded perpetual license when signing up for subscription. I wanted to know if there was any more interest in that, so I wrote a post around that and created another poll, “Would you be interested in switching to Autodesk subscription if you could keep your old (non-upgraded) perpetual license? (Yes/Maybe/No)”. Here’s how the results ended up:

While the level of interest in this idea appears higher than in Autodesk’s current unappealing offer, it’s still not great. It seems most people don’t just want perpetual licenses for the sake of it, they want an escape route: the option to stop paying and keep playing, regardless of file format and OS compatibility issues. That means they want those perpetual licences to remain current.

The upshot is that Autodesk is going to find it very difficult to push most of its existing customers onto subscription, no matter what the offer.

The big Bricsys interview 2 – making money

Leave a reply

This is one of a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh. In this post, I ask about Bricsys’ profitability and growth.

Steve: Do you publish your numbers?

Erik: No we don’t. We are a private company.

Steve: Can you give us an indication of what’s happening with your sales at the moment?

Erik: Last year we grew in revenue 25%. First quarter this year was up 27% over the same quarter last year. If you compare the sales in total of 2016 compared with 2015, it was 25% in growth. It means that the growth is going faster and faster and faster. That’s what we expect normally as well.

This is without any sales to Intergraph. We expect that the Intergraph deal will have an impact on our growth for sure. Mark as COO is responsible for sales and managing of that network. [To Mark] And I see you’re very occupied!

Mark: That whole Intergraph network is coming to us. It’s huge.

Erik: It’s more than doubling what we have, on sales partners.

Mark: Just to add to the numbers, we are very profitable: 24, 25%. We have very good profitability which is also significant. We’re not burning money.

Erik: Year after year.

Steve: So you’re making money every year and that’s increasing every year?

Erik: Yeah, yeah, absolutely. The percentage is always around 24-25% but as we’re increasing revenue it becomes exponential.

Mark: We started in 2002 and I think we have always been profitable.

Erik: I think the first two years are what we call a black zero. We have started with an investor, but we have always kept a majority within the company. I won’t give the total shareholders but you must know that most of the people here, if somebody works here two years they get stock options and becomes a shareholder. The goal is we always keep the majority with the employees and the management.

We have a good partner investor. He’s satisfied with the growth, of course. There’s no big deal.

This is the complete set of links to this interview series:

The big Bricsys interview 1 – why invite the press?

Leave a reply

This is the first in a series of posts covering an extensive interview with Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh.

On April 26 and 27, I attended Bricsys Insights, a press event in Ghent, Belgium. Other attendees included Cyrena Respini-Irwin (Cadalyst editor in chief), R.K. McSwain (CAD Panacea), Ralph Grabowski (upFront.eZine), Randall Newton (GraphicSpeak), Roopinder Tara (Engineering.com), Martyn Day (DEVELOP3D), Jeff Rowe (AEC Café), Anthony Frausto-Robledo (Architosh) and Paul Wilkinson (pwcom).

Although Bricsys has invited some of these people (including myself) to previous events, this was the first gathering of such a significant number of illustrious industry press, bloggers and observers. So when myself, Cyrena Respini-Irwin and R.K. McSwain had the opportunity to interview Bricsys CEO Erik De Keyser and COO Mark Van Den Bergh, the first thing that we asked was this:

Cyrena (clarifying earlier question): What was the change that led you to bring in more people for the press event?

Steve: Why are we here?

Erik/Mark: (Laughs)

Cyrena: That’s a big question!

Erik: If you look to the history of what we have done and it goes together with what we said in the beginning, that we chose to grow by organic growth, and for a long time we didn’t do any marketing, and especially for the American market, because if you do it too early… And really, if we had done that massively, five years ago we would have been categorized as just another clone of AutoCAD. Once you have that, it’s very difficult to leave that, and that’s exactly what we wanted to avoid.

And so we waited until we had really substantially different product technologies that add a lot of stuff to… if you compare it to AutoCAD, I think that’s the moment where we are now. And we decided from that moment on, probably it made sense that we tell it a little bit more to the world. And of course what do you do then? You invite influencers in the market, which is the journalists. That’s the reason we invited you all.

We’re going to repeat this more and more.

Mark: Just to add to that, just sitting here for just two days with you guys also helps us to really talk about everything. If you go to a conference (you [Steve] were also in Munich), the time is limited and so we don’t show the systems behind, the testing system, we cannot show everything.

The idea here was, OK, these are the things we’re doing, what you see of course but also what is behind, the people behind the DNA of the company. We thought that’s a good idea to do that in depth with an audience like you guys.

Erik: That’s an important element as well that we wanted to show: the DNA of the company. It’s a bit different from others. That’s who we are and it’s important to know.

Steve: You’re about 90% developers, programmers. Do you think that’s going to change as you put more effort into marketing?

Erik: I think that the awesome part of the company that has to be improved, and on the marketing side we’re going to need to improve… to give you a rough idea we think that over the next two, four years we’re probably going to grow to maybe 200-250 people.

Steve: So where are you now?

Erik: We’re at 130-140. We just hired six new developers here in the office last week so we have to recount where we are in total. Dmitri is hiring in Novosibirsk (Bricsys Russia) as well.

So for sure we are starting what I would call a second life now. There’s been a lot of development, but still the majority of people in our company will be developers. I think we’re always going to stay around 80% developers. But there’s a part of the business, and especially in the marketing, that we will have to improve.

What we have encountered now, with the new modelling techniques we have introduced for BIM, we have to teach all the resellers. We have to produce material to teach the people how to work with it. These are not developers we’re going to need. We’re going to need seasoned architects that have experience for the last six to ten years with BIM already, maybe with competitive products. But that understand the concept, have experience with it, those guys we are now attracting and we’re going to need. Those are not developers, but in that sphere we have to extend and we have to grow. And that’s what we’re doing. We are hiring.

The focus will always be… what we’re good at, is basic research and development. That’s really what we’re doing, that’s the focus, and the results are the products we make.

We have a good partnership network I think, we’re going to continue to feed that, so I expect that balance between developers and non-developers to remain always above or about 80%.

If you have a look at the system, how we sell and support our products, we are scalable, to maintain that balance of a high level of developers. There’s no need for us to change that model. But in certain aspects we’re going to have to extend.

BOA (Bricsys Online Administration) is helping us tremendously to be scalable. If we were to double our revenue we wouldn’t need that many more people to manage that. We are constantly investing in automating all the systems we have, and it pays off big-time.

Cyrena: So that very heavy R&D investment you’ve sustained thus far will be scaled back a little in order to invest in other areas such as marketing?

Erik: Yeah, but it doesn’t mean we will scale back from development. We will grow in development as well, but the balance will be a little bit different; the proportion is different. We will grow tremendously, even more still in R&D when it comes to number of developers than in any other area over any other field or kind of employee that we have.

This is the complete set of links to this interview series:

Disclosure: Bricsys covered travel and accommodation expenses and provided some meals. Oh, and beer. Mustn’t forget the Belgian beer.

Autodesk’s revolting customers are evaporating

2 Replies

The revolting customers themselves aren’t evaporating, of course. They remain solid and are still as irate as ever. It’s just that the appearance of outrage is gradually fading away on the Autodesk Community forums.

As mentioned before, forum moderators have been busily vacuuming up threads from all over the place and moving them to the Moving to Subscription forum. Some time in the last week or so, that forum became less visible. It’s no longer listed among the bold links on the right pane under Subscription Management, but for now can still be found (if you look hard) in the list of 96 forums. Or at least you can get to the page above that forum, from where you can click on another link.

As it’s now so hard to find, I’ll help Autodesk with its sincere desire to be transparent about its extortion scheme, er, wonderful discount offer by making the link a bit easier to find. Here it is:

Autodesk Moving to Subscription forum

Don’t mention it, Autodesk!

Oh, and the first time I tried to get in as a signed-in user, I got kicked out to the top forum list level. Don’t give up, try again and it should work.

From the beginning, I’ve had no doubt that the main idea behind the forum is to keep customer dissent neat and tidy in one easily-hidden place. It will almost certainly lose its final link in due course, then it will be made read-only and merged into semi-oblivion, just like the last one. When I dared to suggest such an outrageous thing, an Autodesk moderator accused me of being a conspiracy theorist.

Well, melt my steel beams with jet fuel, look what’s happening! Who would have thought it?

I’ll be sure to let you know when each of the final evaporation stages occurs. If you happen to notice before I do, please let me know and I’ll pass the information on to my readers.

BricsCAD documentation – a tale of three systems – part 3

11 Replies

In this third post in what was supposed to be a two-part series, I have more to say about the BricsCAD documentation system. See here for part 1 and here for part 2.

Developer Help – Addendum

In this comment from Bricsys API person Torsten Moses, he informed me about the availability of the Lisp Developer Support Package (LDSP) in the Bricsys Application Catalog. As always, when presented with new evidence I am prepared to re-examine my position on anything. Therefore, I will now further discuss the BricsCAD developer documentation.

The first thing to mention is that the existence of the LDSP package is not obvious. To somebody who uses BricsCAD as-provided and as goes burrowing down through the Help system looking for information, that system is still broken. The documentation as presented to the user remains sub-standard, exactly as described in part 2.

Assuming you know of the existence of LDSP, how do you go about using it? Here are the steps:

  • Go to the Bricsys Application Catalog site, click in the search field and start typing LDSP (you don’t need to hit Enter).
  • The link to the Lisp Developer Support Package (LDSP) will appear: click that.
  • Enter your email address, accept the privacy agreement and pick Download. (Note in passing that this is actually published by Torsten’s own company, not Bricsys).

  • If you’re already a registered Bricsys user (you will be if you’re evaluating it), the download will start. If not, you’ll be expected to register (free):

  • Once you’re registered, the download results in a 12 MB file called Lisp Developer Support Package.rar (RAR is a ZIP-like format).

Any recent commercial ZIP utility (e.g. WinZip) will open RAR files and there are a variety of freeware/adware/shareware utilities available to do likewise. For example, RAR Opener in the Windows Store will present itself as the first option in Windows 10. But it goes without saying that going off in a hunt for utilities wouldn’t be on anyone’s expected to-do list when just looking for product help. A bunch of people would give up here, if not earlier.

I went through with installing RAR Opener, but when I attempted to open the LDSP file I saw this:

Oh, and a handful of empty folders were produced. Is there an email waiting for me at work with the password (my Bricsys registration email is at work but I’m at home)? Am I really supposed to have a password to open this RAR? If so, why wasn’t I prompted for one? RAR Opener doesn’t present me with that option anywhere I can see. Is the download corrupt? Does it refuse to work on a Sunday? I have no idea.

At this stage, many more would give up. How many prospective customers would be filtered out by this experience? There’s no way of knowing. However, I’m made of sterner stuff and persevered with downloading and installing another app from the Windows Store. 9 zip did the job and uncompressed the file, no password required.

Yes, the RAR Opener problem I had above isn’t a Bricsys problem directly. But it is indirectly, because the file I was given to deal with won’t open by default in Windows, where the vast majority of BricsCAD users will be working. It’s a level of obfuscation that you can get away with when dealing with cellar-dwelling geeks handling obscure pieces of open source software. It’s not appropriate for customer-facing documentation in a mainstream CAD application. Yes, even developer documentation, because with CAD applications like AutoCAD and BricsCAD, most of the developers are customers/users/managers, not people trying to sell utilities.

Once you manage to get the file uncompressed (it becomes 41 MB), there are three help systems provided in there (CHM, PDF, HTML). That’s excellent, and conforms nicely with the Bricsys philosophy of providing customers with choice. I was unable to find any broken links. However, even in the LDSP, standard AutoLISP functions are undocumented. So I still couldn’t find the (entget) help I was looking for in part 2:

According to Torsten:

…the standard AutoLISP functions like (entget) are not documented, as there are plenty docs on the web for this; but we document any extension beyond AutoLISP standard, even for the standard functions.

Sorry, but while “we don’t have that information but you can Google it” might have been an acceptable answer for a cheap AutoCAD clone’s API documentation ten years ago, that’s not where BricsCAD is today and most definitely where Bricsys wants it to be in future. Just two days ago, Bricsys CEO Erik De Keyser sat across a table from me and told me that BricsCAD isn’t intended as merely an AutoCAD alternative, but must go well beyond that in order to prosper. He’s right. The BricsCAD developer documentation today is not compatible with that vision. I know it’s that way for historical reasons, but we’re now at a different point in the historical timeline.

Conclusion – Addendum

My conclusion from Part 2 remains valid, despite the existence of LDSP. Both Autodesk and Bricsys have work to do. Downloading LDSP will help with some of the BricsCAD developer documentation failings but leaves plenty behind. It also provides its own set of unfortunate challenges.

This isn’t just a technical and ease-of-use failing, it’s a marketing one. That’s because it acts as a stumbling block to conversion of AutoCAD sites to BricsCAD. Disaffected AutoCAD power users in small sites and CAD Managers from large sites are right now taking tentative steps to evaluate the suitability of BricsCAD to replace AutoCAD in their complex LISP-heavy custom environments. They’ll want to know what’s the same and what’s different so they can estimate the effort and cost involved in the transition before getting in too deep. I know this, because I’ve done it myself. The first thing they will come across in their search is disjointed, very inconvenient and incomplete. It presents a less-than-professional image.

Some potential customers, like me, will persevere and discover that the quality of the developer tools implementation far exceeds the expectation generated by the documentation. Others will give up well before they reach that stage, and that’s a shame.

Autodesk acquires Angry Birds developer Rovio (repost)

2 Replies

This post, originally published on 1 April 2012, brings back fond memories. That’s mainly because of this tweet from Carl Bass:

Autodesk announced today that it had welcomed Rovio Entertainment into the Autodesk fold. Following a US$2.6 billion acquisition, the publisher of mega hit video game Angry Birds is now Autodesk’s Mobile Entertainment division based in Espoo, Finland. “This is a tremendously exciting development for Autodesk going forward,” said Autodesk CEO Carl Bass. “Rovio is the world leader in mobile entertainment software,” he added, “so for Autodesk to have access to that market and that technology opens up a whole new world for us.”

Bass was effusive about the synergistic benefits of the merger and the benefits it will bring to the user interfaces of all Autodesk products. “When a kid starts playing Angry Birds, they don’t need to read a huge mass of documentation. Just show them a few cartoons and they’re away, instantly productive. This is the essence of the democratization of design; it’s not dumbing down, it’s funning up.” This potential ease of use is excellent news for AutoCAD users, because the documentation is now so terrible that it will be wonderful if we no longer have to try to use it.

Former Rovio CEO, Taikke Monniennren, now Autodesk Vice President in charge of Mobile Entertainment, is equally excited about the future. “We have already been given access to the Autodesk code base and my developers can see the potential there. By copying and pasting some code modules, we hope to be able to piece together the Angry Birds 3D Max Suite in a few short years,” said Monniennren. “The main challenge will be in keeping the download size manageable, but with a bit of luck we will be able to keep it down to just a few gigabytes.” In comparison, the original Angry Birds game was just over a megabyte.

“Do not underestimate the strategic importance of this announcement,” said Bass. “Although it may come as an unpleasant surprise to our competitors, our customers are well aware that this is the direction we have been moving for some time now.” This is true. Autodesk is doing whatever it can to appear young, hip, cool, trendy, mobile, social and just totally with it, man. It has been talking and sometimes acting big on Cloud and mobile computing for a while. Clearly, acquiring Visual Tao (now AutoCAD WS) was just the beginning.

Who would dare to call Autodesk antisocial? Autodesk videos are all over YouTube. On Twitter, many key Autodesk people tweet many times a day. The recent AutoCAD 2013 launch in San Francisco was done entirely via Facebook (which enhanced Autodesk’s green credentials by allowing a reduction in the number of press and bloggers flown in from around the world to only 120). The first thing a new AutoCAD 2013 user sees on installation is a Welcome screen that is largely dedicated to Autodesk pushing its app store and Facebook and Twitter pages. Because the Welcome screen phones home on each use, Autodesk can easily slip in new links to any other sites it wishes to promote. I expect your AutoCAD 2013 Welcome screen will sport Angry Birds gaming links within a few days. Angry Birds gaming plug-ins for AutoCAD and related products are likely to appear in the app store soon, but I expect we will have to wait for AutoCAD 2014 until the games become part of the core product.

Clearly for Autodesk, kids are the new adults. But is what spoiled teenagers do on their iPhones really a sound basis for the needs of professional CAD users in a corporate environment? How well does this concept work in practice? Bass answered that by showing a prototype user interface for AutoCAD that uses the new technology. He demonstrated it on a 48″ touch-screen, but it is believed that it will be at least partly functional using old-fashioned mouse-based technology.

Bass started by selecting a red bird from the Ribbon, which sported a snazzy new flouro theme. He dragged the bird down into the drawing area (which had a beautiful animated background with kittens, rainbows and unicorns; let’s hope that makes into production). While this was going on, the system was providing haptic feedback, with the screen vibrating and the bird squawking when dragged close enough to an existing object. By dropping the bird close to the end of a line, Bass was able to start drawing a line from exactly that point. He then drew back the bird and released it such that it was launched in the direction he wanted the line to go. As the bird shot forward, Bass touched it just as it crossed another line and it snapped on to the midpoint with a happy chirp. Perfect!

He then demonstrated other birds in action. To draw a polyline you use the yellow bird and touch it at each vertex as it flings itself along your desired path. To explode a block you use the black bird, triggering a loud explosion which I think will have to be toned down for office use. Ellipse? That white chicken thing that lays an egg. Multileader? The little grey one that splits up when you touch it. And so on. Bass already has his Finnish developers hard at work devising hundreds of new birds that cover most of AutoCAD’s key functionality. Some unimportant features, such as plotting and xrefs, are difficult to translate into birds and will be deprecated into command-line-only versions before being dropped completely in a future release.

The demonstration had to be curtailed after a few minutes when Bass’s arms became too tired for him to continue, but it provided an enticing view of a future where CAD is fun, fun, fun! Addicted users are productive users, according to Bass. “If you’ve ever seen kids playing Angry Birds, you know that they will happily sit there playing it all day every day without complaint. They don’t even stop to eat. The only time they take a break is when they’re forced to visit the bathroom. Even when they’re in there they will probably photograph themselves in the mirror and post it on Facebook. CAD Managers, don’t you wish you could tap that astronomical productivity resource?”

According to Bass, those managers will soon be able to do exactly that. His advice is, “Fire the old fuddy-duddy naysaying Luddites who are allergic to change and replace them with a bunch of kids off the streets. Give them Autodesk software they can’t resist using and they’ll soon be flinging pixels around like there’s no tomorrow. You’ll have an instant office full of the cheapest engineers you’ll ever find, and they’ll be begging you to take their work home with them. With the literally infinite anytime anywhere power of Autodesk 360, they’ll be able to do exactly that. In a few years, the kids in hoodies you see hanging around shopping malls won’t be waiting to snatch your bag, they’ll be leeching wi-fi so they can design your next car on their phones. And they’ll be doing it using Autodesk software.”

Bass refused to be drawn on leaked details about the upcoming iPod Shuffle version of AutoCAD or its supposed marketing slogan Shake to Design, though. “We have a very strict policy of never discussing our plans for future products,” he explained, “except when it suits us.”

The marketing gurus at Autodesk have written an independent productivity report that shows that AutoCAD with the new interface improves productivity by 632.7%. On Windows only, that is. This productivity phenomenon will not apply to AutoCAD for Mac, because there are no plans to provide the Angry Birds interface on OS X. Autodesk believes that this won’t concern Apple users, because Macs are shiny and look really nice.

The impressive productivity figure was generated by performing carefully selected tasks on AutoCAD 2013 using the prototype interface, when using the latest, fastest and most expensive hardware. This was then compared with completely different tasks performed using AutoCAD 1.4. On a twin-floppy IBM PC. With a 12″ monochrome monitor driven by CGA. But without an 8087. The resultant percentage was then multiplied by the number of years since Autodesk produced an AutoCAD feature that wasn’t half-baked on release.

In related news, Autodesk’s legal department has lodged applications to register the words ‘Angry’, ‘Birds’ and all images of feathered flying creatures as Autodesk trademarks. Cease-and-desist notices have already been sent to publishers of ornithologist guide books. Also in Autodesk’s legal sights is Disney Corporation, which clearly violates Autodesk’s intellectual property rights with its depiction of Donald Duck as not just a bird, but frequently as an angry one who goes around smashing things up.

The last word goes to Bass. “Look, the trend is irresistible, and those who can’t keep up will be left behind. Here at Autodesk we believe in freedom of choice. You can either choose to follow our vision of the future, or take to the streets with a cardboard sign and a chipped enamel mug. What could be more democratic than that?”

Hot tip for Autodesk

10 Replies

Hey Autodesk high-ups, I’m sorry you’ve been having so much trouble persuading your customers to throw away their perpetual licenses and throw themselves on your perpetual mercy. It’s clearly difficult to persuade technical types to do dumb things like rent your software at enormous and ever-increasing prices. I feel for you. But there’s an answer.

Find dumber customers.

Lots of them. And fast, before the stock market notices that you’re no Adobe and we’re not buying it. Sorry, I mean not renting it.

Look no further! Simply buy this company, discard the product when you’re bored with it (you’re very familiar with that process) and get hold of the customer list.

Sell subscription software to those people. They’ll have no idea what they’re renting or why, but that doesn’t matter. They’ll buy anything that’s pretty, hip, now, connected, and preferably organic. They will commit to perpetually shelling out large sums just to keep using it, no matter how poorly it performs. They’re rich and dumber than rocks. All of this makes them ideal customers for you.

If you’re a bit strapped for cash at the moment, just have a word with the investors (including Google) who pumped $120M into an Internet-enabled $700 (sorry, now $400) machine that squeezes expensive pre-squeezed juice out of DRM-protected short-lifespan bags, and manages to do it slower and noisier than you can do it with your bare hands. They’re even dumber than the customers, so squeezing money out of them will be easier than squeezing juice out of a bag when the Wi-Fi’s down.

This is a perfect fit for you, Autodesk. It has everything you need to ensure mission-friendly proactive synergistic compatibility on a going-forward basis. It’s disruptive. It looks good. It’s an overpriced, poorly functioning product. It has on-point (but pointless) compulsory connectivity. It ties users into paying whatever you ask, for ever. And best of all, it connects you to a collection of completely clueless cashed-up customers.

Thanks to @internetofshit on Twitter for making me aware of this and other hilarious Internet of Things (IoT) idiocy. Examples:

Enjoy!

BricsCAD documentation – a tale of three systems – part 2

3 Replies

In this pair of posts, I describe the BricsCAD documentation system. Click here for part 1, where I describe the general Help system and the descriptions in the Settings command.

In this part, I discuss developer documentation and draw my conclusions.

Developer Help

If we count the Settings descriptions as a system, there’s a third documentation system for BricsCAD. The Developer Reference isn’t offline and included in an install like the main Help. Instead, it’s online, just like Autodesk’s default. Unlike Autodesk’s system, it works pretty well.

Being online means the performance suffers, of course, but it’s generally not too bad. It appears quicker than Autodesk’s. A link within the main Help system takes you to the Bricsys Developer Reference which is just accessed using your default browser. Of course, that means your mouse buttons work correctly and you have all other the advantages of whatever functionality is built into your browser.

Hot tip: you can get to a real browser from within the AutoCAD pseudo-browser thing too, by right-clicking on a link and picking Open in Browser. The URL takes a while to mangle and unmangle itself before you get to read any content, but you get there in the end.

Unlike the general Help, the BricsCAD developer Help system isn’t so obviously superior to its AutoCAD equivalent. This is largely thanks to the outstanding efforts of Autodesk’s Lee Ambrosius who has managed to take Autodesk’s pig’s ear of a system and produce perhaps not a silk purse but at least a decent-quality cloth bag. It can’t have been easy.

Like the main Help, the BricsCAD online developer reference has a Contents mode with structure:

There’s an Index:

And there’s Search:

As the last image shows, the system contains not only missing information (where’s the (entget) description?) but also broken links; this wasn’t the only 404 I came across. That’s a bit embarrassing, Bricsys. There’s a lot of work to be done yet to bring this up to scratch.

There’s no Favorites section, but of course that’s built into your browser so it would be pointless reproducing that.

Of course, you can’t get context-sensitive help on functions within your LISP code from VLIDE, because BricsCAD has no VLIDE.

Conclusion

The BricsCAD documentation system is notably better than the AutoCAD one in many ways. However, it’s a long way short of perfect. Many aspects need attention, and there are multiple holes to be filled. Sometimes I find myself forced to use AutoCAD’s general documentation system to find out something about a system variable that’s common to both systems. That shouldn’t be necessary.

I’ve hardly mentioned the content of the respective documentation systems, but I must say Autodesk’s content is often superior (thanks, Dieter). But there are exceptions; the BricsCAD descriptions and pictures of various commands and options are better in some cases. For example, try to find out what the various options of the PEdit command do in both systems. With BricsCAD, it’s all laid out on one page and nicely linked.

The AutoCAD command documentation has been pared down too much in places to make each page shorter and simpler, hiding the content beneath sometimes obscure links. It’s possible to find out what the Pedit options do in AutoCAD, but it’s certainly not BricsCAD-easy and I initially gave up after chasing my tail for a while. I went back and found it later, but it took a lucky guess. Giving up after looking through a circular set of links is a common experience with AutoCAD’s Help. There’s a programming concept called mutual recursion, but I don’t want to experience it during a vain search in a Help system, thanks. A visible, navigable structure would help eliminate that issue, but there isn’t one. There needs to be one. Did I mention that already?

With system variables, BricsCAD’s Help is consistently and clearly inferior to AutoCAD’s. The AutoCAD content also tends to be better worded, with the BricsCAD wording being occasionally slightly awkward in a non-native-English-speaking manner. There are also some formatting issues with wide gaps left where the system attempts to expand command descriptions to the right margin and does a poor job of it.

As with AutoCAD, there are many video tutorials available for BricsCAD. I have not considered these in my evaluation but the few I had a look at were pretty good.

Who wins? Nobody. It’s a draw. Both companies need to step up. Autodesk mainly with its awful structure-free system, Bricsys mainly with its incomplete content, particularly for developers. But both companies have work to do in all areas.