Category Archives: Thoughts

Cloud concerns – tie-in

One of the major attractions of the Cloud for vendors is that it ties in customers, providing a reasonably consistent revenue stream. It is an effective anti-competitive strategy. There are various technical and other methods that can be used to ensure that it’s difficult or even impossible for customers to jump ship. While that’s all very nice for vendors, it’s not such a wonderful thing for customers.

Let’s say you’re a CAD Manager who persuades your company to use a great new SaaS service and Cloud storage. Let’s assume it performs well, is secure, has 100% uptime and offers functionality that is not available with standalone software. Your company is pleased with all this and uses it increasingly over several years, eventually moving completely into the Cloud. A good news story, right?

Well, maybe. There are a few things that could go wrong. Very wrong. Wrong enough to get you fired. Most of these things have multiple precedents, some of them quite recent. They are realistic concerns and it’s not really plausible for anyone with any knowledge of the past to argue that they won’t happen in the future. I have grouped these concerns into five categories:

  1. Impermanence. The vendor stops providing the service. There are many possible reasons for this happening. Computing is full of product failures and withdrawals. Autodesk alone has such a long history of dead products and orphaned customers, that it would be a major undertaking just to document them all. If the product’s not making money, it’s unlikely to have a future. The vendor itself could go down the tubes. Computing history is littered with the corpses of once-dominant companies. Because there is a chain of dependencies in a typical Cloud solution, there are several potential points of corporate failure. Maybe Autodesk doesn’t go down, but Amazon does, or Citrix. One day, your software just isn’t there any more. What now?
  2. Price ramping. Once you and enough of your fellow customers are tied in, there is nothing to prevent the vendor from racking up the prices. Autodesk has already done this kind of thing with upgrade pricing and Subscription, so it’s not as if it’s an unlikely scenario. If the boil-a-frog-slowly approach is used and you’re the frog being boiled, you’re better off not being tied down when you decide it’s time to get out of the water.
  3. Unwelcome terms and conditions. The terms and conditions under which you operate are often in the Cloud themselves and can be changed by the vendor without you having any say in the matter. What if one day your company lawyer spots a clause has been added that is totally outrageous (even more than normal, I mean) and there is no way your company can possibly continue to operate under those conditions? Good luck trying to negotiate your way out of that one from a position of weakness.
  4. Unwelcome technical changes. I intend to cover the issue of as-you-go upgrades more fully later, but let’s say the vendor introduces a new feature that seriously impacts your ability to use the software productively. No off switch is provided. Sound familiar? It happens to standalone software. It will happen to your SaaS choice, too.
  5. Ignoreware. Your once-fashionable product stops being The New Black. The vendor decides to concentrate its resources in other areas to attract new customers rather than the ones it has already tied up. While your SaaS product continues to be provided, it is put into maintenance mode and nothing useful is added to it. As the rest of the computing world moves on, your SaaS product does not. Holes start to appear that make your life difficult or impossible. Again, Autodesk history is replete with examples of this kind of thing.

If you’re using standalone software and any of the above occurs, it’s probably a pretty big deal, but you can work around it in the short term by simply continuing to use the product that works. You can keep doing this into the medium term, perhaps for several years. Sure, if Autodesk goes down you’ll find that you can no longer authorise new installations or transfer software from one computer to another. But you’ll have some breathing space. You’ll still have all your data, bang up to date. You’ll be able to continue working productively while you look around for an alternative.

If you’ve deeply committed your company to a Cloud solution and the SaaS hits the fan, it’s more than a big deal. It’s a disaster. It could kill your company. It could kill your career. As a computer once asked me, “Do you really want to do this?”

(so (long (and (thanks (for (all (the (parentheses))))))))

A few days ago, John McCarthy died at the age of 84. He didn’t make a fortune selling gadgets, he just profoundly affected the world of computing. He will be remembered mainly as the father of LISP, without which it is quite possible that AutoCAD and Autodesk would not have survived beyond the 80s. However, his original thinking went well beyond the development of a language. For example, 50 years ago he came up with an idea that is very relevant to what we are actively discussing today:

In 1961, he was the first to publicly suggest (in a speech given to celebrate MIT’s centennial) that computer time-sharing technology might lead to a future in which computing power and even specific applications could be sold through the utility business model (like water or electricity). This idea of a computer or information utility was very popular in the late 1960s, but faded by the mid-1990s. However, since 2000, the idea has resurfaced in new forms (see application service provider, grid computing, and cloud computing.)

(Credit: Wikipedia)

Back to LISP, I still use John’s antique language today. It’s still the best language choice for the vast majority of the development I do. Thanks, John.

“The Cloud is Dead” is not what I said

I guess most of this blog’s readers also read WorldCAD Access and upFront.eZine, so it probably hasn’t escaped your notice that in the latest upFront.eZine, Ralph had procalimed “The Cloud is Dead” and referred to some of my recent posts here as supporting evidence. I’d just like to point out that it’s Ralph announcing the death of the Cloud, and not me. Personally, while I agree with some of Ralph’s points, I think there’s life in the Cloud yet and the obituary is somewhat premature.

My own attitude toward the cloud matches that of most of you, judging by the poll results here. I see pros and cons, and have strong concerns about many of the cons. However, I intend to cover both sides objectively. Look out for more coverage soon.

Autodesk Cloud – don’t panic, business as usual

Autodesk recently made a big announcement about its Cloud initiatives, and reactions have been all over the place. Some people can barely contain their breathless excitement while others are outraged to the point of passing out the pitchforks. Why? It’s pretty much business as usual.

It’s nothing like Dassault’s disastrous we’re-moving-you-to-the-Cloud FUD campaign against its own product, SolidWorks. There’s no hint here of AutoCAD (real AutoCAD, I mean, not “AutoCAD” WS) being moved to the Cloud, or anything as radical as that. (Yes, I know there’s a limited experiment along those lines but that’s nothing to do with this announcement). It’s just a collection of relatively minor changes to Autodesk’s existing on-line services, collected together to make a newsworthy press release.

(As an aside, I must say this was a much more worthwhile announcement than the ridiculously over-hyped DE8.16N thing. So I was supposed to get excited about a routine upgrade of a product I have already been using for months, on an OS I don’t use, when the upgraded product is still half-baked just like the first underwhelming effort? Fortunately, I didn’t get sucked in by the pre-announcement build-up so I wasn’t disappointed, just amused when the truth was revealed. Autodesk PR, please don’t cry wolf so often; keep the hype in reserve for the hypeworthy stuff.)

Back to the Cloud thing, and putting aside hype and horror, here’s the stuff that has just happened:

  • Autodesk Cloud documents lets anybody store up to 1 GB documents on-line, or 3 GB if you’re a Subscription customer. This isn’t new, but until recently it was an Autodesk Labs project called Nitrous. The infrastructure is provided via Amazon and Citrix.
  • AutoCAD WS has been updated to integrate its storage with Autodesk Cloud documents. Remember, WS isn’t anything like real AutoCAD, but rather a limited on-line DWG editing tool. There’s a WS iPhone app, but that’s not new.
  • There’s an Autodesk Design Review iPhone app for reviewing DWF files you’ve stored in Autodesk Cloud. It won’t do DWG; use WS for that.
  • There are several cloud-based services that are available “free” to Subscription-paying users of a small subset of Autodesk software, mostly Revit and Inventor-based suites. They are: 
    • Inventor Optimization
    • Cloud Rendering
    • Green Building Studio
    • Conceptual Energy Analysis
    • Buzzsaw (now bundled with Vault Subscription)

    AutoCAD users need not apply for any of these services.

So some of Autodesk’s on-line services are now being provided only to Subscription customers, and one is offered in improved form for Subscription customers. There are two obvious reasons for this: tie-in and revenue.

First, Autodesk wants its customers tied to the Subscription gravy train, if you’ll excuse a fairly awful mix of metaphors. Offering Subscription benefits like this is preferable to some of the much less pleasant arm-twisting that has been happening recently (e.g. trebling upgrade prices). Is it too much to hope that Autodesk has learned that offering carrots to its customers is a better strategy than threatening them with sticks?

Second, Autodesk needs to start making money out of this stuff somehow. For some years, it has spent several fortunes on buying and developing on-line services and then given them away for nothing, usually as Labs projects. This obviously can’t go on for ever, but just slapping a charge on these services wasn’t going to fly. Bundling Cloud services up with Subscription is a way of easing people into paying for them, and this is something I expect to be expanded in future, for example with AutoCAD WS. Once that’s been established for a few years, it wouldn’t surprise me to then see Subscription for at least some of the services split off, so you’re paying for Cloud services explicitly. By then, enough customers may consider them to be worth paying for and they may therefore survive beyond the short term.

Will it work? I’m not sure. Time will tell which of these services will thrive and which will die, and such uncertainty is one of the many reasons real-world customers aren’t excited about getting their heads in the Cloud. I don’t intend to make use of these services (I’m not even allowed to), so I’m not too bothered what happens to them. Like the vast majority of Autodesk customers, I will just carry on using conventional software in that old-fashioned 20th century way that just happens to work very well. Autodesk will go on providing its software in that way, because that’s what most customers will want for at least a while yet, and Autodesk can’t survive on wisps of Cloudy revenue.

Move along, people, nothing to see here.

Will Autodesk have to explain itself to the SEC?

The observant among you may have noticed that for many years, Autodesk’s free patches, service packs and updates haven’t added any new functionality. Bugs may get fixed, severe performance issues may be addressed, but design errors generally have to wait for the next release (at the earliest), and new features definitely don’t get added.

The last time new functionality was added to AutoCAD in a free maintenance release was Release 13’s c4 update which shipped on 12 February 1996. (There was a public beta available some months earlier; I picked up a copy at Autodesk University 1995). That free update contained not only a host of bug fixes, but also more useful new features than some later full-price upgrades (e.g. AutoCAD 2000i). In an outbreak of outstanding customer service, a c4 CD was shipped free to all registered users. Maybe Autodesk was trying to recover from disastrously shipping Release 13 prematurely, but issuing such a comprehensive update free of charge was still highly commendable.

Why did Autodesk stop providing new functionality in free updates? While it involves more work for Autodesk and hardly encourages paid upgrades or Subscription, the reason we’ve been given over the years is that there are accounting regulations that prevent Autodesk from providing new functionality in free updates. This does not apply to benefits from paid Subscription, and various new features for Subscription users have indeed appeared (albeit in fits and starts) over the intervening years.

I have to admit that I have always thought that this accounting thing was a pretty unlikely-sounding excuse for Autodesk’s inactivity. This attitude was reinforced by a lack of Autodesk response to my requests for further information about the alleged regulations. Until recently, I didn’t care enough about this matter to bother finding out for myself, but something extraordinary just happened that piqued my curiosity.

What happened? Autodesk released a free Service Pack that included new functionality for the first time in over 15 years. I was particularly interested in this, because part of what’s new is a new command providing a subset of the functionality of my ClassicArray™ plug-in. When I put in the time and effort to develop this product to fill a hole of Autodesk’s making, I did so on the assumption that Autodesk wasn’t going to provide an Array dialog box until at least AutoCAD 2013. It turns out that this assumption was wrong.

So what’s all this about accounting regulations preventing new functionality being provided free between releases? Was I right to be vaguely cynical about that? After some research, it would appear that I was wrong about that, too. There is an FASB (responsible to the SEC) accounting standard called SOP 97-2, which covers software revenue recognition. I’m no accountant and the regulations are large and complex, but here is my layman’s understanding of the basics.

In a simple case where a vendor (e.g. Autodesk) sells a complete product (e.g. AutoCAD 2012) at a given date, it records and declares the revenue for that product in the appropriate period as a single unit of accounting. If there are multiple elements of the product, things get more complex. If Autodesk ships part of AutoCAD 2012 (the main product) at one time and part (e.g. a Service Pack with new functionality) at another, then it is required to separate the elements into multiple units of accounting. It is required to make available vendor-specific objective evidence (VSOE) for each element of the product. If Autodesk has not done so (which seems likely), there is probably a problem. My understanding is that without VSOE, Autodesk is required to allocate the revenue for AutoCAD 2012 sales not at the point when it was received, but when all the elements have been delivered (i.e. when SP1 was released).

What about an argument that the new ARRAYCLASSIC command and new SNAPGRIDLEGACY system variable are not new functionality in themselves, but merely mechanisms to restore functionality that was available in previous releases? I don’t think that matters. The functionality is new to those customers who purchased AutoCAD 2012 and thereby provided Autodesk with revenue between March and September 2011. If that revenue has been allocated incorrectly, then Autodesk has some revenue shuffling and explaining to do.

I repeat that I’m not an accountant and this is all a layman’s uninformed opinion. It is quite possible that the regulations have recently changed, or that a relaxed interpretation is now permissible, or that I have the wrong end of the stick entirely. I’ve admitted being wrong in this post twice already and it could well be thrice.

If I’m wrong and Autodesk is in the clear, that’s great. Why? Because it means Autodesk customers can look forward to a lot more functionality being provided in future service packs.

AutoCAD for Mac – what’s missing?

According to Autodesk, the forthcoming OS X version of AutoCAD has “many of the powerful AutoCAD features and functionality.” So what doesn’t it have? What are the holes? Autodesk hasn’t bothered to let me know a single thing about this software, so I guess I’ll just indulge in some irresponsible and uninformed speculation, based on what I can glean from marketing materials and various better-informed sources. I could have just asked, but who knows if I would have ever got any real answers? Besides, this way is more fun.

First, here’s a quick list of some things that don’t appear to be missing, but which might have been lost in translation:

  • Command line (in fact, the Mac one appears to be better than the Windows one).
  • Xrefs.
  • 3D, including visual styles and rendering.
  • Some kind of Quick View Layouts and/or Drawings feature.
  • Navcube.
  • Constraints.
  • Dynamic Input.
  • Selection highlighting.
  • LISP (at least some form of it).

Now for speculation on things that are possibly missing or not fully functional (based largely on screenshots, which is not a reliable indicator):

  • I don’t see a Communications Center, but I do see an Online Contact pull-down. Maybe that gives access to the same functionality, maybe it doesn’t.
  • Navbar.
  • Coordinate display in status bar.
  • Layout tabs (there’s a control instead)
  • The layer palette, in its docked form as shown in screenshots, looks very cut-down and would be tricky to use productively in complex drawings. It’s not clear if the old layer dialogue box is supported, but it needs to be.
  • Action Recorder? As this is a “brochure feature”, it’s no great loss if it’s absent.
  • Visual LISP? It’s not mentioned, so maybe it’s missing, or lacking the ActiveX bits. That would be a big problem for many organisations. Edit: I have since seen it confirmed that the Visual LISP environment is missing, as are the COM APIs.
  • Other APIs? DCL? ActiveARX? Deelip’s developing stuff using something, but the blurb just mentions a “flexible development platform” without giving any indication of what that means. Which leads to…
  • Add-ons, large and small. Many of us use various third-party utilities for making our AutoCAD lives more productive. Will they work? Probably not. Can the developer make them work? Maybe. But only if they want to, and feel the need to make the investments required. For small developers, that may not be the case.
  • Will your tablet, image and screen menus work in this environment? I don’t know, but here’s a guess: no.
  • Profiles? I couldn’t possibly work without being able to store and switch between profiles.
  • Object enablers. Has it got a full set? Or any at all? Dunno, but Autodesk’s object support for DWGs from its own AutoCAD verticals has been patchy, even on Windows.
  • Performance. Has it got any? Dunno.
  • Reliability. Has it got any? Dunno.
  • Longevity. Has it got any? Dunno. I think we can confidently expect an AutoCAD for Mac 2012, and probably 2013 too. Beyond that, it’s anyone’s guess. Maybe I should run a book on it?

Finally, things that do appear to missing:

  • Ribbon, QAT and The Big Red A. What, no Next Big Thing in UI Design, embraced wholeheartedly by Autodesk from AutoCAD 2009 onwards and still spreading out to the outer reaches of the product range? How will Mac users be able to live with the terrible loss of productivity when compared with their Windows-using colleagues?
  • CUI. There is a screenshot of a very cut-down interface customisation thing, but it’s not the CUI interface you’ve grown to love. Seriously, it looks extremely limited.
  • Express Tools. Last time Autodesk tried to sell an AutoCAD without these was 2000i. Remember that? Maybe not, because the i apparently stood for ignore and upgraders avoided it in droves.
  • AutoCAD verticals. Civil 3D for Mac, anyone? Mechanical? Architecture? Not yet. Verticals, if they ever arrive, are likely to be years away.
  • Network licensing. All of your Macs will need individial licenses.

It will be amusing to see how the various omissions are spun or glossed over. My guess is that they will be ignored altogether, or some vague indication being given to them being investigated for possible inclusion in a future release. But maybe you can think of more interesting ways of handling it. How about something like this for the missing Ribbon?

Mac, Windows. Chalk, Cheese. Ribbon, no Ribbon. Oil, Water. Creative, Productive. Cat, Dog. Trendy, Nerdy. Choose one. Be whatever you want to be. Because with AutoCAD®, it’s your choice™.

Have a go with your own Spin Segment. Who knows? Autodesk may even use your ideas.

Why we keep upgrading

In a comment in response to a Deelip post yesterday, Brad Holtz pointed to an article he wrote in 1999. It’s interesting to note that while much of the computing world today bears little resemblance to the scene at the end of the last century, this article remains almost completely accurate and relevant. Indeed, it’s so right that you might even be tempted to think, “Duh, isn’t that obvious?”

One section that stood out to me had this to say:

Many software systems never even get beyond the acceptable stage …. vendors of these systems are continually coming out with new versions, never stopping long enough to fix the problems with the existing systems.

It’s fascinating to me that this observation came at the very time that Autodesk was switching from a company that wasn’t exactly like that to one that very much was (and still is today), thanks to the 12-month release cycle.

Studying Autodesk’s productivity study

Heidi Hewett just reported the following on her blog, about a productivity study:

According to a recent independent study, AutoCAD® 2011 can help you work up to 44% faster with the latest productivity enhancements.

I have a couple of problems with that sentence. First, it’s not an independent study. It’s a study conducted by long-time respected CAD figure David Cohn, but it was specified and paid for by Autodesk:

This productivity study was performed at the request of Autodesk Inc., which funded this work.

That’s not exactly independent then, is it? Second, the study does not state that AutoCAD 2011 is responsible for a 44% improvement. That’s a figure that combines both the effects of AutoCAD 2011 (over AutoCAD 2008), plus the effects of using a newer, faster PC. Just stating that figure wthout such a disclaimer is misleading.

Now to the study itself. Let me make it clear that I have no problem with David Cohn, who is respected, experienced and honest. I do not doubt that his study accurately describes his observations of the time taken to perform the chosen operations on the chosen drawings. The problem is that the study is designed to concentrate purely on a set of AutoCAD operations that benefit from the changes of the last three releases. In other words, the dice are very heavily loaded. To David’s credit, he states that very clearly in the study report:

Each drawing was chosen based on a number of criteria designed to showcase one or more features of the software that did not exist in AutoCAD 2008 but were added in subsequent releases. While each drawing could certainly be produced using the features and functions available in AutoCAD 2008, the advanced capabilities added in subsequent releases would likely enable a typical user to produce the drawing faster using AutoCAD 2011.

Since the premise of the test was to determine how much time could be saved by using a new feature, the test itself was already predisposed to show that using AutoCAD 2011 is more productive than using AutoCAD 2008.

A quick skim-read shows that there are several other problems with the study. For example, it doesn’t attempt to measure the productivity of those operations that are common to both releases, which are much more likely to be used in bulk by typical users. The report states that the Ribbon interface is likely to be more productive, but makes no attempt to justify that by comparing the exact same operations performed using the two interfaces.

In addition, both AutoCAD 2008 and 2011 are measured on a typical middle-age PC using XP, but only 2011 is measured on a modern PC running Windows 7. The report states that the latter tests were performed after the former tests, so the times will also be biased by familiarity with AutoCAD 2011, the drawings and the operations required. That’s where the 44% figure comes from, and it doesn’t mean anything.

What’s the point of studies like this, that are self-evidently designed to produce a good-looking outcome? Who are they supposed to fool?  Come on Autodesk, either do these things properly or don’t do them at all. Please.

Censorship on the Autodesk discussion groups

The Autodesk discussion groups have quite a few problems at the moment, which I will discuss at length in future. One unnecessary problem that has been added to the mix is censorship. Having praised Autodesk in the past for allowing discussion to go unhindered, it’s only fair to slam heavy-handed moderation when I see it.

Before I get started, let me just say that Autodesk is entitled to moderate its discussion groups as it sees fit. The forum belongs to Autodesk and it can do what it likes with it. But just because Autodesk can censor its forums, that doesn’t mean it’s always a good idea to do so. Neither does that it mean that Autodesk is immune to public criticism of that censorship. There is no First Amendment obligation on Autodesk, but there are many other places that censored viewpoints can be repeated. Here, for example.

In this particular case, a section was deleted from a reply I made in a thread about the educational plot stamp. In that section, I mentioned that the educational plot stamp is very easy to remove with an everyday AutoCAD command. I didn’t name that command or give any details of how to use it to remove the stamp.

Now I understand that Autodesk gets the twitches when people discuss circumvention of its educational stamp “virus”, but I didn’t mention anything that isn’t already public knowledge. I discussed this issue at length in Cadalyst some five years ago, again without giving away the details. If you really want to know the details, please don’t ask me because I won’t reply. Google it, it’s out there. You probably don’t even need to do that. It’s a pretty obvious thing to attempt. It was, in fact, the very first thing I tried when I first saw an example of an infected file. It worked perfectly.

Back to the censorship. My post was edited, and I wasn’t happy. I wasn’t contacted about it, so it was not possible to have a reasoned discussion about it with the moderator (as I have done in the past on the AUGI forums and elsewhere). Annoyed, I made a further post, this one objecting to the censorship. In that post, among other things, I pointed out that the Autodesk position on the plot stamp was fictional. Here is what the Autodesk knowledge base item TS63668 (which I can no longer find) had to say on the subject:

Issue
When you plot a drawing that was created in or that contains drawing data that was created in the Educational (Student and Faculty) version of AutoCAD® or AutoCAD-based software, the following plot stamp or watermark appears in the plot:

For Educational Use Only

Solution

There is no way to circumvent the plot stamp. This is as designed to discourage the commercial use of an educational version of an AutoCAD product. Autodesk sells educational versions of software on the premise that the software will be used for educational purposes only.

The statement above in italics is a blatant lie. Hopefully, the knowledge base item is now missing because somebody sensible at Autodesk decided that it’s not a good look to have such fraudulent nonsense on its site, dishonestly masquerading as technical support. Or maybe it’s not missing but I can’t find it because the search engine is bad. After all, Autodesk really, really sucks at search. Perhaps it should buy a search engine company?

I digress; back to the censorship issue again. My post objecting to the first censorship was deleted. I was not contacted to discuss this deletion. I made another post objecting to the second censorship of my objection to the first censorship. This post made no reference whatsoever to the plot stamp issue itself. This post was deleted, too. In a surprise development, I was not contacted to discuss this deletion. Three levels of censorship to cover up an Autodesk lie. I can’t see a problem with that, can you? Except for this:

The Internet interprets censorship as damage and routes around it. — John Gilmore

Discussion_Admin, you were entirely within your rights to perform this censorship. Your moderation guidelines may even require it. But as a result, my statement about the plot stamp being easily removed has been read by a much larger number of people. So it really wasn’t such a good idea to censor it, was it?

Readers, if you have your own Autodesk censorship tales to tell, feel free to tell them here. It should be a fun read.

Does Autodesk discuss future plans?

According to Shaan, Autodesk does not discuss its future plans. Or does it? In a comment, Ralph reckoned it does. Putting aside technology previews and various NDA-bound circumstances (e.g. Beta testing), can you think of cases where Autodesk has revealed what it intends to do in future? Here are a few off the top of my head:

  • I’ve been to AU sessions dating back to 1995 that pretty much give away the contents of the next release of AutoCAD, using a vague cover-my-butt session title and a disclaimer at the start of the session. I understand that these days, attendees need to sign an NDA before entering such sessions.
  • Last year in San Francisco, an international blogger audience was given all sorts of information about Autodesk’s future directions (preceded by a similar disclaimer), with no NDA and nothing off the record. I assume something similar happened at this year’s North American bloggers’ event.
  • The Subscription (Advantage) Packs of the last couple of years have been a dead giveaway about some of the features that are going to make their way into the next release.
  • The new 50%-cost upgrade policy was announced a year in advance.
  • Surveys and other customer feedback mechanisms provide a very big clue about what Autodesk is looking at changing next. Some of these are covered by NDA, others are not.
  • In the specific case that triggered this discussion, Autodesk has been gradually building up expectation of a Mac AutoCAD for quite a while. Yes, it required a little reading Between the Lines, but for some time it has been pretty obvious where all the Mac love was leading to.

Feel free to add your own examples, but it seems to me that Autodesk is perfectly happy to reveal future plans as and when it sees fit. And that’s fine. In each of the above cases, the revelations have been A Good Thing. Good for Autodesk, good for customers.

Maybe the question should be, “Why doesn’t Autodesk discuss future plans much more often?” Stock market regulations, perhaps? But hang on, there are some very major publicly traded corporations that seem to get away with revealing all sorts of things about their future products. For example, Microsoft regularly conducts very widespread public Beta programs that let people know in great detail what’s very likely to appear in the next release, and seems to have survived the experience so far. There’s surely no reason why Autodesk couldn’t do the same if it wanted to.

Ultimately, it comes down to a desire for secrecy; a culture of concealment and control. Of course Autodesk may have legitimate reasons for keeping some of its plans from its competitors, but the culture can be so pervasive as to cause some bizarre side effects. You may find this difficult to comprehend, but there are those in Autodesk who got into a tizzy about me speculating in my launch announcement that Autodesk’s general design product (AutoCAD 2010) was going to be followed by something called AutoCAD 2011. There was something of a surreal drama behind the scenes. There were apparently people within Autodesk who genuinely thought I needed privileged information to work out that 10+1=11. No, I’m not making this up.

I’m not sure Autodesk’s secrecy is doing any good for anyone. It’s surely harder to maintain these days and it’s only going to get harder. I suspect several Autodesk blood vessels were burst when AutoCAD Mac Beta 1 was leaked. On the one hand, I can understand that; somebody broke an NDA, a legitimate agreement was freely entered into and then broken. Some people at Autodesk probably had their carefully planned marketing timelines disrupted.

On the other hand, this provided a whole heap of free and largely positive publicity. Potential AutoCAD for Mac users are now hovering in anticipation, filling the Mac forums, spreading the good news among themselves, putting off the purchase of competitive products, considering entering the official Beta program, and so on. At the same time, the news of performance issues in the early Beta is helping to put a dampener on expectations in that area. Lowered customer expectations may turn out to be very useful when the product is actually released. All considered, a good thing for Autodesk, then.

I’m convinced that Autodesk is opening up. That’s great, but there’s a way to go yet.

The Machine that Won the War

I just wanted to get on the record that I don’t trust claims based on statistical data without being able to review in detail the methods used to obtain and interpret the data. Even with the best intentions, full integrity and honesty, it is not difficult to come to completely the wrong conclusions based on apparently compelling statistical evidence.

This isn’t just theory, I’ve seen it happen. Detailed percentages presented at upper governmental levels, based on huge sample sets, giving a totally false impression because of errors and assumptions that occur at various places in the process. The exact same question asked twice in the same survey, giving very different results depending on the section in which the question appeared, providing an unstated context to the question. The devil is in the details, and the details can be extremely subtle.

I have a “put up or shut up” rule that applies to anybody who makes claims based on unrevealed statistical evidence. It applies to corporations, news outlets, bloggers, government ministers, everybody. Without allowing scrutiny of the full details, all statistical claims are null and void, as far as I’m concerned. “Trust me” doesn’t cut it. Sorry, no exceptions.

What does this have to do with the title? Those familiar with Isaac Asimov’s short story of that name will understand. I’m sure Robin Capper worked it out immediately.

Autodesk’s CIP data – massively biased?

You may have seen Shaan Hurley and I having a discussion (ahem) over the validity of his statement:

I really do use the ribbon now with AutoCAD 2010 along with most users as evidenced by the CIP data we receive daily from thousands of AutoCAD users who choose to send the great data.

So, now you know. Most of you use the Ribbon now,  Shaan said so. Shaan, as he always has done in the past, declined my invitation to back up this assertion with more details. He has vast amounts of data collected from huge numbers of users. How could that possibly be wrong?

Here’s how. CIP data is biased.

How can millions of data points be biased? Actually, all samples are biased. Only the degree of bias varies. The polls on this blog are no exception. I do my best to keep the questions and options neutral; the only leading questions you’ll see here in serious polls are the ones I copy and paste from Autodesk blogs. But readers of this blog are one self-selecting small portion of Autodesk customers, and people who vote in my polls represent another self-selecting portion of that portion.

The question is, how biased is Autodesk’s CIP data? Without access to Autodesk’s data (which it won’t provide) and resources for alternative data collection from its customers (ditto), the best I can do is use my own biased sample (that’s you lot out there) as a cross-check.

Let’s examine it in light of Ribbon use among AutoCAD 2010 users. In an earlier comparison of my 2009 poll figures and Shaan’s CIP data, I wrote this:

But Shaan’s CIP users are also a biased sample, comprising those AutoCAD users who have CIP turned on. Are users who go with the flow and have CIP on also more likely to go with the flow and leave the Ribbon on? Possibly, but I would have thought the CIP-on bias would be less significant than the blog-reader bias.

I have recently run a poll to try to determine if that “possibly”, that hunch, has any basis. Let’s examine the results I got.

AutoCAD 2010 users, what are your Ribbon and CIP settings?

Ribbon on, CIP on (24.7%, 65 Votes)
Ribbon on, CIP off (19.4%, 51 Votes)
Ribbon off, CIP on (11%, 29 Votes)
Ribbon off, CIP off (44.9%, 118 Votes)

Total Voters: 263

For the sake of argument, let’s make the assumption that my poll sample is unbiased. It’s not, and the degree of bias is unknown, but let’s see what it would mean if it was. Let’s see what kind of results Autodesk would see from its CIP sample:

CIP-on voters (94):
Ribbon on 69% (65)
Ribbon off 31% (29)

Shaan would see from this result that 69% of AutoCAD 2010 users have the Ribbon on, and would be tempted to say stuff like “use the ribbon now with AutoCAD 2010 along with most users”. Understandable. That’s just CIP users, but non-CIP users can’t be that different, surely? Or can they?

CIP-off voters (169):
Ribbon on 30% (51)
Ribbon off 70% (118)

Wow. That’s a huge discrepancy, and it implies that a sample selection based on CIP use introduces a massive bias. I’ve watched this poll grow over the weeks, half-expecting things to even out as the sample size increased. It didn’t. It has been pretty constant, with non-Ribbon non-CIP users outnumbering Ribbonite non-CIP users by a substantial margin.

Let’s put the groups together, shall we?

All voters (263)
Ribbon on 44% (116)
Ribbon off 56% (147)

So, if the voters in my poll were observed by Autodesk via CIP they would appear to be 69% Ribbon users. In fact, only 44% of these voters are Ribbon users.

How many AutoCAD 2010 users really have the Ribbon on? 69%? 30%? 44%? Some other number? I don’t know, and that’s not the point. The point is, Autodesk doesn’t know either. It can take some smart guesses, but just assuming CIP is accurate isn’t smart, it’s just a guess.

Why does this matter? Because Autodesk makes decisions based on this stuff. Decisions that affect you and me and how we use our tools. Have a look at this statement from Autodesk’s Teresa Anania, Director of Industry Management (taken from her interview with Deelip Menezes about Inventor):

…we had data that suggested that the new ribbon UI was well received and would be absolutely all that customers needed …. And now since we have the CIP data that shows us how our customers are using the software, we can analyze this before we permanently turn anything off.

Comments like this (and others from other Adeskers) seem to indicate that there is an unspoken assumption that CIP users accurately represent a true cross-section of users in general.

I know that Autodesk doesn’t rely solely on CIP; it uses a wide range of research tools to find out what users are up to and what they need. I regularly encourage you to participate in various Autodesk surveys, for example. But there are problems of accuracy inherent in all those methods. It would be natural, when faced with a set of apparently conflicting results from different sources, for Autodesk decision-makers to simply assume that the source with the biggest sample size is the most accurate. That could be a dangerous mistake, for both Autodesk and its customers.

Note: my arithmetic was off in several places when I posted this, and I have edited the post to correct some of the figures. These corrections do not invalidate the arguments; the substantial bias is still evident.

Not a topic to be debated publicly

Over on the oft-entertaining Deelip.com, there was an interesting comment made by Autodesk’s Scott Sheppard. After going back and forth a few times over Autodesk’s then-failure to allow Indian customers legal access to certain free Autodesk software downloads, Scott said this:

I defer to Autodesk Legal on these matters which is where I get my guidance. This is not a topic to be debated publicly. As one of our most active Labs participants, I was just sharing some information with you and your readers.

On the face of it, Scott’s “not a topic to be debated publicly” comment seems pretty silly. Ralph Grabowski certainly saw it that way. In these blog-happy days, a lot of things that Autodesk may not like to see discussed are going to be discussed publicly. Autodesk needs to get used to that fact. Attempting to suppress public discussion of Autodesk policies is not just ineffectual, it’s counterproductive and harmful to Autodesk’s image. The very fact that this problem was fixed as a direct result of being discussed publicly shows that such discussion was not only appropriate, it was positively useful to everyone concerned.

That’s on the face of it. Actually, I don’t think the comment is anywhere near as sinister as it seems. I think it was more of a throwaway comment along the lines of, “I can’t continue discussing this because it really isn’t my area”.

Recently, I have noticed Autodesk opening up somewhat and demonstrating increased responsiveness to publicly aired concerns. I know that Scott is quite open to constructively discussing points of disagreement in public comments on his own blog. So I think we should cut him a bit of slack and just put this down as one of those “it may be what I said but it’s not what I meant” moments that we all have from time to time.

It’s not easy being green (and believed)

I know that some of you out there (unlike me) are pretty cynical about anything that Autodesk says on any subject. So when Autodesk makes a big thing about being environmentally responsible, such as its new Autodesk Sustainable Design Center site, it would be tempting to say “Yeah, right” and assume it’s just more spin to ignore.

That would be wrong. Yes, Autodesk is using its green credentials as a marketing tool. No, that doesn’t mean it’s all bovine excrement. Autodesk is genuine about this stuff. It’s being driven from the top, and it’s being driven hard.

How do I know? In addition to Autodesk backing up its assertions with a reasonable level of detail and independent scrutiny, I have a little first-hand knowledge. When I was attending the AutoCAD 2010 launch bloggers’ event last year, I was able to chat casually with quite a few non-marketing people. During those conversations, Autodesk’s move towards green issues was mentioned by more than one person, and in unscripted ways. It was clear to me that Carl Bass was serious about this and was strongly pushing a green culture within the company.

Disclosure: when attending the AutoCAD 2010 launch in February 2009, Autodesk provided transport, accommodation and some meals. Yes, I am fully aware of the irony of learning about Autodesk’s green culture only because it flew me half way round the world and back again.

Some meaningless AutoCAD 2011 numbers

According to David Cohn, at yesterday’s blogger event in San Fransisco prior to the 2011 launch, Autodesk provided the following figures:

  • 76,000 man hours spent on Q/A of the new release
  • 6,000 total code reviews of new release
  • 2,000 commands tested
  • 4,600 Beta customers involved in AutoCAD 2011
  • 1.4M lines of old code were removed

Well, that’s all very nice, but those numbers are completely meaningless without context. Autodesk may as well have just published the equivalent numbers for Release 13; I’m sure they would have looked impressive in isolation.

Did anybody in the blogger audience ask the obvious question?

How do these numbers compare with previous releases?

If so, I’d be interested to see the answer.

If not, why not? I’d like to think that I would have asked such a question rather than sitting there unquestionably accepting whatever was being presented.

I’d like to think that, but I can’t. I’m in no position to throw stones. I had a similar opportunity at the equivalent event last year and failed to take advantage of it. I was operating at a very sub-optimal level for a variety of reasons (some of which were entirely of my own making, so no excuses there). It was a small, fairly informal event at which Autodesk actively and repeatedly encouraged two-way communication. But sitting there absorbing what I was told was pretty much all I did. I even caught myself on video doing this (i.e. very little), so I have absolutely no right to expect anything better from anyone else this year.

Still, it would have been nice to have had that question asked. It would be even nicer to have it answered. Otherwise, the numbers will remain meaningless.

Interesting times

The past few days haven’t been so great for me. Here’s what has happened lately:

  • A family member had an expensive musical instrument case burned when it was placed too close to a stage light.
  • As I was driving home on Monday to escape a major oncoming storm, my car was hit out of the blue by a single golf-ball size hailstone. This caused damage on a styling crease, which will be difficult to repair. As a single dent, it’s probably not worth getting fixed, and will therefore remain to irritate me every time I see it, until the car is sold.
  • Our lovely big Protea tree was blown over and uprooted, and the top half of our lovely flame tree was sheared off and dumped some distance away.
  • The trees took our overhead power cable with them as they died, leaving a live cable end on the wet ground. This was isolated but not fixed the next day, just before parents started dropping off their kids in our street (we live near a primary school). We were left without power for most of two days, during which we had no idea when the power would be restored, and which made meal planning a little tricky. This outage resulted in the spoilage of a fridge-freezer full of food, and left me unable to work from home or prepare some planned future blog posts.
  • My wife bashed her nose and eye this morning when a heavy washing machine lid fell on it. In addition to her own pain and suffering, this will probably come up in a lovely bruise and leave people wondering if I’m a spouse abuser, a form of life for which I have nothing but contempt.

All in all, not the best time of it. But I’m OK. I’m feeling pretty positive about things. There are lots of people in my area with destroyed homes, well-hammered or flooded cars and still no power supply. I still have a source of income, my health and that of my family. There are large numbers of people in the world without adequate shelter, food and clean water, let alone a convenient power supply that fails for a couple of days only once every few years. Many of them live a miserable and fragile life under oppressive regimes or other sources of potential or actual violence or injustice.

No, I reckon I still have things pretty good.

Celebrating Douglas Bader

As I am currently re-reading Reach for the Sky, I happen to know that yesterday was the 100th anniversary of the birth of Douglas Bader, a inspirational man who lost both legs (one above the knee) in an air crash while a trainee RAF pilot. A sporting hero and natural pilot, he used his immense self-will to overcome this setback and mount several other obstacles placed in his path.

Retired from the RAF as 100% disabled, he relearned how to walk on tin legs (never using a stick), drive a car (he needed the clutch pedal moved), play squash (with much falling, crashing and banging) and golf (to a very high standard). When World War II started, he used the force of his personality and his old contacts to overcome official resistance and become a pilot again. He was passed as 100% fit (while simultaneously being classed as 100% disabled) and took to Hurricanes and Spitfires alongside the mostly younger men who became The Few. He and his colleagues protected his nation from an unspeakable evil.

Following many airborne successes in the Battle of Britain and more crashes (one of which would have probably cost him his legs if they had not already been lost), he had a meteoric rise through the ranks. In 1941 Wing Commander Bader was either shot down by, or collided with, a German fighter over France. Unable to extricate himself from his plummeting tail-less aircraft, he only survived because the straps that were holding on his trapped leg broke free. Captured, taken to hospital and reunited with his leg (repaired by respectful German airmen), he escaped out of an upper-storey window on knotted sheets!

Although recaptured and deprived of his legs for a while, Bader made it his business to make life as difficult as possible for his captors. After several other escapes and attempts, he ended up in Colditz castle where he continued to make life difficult for the Germans until the inmates were freed by American forces in 1945. He immediately tried to get hold of a Spitfire to join in the ongoing fight, but was not allowed to do this. He did, however, get to lead the fly-past of 300 aircraft following the victory in Europe.

Douglas Bader continued to be an inspiration after the war, and was knighted for fighting on behalf of disabled people, often against the same kind of officialdom that he had to overcome in order to get back in the air. He was always especially supportive of disabled children, writing to one little boy who had lost his legs in an accident:

Don’t listen to anyone who tells you that you can’t do this or that. That’s nonsense. Make up your mind, you’ll never use crutches or a stick, then have a go at everything. Go to school, join in all the games you can. Go anywhere you want to. But never, never let them persuade you that things are too difficult or impossible.

The internal demons that drove Douglas Bader would have driven him to greatness with or without his legs. Not always a likeable man, often rude, always strident in his opinions (right or wrong), and holding some political views with which I would not agree, he nevertheless deserves great respect. At a time when Britain, and ultimately the whole free world, needed people of great strength and bravery, he was there. I am profoundly grateful to him and his colleagues for that, and to him personally for his example. If ever circumstances knock you down and you need inspiration to get back up again, look to Douglas Bader.

Comment censorship

I want your views on how much control I should exert over the comments that people make here. I’ve been led to thinking about this by a couple of things. Mostly by the occasion of the first troll comment on this blog, and to a lesser extent by Shaan Hurley turning off comments on posts older than three months on his Between The Lines blog. (I am not complaining about this; it’s Shaan’s justifiable reaction to mass spam attacks and it has nothing to do with censorship. There are some Autodesk blogs that don’t allow comments at all, which may in itself be justifiable).

I’m a proponent of freedom of speech and don’t want to restrict your ability to say what you think. I’m perfectly happy to see you express your contrary opinions and would never dream of removing or editing a comment simply because it contains viewpoints with which I disagree. There are plenty of comments on this blog from people who disagree with my stated views, and at least one containing an insult aimed at me personally using a variant of a word that many people would consider very offensive. I haven’t touched those comments. I haven’t even touched the troll comment.

Spam, on the other hand, is mercillesly dealt with. The vast majority of it is automatically excluded by Akismet, a handful I have to remove manually, but in all cases the comment is deleted and the sender’s IP is banned from accessing the site. I can do that with other commenters too, but I have not yet done so.

My question to you is where do you think I should draw the line? If a discussion leads to a vendor commenting to let people know that his company provides a service relevant to the discussion, is that spam or should I let it go? Should I remove deliberate trolling attempts? What about comments or words based on race or religion? If somebody drops an f-bomb or a c-bomb without attacking anybody, is that a problem for you? How about attacks on companies or individuals? If commenters start personally attacking each other, should I let it go? If somebody has a go at a company in a way that looks unhinged to some, is that OK? What if somebody else says it is loony bin material? What if that then leads to a flame war?

I’d like to draw up some moderation guidelines so everyone knows where they stand. I know I will have to make judgement calls wherever the line is drawn, but I’d appreciate it if you would give me an idea about your own preferences. I’ll consider adding a poll later if the discussion throws up a few options.

Open Letter to James Cameron

James, you don’t know me, but I see you have been getting involved in CAD events lately, which is my area of interest. Autodesk University 2009 attendees got a sneak preview of Avatar and you were a key speaker at Solidworks World 2010. I absolutely loved Avatar. It’s the only film I’ve ever seen where I immediately wanted to watch it again. Yes, it’s possible to poke holes in the plot, but that applies to 99% of films and anyway, this film isn’t about the plot, is it? It’s about the breathtaking visuals. I was dreaming about Pandora for days afterwards; good job.

I grew up in the 70s with the music of Yes and the artwork of Roger Dean. That the visuals of Pandora are based on Roger’s artwork is undeniable, and the film benefits immeasurably from the floating mountains, spectacular arches, dragons and even skin patterns that are so obviously lifted from Roger’s work. Why then, when I stayed to watch the credits at the end of the film, did I not see Roger Dean credited? I understand that Roger has received no monetary credit for his contributions, either.

James, you know the right thing to do. Please do it. Otherwise, instead of thinking of you as the guy behind the most visually impressive film ever, I’ll think of you as the jerk who ripped off Roger Dean. Over to you.