Category Archives: Thoughts

How will you react to Autodesk’s new upgrade pricing?

As I reported early last year, Autodesk is going to discourage you from paying for upgrades as and when you see fit. It is doing this by charging you 50% of the cost of a full license to upgrade from the previous release. The same 50% cost will apply if you crossgrade [edit: crossgrade from an non-current release, that is] (say if you move from AutoCAD to a vertical). If your product is more than three releases old, you can’t upgrade. This change takes effect from 16 March 2010. There were some discounted upgrade offers to get you signed over early, but these have now expired. If you are thinking of upgrading or crossgrading, I suggest you contact your reseller, get out your calculator and consider doing it in the next few weeks.

There is some laughable doublespeak in the Autodesk marketing of this change, such as “streamlining our upgrade pricing based on feedback from customers and resellers,” but I can’t imagine anyone being fooled by such nonsense. It’s obvious that Autodesk is not doing this because you all asked for upgrade prices to be trebled to make a nice predictable percentage, it’s doing this to force upgraders on to Subscription. Once you’re on Subscription, you’re paying a year in advance for an upgrade (bonus cashflow!), and you’re something of a captive market, theoretically providing Autodesk with a more regular source of income. (The financial crisis has knocked something of a dent in that theory, as many companies have chosen not to renew subscriptions for products that were previously used by now-retrenched employees).

If you’re already on Subscription, you may be feeling pretty smug right now. Don’t be. Once Autodesk’s user base is effectively converted to the Subscription model, Autodesk will be free to do all sorts of things to that user base. Things like jacking up Subscription prices, reducing or eliminating existing Subscription services, and slipping little clauses into the EULA so you’re “agreeing” that you will lose your license if you stop paying your annual fees. You may be able to think of other things that you won’t like but which will benefit Autodesk shareholders. Maybe not, because Autodesk is too nice to its customers? Maybe I’m just cynical? Then again, if a couple of years ago I had suggested that Autodesk would treble (sorry, “simplify”) upgrade prices, more than a few would have thought I was paranoid.

Autodesk’s various little Subscription carrots have had limited success among its customers, so now it’s time for the big stick. In effect, Autodesk is encouraging you to get on Subscription or get out. What to do? Jump off the upgrade/Subscription train altogether and stick with what you have? Upgrade once now and stick there indefinitely? Upgrade every 3 years? Buy a new license every 6 to 10 years? Hang on and hope Autodesk introduces an upgrade amnesty in a few years? Move over to one of Autodesk’s competitors? My guess is that a large majority of us are going to just do as we’re directed and get onto Subscription.

I’d like to hear from you. What are you going to do, and why? If you’re on Subscription already, are you concerned about what Autodesk might do in the future?

Disclosure: I manage several dozen Autodesk licences for a large organisation which has been on Subscription for quite a few years.

If you admire somebody, please let them know

This post has nothing to do with CAD or the other subjects I occasionally cover.

Last month, I unexpectedly lost two of my colleagues to cancer. Wayne was a loud, larger-than life character, full of life. Paal (pronounced like Paul) was a quieter, more reserved man, but very friendly, funny and positive. Wayne occasionally rubbed people up the wrong way with his robust manner, but everybody who knew Paal liked him. I thought he was a great guy, but I never told him that. Now I wish I had. I never even knew he was ill, so when I read the email telling me he was dead it was quite a shock.

It’s not my place to tell you what to do, so please take this purely as a suggestion. If you know somebody and you admire them for whatever reason, let them know it. They will feel better, you will feel better, and if you come in to work one day and find they are gone, you won’t be left wishing you had said something positive to them while you had the chance.

As for cancer, I can’t prevent or cure that, but I have a little idea for something I can do to help. More on that later.

Ralph Lauren – genuinely dumb or trying to be clever?

One of the blogs I read regularly is Photoshop Disasters, which recently posted a picture of a Ralph Lauren ad. In common with many fashion photos, this showed a skinny model that appeared to have been further skinnified on somebody’s computer to the point that the poor waif was ridiculously deformed. Like this:

LOL - Laugh On Lauren

Nothing out of the ordinary there, then. Under normal circumstances it would have received a few dozen comments and scrolled off the front page in a week or so, because there is no shortage of bad image manipulation out there for the blog to snigger at. The image was reposted at Boing Boing, but it would still have been forgotten in a week.

Except this time, Ralph Lauren prodded its lawyers into action and demanded the image be removed from both sites, issuing a DMCA notice. The DMCA request was spurious, as this is a clear case of fair use of an image for the purposes of criticism. Photoshop Disasters is hosted by Blogspot, which automatically complies with such requests. Boing Boing is not, and instead went on the offensive. They refused to take down the picture, instead reposting it with biting sarcasm. Read it, it’s funny. Ralph Lauren, if you’re reading this, please send me a DMCA notice too. I’m feeling left out.

This led to a flurry of comments, reposts and reports all over the Internet, including here. The comments (running at over a hundred an hour right now) are almost universally mocking of Ralph Lauren, its legal team, its models and its image manipulation propensities. The criticism goes way beyond the few snipes at a mangled-body image that would have been the case if Ralph Lauren had done nothing. It has moved on to the fashion designer’s ethical standards and those of the fashion industry as a whole for promoting artificially skinny bodies to eating-disorder-vulnerable people.

Now, is Ralph Lauren really that clueless and out of touch, to think that this kind of suppression would work? Or is this actually a deliberate marketing move, using the Streisand Effect to gain free publicity? Maybe, but it’s a deplorable attack on freedom of speech either way, and a boycott is fully justified. I’m not going to buy any of their stuff, ever, and I encourage you to do likewise. To be fair, I was unlikely to be a rich source of income. Even if I were a female with lots of excess money to throw away on clothes that look really awful, there is no way they would ever fit me. Or any living human, from the look of that photo.

Vernor wins (for now), customers don’t

Don’t get too excited, because I’m sure Autodesk will appeal, but as reported at Owen Wengerd’s CAD/Court, Vernor has won the right to resell his used copies of AutoCAD. While this is seen by some as a victory for customers, it isn’t. This doesn’t open up a brave new world in which we are allowed to sell the software we buy once we’re finished with it. If it had, I would be rejoicing as loud as anybody, because Autodesk’s ban on software transfers is an unconscionable restriction and deserves to die. But that’s not what this decision means. There are specific and paradoxical circumstances here, which allowed Vernor to win this case despite being morally wrong in my view, but will not benefit legitimate software users.

Vernor won (for now, and in one jurisdiction) because the court found he was not a party to the EULA. He didn’t read it, he didn’t click on anything to indicate his agreement to it, nothing. He just bought a bunch of books and discs and wanted to sell them on eBay. The fact that the item being sold is a remnant from software that had already been upgraded was not considered relevant. Neither was the fact that Autodesk is not obliged to provide the buyer of the discs with the codes they will need to make the software work.  The upshot is that this decision will allow a small number of people to buy and sell useless discs. What about the buyers of those discs who may not know they are useless until too late? Caveat emptor, I guess. Some other court can sort out that mess.

I agree with Ralph Grabowski that “software should be no different than any other consumer good: buy it, use it, resell it, or toss it”. I’d love to see Autodesk and other vendors forced to support a legitimate used software resale market (as they once did in pre-eBay days), but this decision won’t make that happen. It won’t help customers at all. If your firm has shrunk a bit and you have some spare licenses, you still can’t sell them because you are a party to the EULA (probably, although this area is still a bit fuzzy). But take heart! If you go bust, your creditors may be able to slip any discs left over from your upgrade history into a garage sale and hope that Mr. Vernor drops by. Mr. Vernor will be allowed to sell them, and the new buyers will be allowed to put them on their shelves and look at them.

Is that really a win for customers? I don’t think so.

Trusting Autodesk? Contemplating a new product

Last week, in my capacity as a de facto CAD manager for a large public utility company, I was having a chat with an Autodesk Australia person (he’s a nice guy and very honest, by the way). The topic of conversation moved to the new AutoCAD-based vertical, Plant 3D 2010. At that stage, I had not even installed the 30-day trial, but I still raised some of the issues that potentially stood in the way of the company adopting this apparently highly suitable product.

In a word, it comes down to trust. Each drawing used or issued by this utility is a legal document with a potentially very long life ahead of it. I showed the Autodesk person a drawing issued in 1901. The assets documented by that drawing are still in use today; indeed, many thousands of people daily depend heavily on them. Before we invest our money, time and training in Plant 3D, we need to know that the electronic drawings produced with it are going to be fully functional in the long term.

In terms of a new product like Plant 3D, can we trust Autodesk to do the following?

  1. Still be around and providing CAD software for many years?
  2. Go on supporting this new product for many years?
  3. In the event that the product is discontinued, provide an alternative, together with a migration path that retains full drawing intelligence?
  4. In the event that the product is discontinued, continue to provide ongoing support at least to the level of allowing the product to run and be transferred from one computer to another?
  5. Provide a product that works as well in real life as it does in demos?
  6. Provide a product that, from first release, works without crippling restrictions or bugs that render the product unusable?
  7. Include adequate support for national standards?
  8. Sell the product for a reasonable price on an ongoing basis?
  9. Provide Subscription for a reasonable price on an ongoing basis?
  10. Provide the product in such a way that we have flexibility in our use of network and standalone licensing long-term?
  11. Continue to allow the licensed use of earlier releases and use at home?
  12. Provide full API access to the custom objects, including ActiveX?
  13. Provide adequate object enablers for all recent AutoCAD releases and variants?
  14. Support the ongoing use of DWG files by other releases of this product freely up and down within a 3-release DWG version bracket?
  15. Provide full visual integrity, editability of proxy objects and round-tripping of intelligence, when saving to plain AutoCAD, including earlier releases?
  16. Provide mechanisms that allow any company-based custom work to be distributed easily to internal and external users and carried forward to new releases reliably?
  17. Avoid introducing problems and restrictions that would interfere with customisation and other aspects of CAD management?

Feel free to add to my list in your comments. If you go down the list giving a Yes, No or Maybe, how well does Autodesk do? Before looking at the product, I’ve got one Yes, a few Maybes and a very large number of Nos. That’s not based on paranoia or hatred, just on past history, including very recent history.

For example, can Autodesk be trusted to still be selling Plant 3D in a few years’ time? Ask the users of Autodesk FMDesktop. The same can be said of any of the other products in a long list of Autodesk abandonments that goes back to the dark ages. Generic CADD, anyone? What do I do with all my old Graphic Impact files?

Is it likely that Plant 3D will work properly in the real world in the first release or two? Ask the users of Civil 3D who tried to get any grading done for the first few releases. Very major and obvious problems in new products can go on for years before being addressed.

I’d be interested to hear how well you think Autodesk rates for new-product trustworthiness. There are other aspects to trusting Autodesk, and I will cover these in a future post. Please wait for that one before launching into any generic tirades; for now I just want to know about your level of Autodesk trust, purely in relation to new products and continued support for existing ones.

These messages are brought to you by AutoCAD

Over the past few releases, and particularly in AutoCAD 2009 and 2010, I have noticed an increase in the number of information notices (bubbles, warnings, task dialogs, Communication Center notices, etc.) being displayed. Shaan Hurley has pointed out that 2010 Update 1 introduces a balloon notification that periodically makes you aware of how much time remains before your subscription expires. Is this a good thing?

There’s a poll on the right that asks a specific question about the default state of AutoCAD 2009 and 2010, but I’d also like to see some comments on this. What do you think of these messages? Are they useful? Do they get in the way? Do you take any notice of them? Are there too many? Do we need any others? Do you turn them off? Is it easy enough to control them?

A touch of Tehran taints the AUGI Special Election

Most of you reading this blog are fortunate enough to live in democracies, and can only look on with sympathy at those who are denied the right to choose who represents them. What must it be like to live under regimes where the people are denied basic rights such as a free choice over who governs them? Or under mock-democratic regimes that hold “elections” where the candidates available from which to choose are strictly limited, or where the ruling regime changes the rules of the game to prevent losing its majority, or where the right to comment on the suitability of candidates is removed?

Well, I guess we AUGI members now have a slight inkling of what that is like.

OK, so that’s over the top. At AUGI, there are no riots in the street, no fires, no guns, no dead protesters. No election fraud, either, and I would hope there never is. An AUGI election is infinitely more trivial than what the Iranian people are struggling with. That said, there are clear failings at AUGI on the democratic side of things. These include:

  1. In recent years, the Board of Directors (BoD) using the Affirmation Ballot style of “election” to appoint itself as half of the BoD is replaced each year. In this method, the BoD selects the people it wants on the BoD and allows the members the formality of voting “Yes” or “No” for each candidate. This has been widely seen as preserving an “old boys’ club”, and was practiced right up to the point where it failed at the end of 2008. It failed because members’ interest in this “electoral” process had dwindled to the point where a few dozen disgruntled “No” voters were enough to ensure that none of the BoD’s choices were accepted (including some very worthy people who have given a lot to AUGI over the years).
  2. The BoD setting up the replacement election such that it reduces the number of Directors being elected from 4 to 2. This ensures that it is not possible for the members to elect enough Directors to make a difference to how the BoD is run. This was done, despite the fact that it ensures that it will be not possible to run an election at the end of 2009 that meets the requirements of the current bylaws.
  3. The BoD putting tight restrictions on who the members are allowed to vote for. At least 7 members put themselves forward as candidates for the 2 available seats, but only 4 were accepted. The 3 rejected candidates all met the minimum qualifications, and included former Presidents and a highly respected long-term AUGI volunteer who was considered worthy enough to put forward at the end of 2008. Two of the candidates were clearly being punished for expressing views contrary to that of the BoD, but the exclusion of one candidate in particular has everyone baffled. No explanation has been forthcoming to justify these exclusions.
  4. Introducing a special forum to allow members to ask questions of the candidates (which is good), but as part of that process, sneaking in a rule that forbids discussion of the candidates or their answers anywhere on the AUGI forums (which is very, very bad). See here, rule 6: “Discussion of specific candidates and their responses in other Forums is prohibited.”

There are other failings I could have mentioned, but the electoral censorship issue is what drove me over the edge. Having remained neutral for a long time (including defending the BoD on occasion), I reached the point where I felt that continuing to remain silent about these abuses would be an insult to the AUGI membership. Such a violation of the right to freedom of speech is not to be tolerated, particularly where it amounts to interference with the electoral process. I do not accept this rule, but as a good AUGI citizen I will abide by it within the AUGI forums. I will not, however, be abiding by it here, where the BoD has no censorship rights.

You can look forward to seeing lots more on this subject in the coming days leading up to the opening of the polls on 29 June. If you are an AUGI member, I encourage you to take an active interest in this and future elections. Please read the Organization Feedback forums, the Candidates’ Forums, and above all, vote!

The 12-month cycle and shipping software with known bugs

In a recent blog post, Deelip Menezes appears to be shocked by the very idea that a particular CAD company (no, not Autodesk) would ship software that contains known bugs. I thought he was joking, because he’s surely aware that practically all software companies with highly complex products release software with known bugs. As Deelip points out, those companies with 12-month cycles are particularly prone to doing this. There is no possible way any company can release something as complex as a CAD application within a fixed 12-month cycle without it containing dozens* of known bugs (because there isn’t time to fix them after discovery) and dozens* of unknown ones (because of insufficient Beta testing time).

Reading Deelip’s post and subsequent comments more carefully, it becomes clear that he doesn’t mean what a casual glance might lead you to believe he means. Deelip makes a specific distinction between “bugs” and “known issues”. He states that if a bug is discovered and the software is then adjusted such that it does not abort the software in a badly-behaved way, and this is then documented, then the bug ceases to be a bug and becomes a “known issue”.

I disagree. Bugs can cause crashes or not; they can cause “nice” crashes or not; they can be known about prior to release or not; they can be documented internally or not; they can be documented publicly or not. As far as I’m concerned, if the software doesn’t act “as designed” or “as intended”, then that’s a bug. Here’s what Wikipedia has to say, and I concur:

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program that prevents it from behaving as intended (e.g., producing an incorrect or unexpected result).

That doesn’t mean that software that is “as designed” (free of bugs) is free of defects. Defects are things that make the software work in a way other than “as it should”. They can be bugs, design errors or omissions, performance problems, user interface logic failures, API holes, feature changes or removals with unintended undesirable consequences, and so on. Unfortunately, defining “as it should” isn’t a precise science. You can’t just compare the software to the documentation and say that the differences are defects. The documentation could be faulty or incomplete, or it could perfectly describe the deeply flawed way in which the software works.

While I disagree with Deelip’s definition of bugs, I couldn’t agree more with a more important point he makes in his blog post. That point is of a fixed 12-month cycle being the root cause of a plethora of bugs/issues/whatever making it into shipping software, and this being an unacceptable situation. This is a view I expressed in Cadalyst before I started participating in Autodesk’s sadly defunct MyFeedback program, and it’s a view I hold even more strongly today.

In conclusion, I would have to say that the fixed yearly release schedule is not good for AutoCAD. It is good for Autodesk, certainly in the short term, but that’s not at all the same thing as being good for AutoCAD or its users.

I’m not alone in thinking this. The polls I’ve run on this subject, discussions with many individuals on-line and in person, and many comments here and elsewhere, indicate that a dislike of the 12-month cycle is the majority viewpoint. For example, when asked the question, “Do you think the 12-month release cycle is harming the quality of AutoCAD and its variants?”, 85% of poll respondents here answered “Definitely” or “Probably”. In another poll, 71% of respondents indicated a preference for AutoCAD release cycles of 24 months or greater.

Somebody please tell me I’m wrong here. Somebody tell me that I’ve misread things, that customers really think the 12-month cycle is great, and that it’s not actually harmful for the product. Anyone?

* Or hundreds. Or thousands.

AutoCAD for Linux – another bad idea

I often see calls for Autodesk to support AutoCAD on Linux. Just like AutoCAD for the Mac, while I can sympathise with the users of that OS, I think a native port of AutoCAD for Linux would be a bad idea. Again, I think it would be bad for everybody: Autodesk, AutoCAD for Windows users, and most of all, AutoCAD for Linux users.

Why? First of all, for most of the same reasons I gave for the Mac port. Autodesk hasn’t just failed in the past with AutoCAD for the Mac, it has failed with AutoCAD for Unix, too. I remember Autodesk being very enthusiastic about the Sparc port in particular (AIX, too). I know personally of customers who were caught up in that enthusiasm and invested heavily in a Unix environment, only to bitterly regret it a few years later when Autodesk abandoned them. Would this happen again? Probably.

Second, the numbers just don’t add up. Current PC OS market share is running something like this:

Windows 88%
Mac OS 10%
Linux 1%

While the Windows share is currently falling (thanks, Vista) and the others are steadily rising, there’s a long way to go before Linux has the numbers to make the investment worthwhile. In any case, it is likely that most Mac or Linux users of AutoCAD wouldn’t be new customers, simply existing users using a different OS. Not much of a cash cow, is it?

I dislike the Windows monopoly and support the open source movement, so I would love it if Autodesk could just snap its fingers and provide all its software on whatever platforms the users want. Mac? Sure. Linux? Great, why not? The reality is that it’s not that easy. It’s expensive to do and expensive to go on supporting in the long term. Unfortunately, it just doesn’t make commercial sense, and wishing it did will not make it so.

Why AutoCAD for Mac is a bad idea

There has been a fair bit of open discussion from Autodesk lately on the subject of a possible future OS X AutoCAD version. The more I think about this, the more I am inclined to believe that this would be a bad idea. A very bad idea.

It pains me to write this, because I’m very much a user advocate and I’m arguing here against something that some users have been requesting for a long time. If you’re one of those users, I’m sorry, but I think this is one of those cases when giving you what you want would be bad for everybody, and bad for you in particular.

Now, this sort of platform discussion often degenerates into a quasi-religious debate, so let’s see if I can head it off at the pass. If you’re a Mac fan who wants to tell me the benefits of your chosen computer family and how inferior Windows is, save it. I’ll concede right here and now that you are probably right. My experience of Apple products has generally been very positive. They look good, they’re well made, they work well, the Mac OS has been shamelessly copied by Microsoft for decades, and so on, ad nauseam. Yup. Not disputed. Also, not relevant to the point I’m about to make.

Ever since the last multi-platform AutoCAD (Release 13), Autodesk has dedicated its primary product solely to Windows. Since then, the code base has been spreading its mass of roots deeper and deeper into the Windows soil. Any Windows-specific advantage the developers can take has been taken. Reversing or working around that process is a very substantial undertaking. If it were done, I think it would have the following outcomes:

AutoCAD for Mac would suck

The performance is likely to be poor, because all the Windows-specific stuff will have to be redirected, recreated or emulated. The stability is likely to be awful, because this will be new ground for almost all of the developers involved. Developers with AutoCAD experience are going to have little or no Mac experience and vice-versa. They would be trying to make significant changes to the code base at the same time that that code base is being modified for the next release. The bug level is likely to be abysmal, both for the above reasons and also because the number of pre-release testers available to Autodesk on this platform is likely to be relatively tiny. The user interface is likely to be an uncomfortable square-peg-in-round-hole effort, which will work badly and be derided by OS X users.

AutoCAD for Mac would be half-baked

Not just half-baked in the usual let’s-put-this-out-as-is-and-maybe-we-can-fix-it-later way, but half-baked by design. The Autodesk survey implies that serious consideration is being put into a version of AutoCAD that is missing some of the things that make AutoCAD what it is. Things like paper/model space functionality, the command line, 3D, LISP, the ability to use third-party apps… AutoCAD for Mac LT Lite, anyone? If the APIs are not all there, that means no OS X version of any of the AutoCAD-based vertical products, either.

AutoCAD for Mac would be bad for Mac users

Last time this was attempted, it was a failure. The early 90s attempt at AutoCAD for Mac lasted for two three releases: 10 to 12. Autodesk had little option but to pull the pin on a non-viable product, but the orphaned users weren’t happy. Fortunately, there weren’t that many of them.

Would this happen again? Yes, I think it probably would. Any Mac user with any sense wouldn’t touch the first new Mac release with a bargepole. That, of course, makes it much less likely that there would be a second or third release. Autodesk’s corporate culture (espoused very strongly by Carol Bartz, but dating back to John Walker) encourages brave attempts that may lead to failure. This policy has unfortunately left large numbers of orphans in its wake over the years. In the event of poor sales, Mac for AutoCAD users would just be another set of unfortunates to add to a long list.

AutoCAD for Mac would be bad for Windows users

The very substantial effort required to produce any kind of AutoCAD for Mac at all would be a major drain on very limited (and shrinking) development resources. That means Windows users of AutoCAD would look forward to a release (or more likely several releases) with fewer new features, less completion of existing undercooked features, and longer waits until bugs and other problems get fixed. This, in exchange for no benefit whatsoever to those users. In fact, the decoupling of Windows-specific calls and the likely introduction of extra bugs would probably make AutoCAD for Windows work less well than it otherwise would.

AutoCAD for Mac would be bad for Autodesk

Autodesk is currently trying to save money by closing down offices, dropping products, cutting down on expenses and sacking employees (some of whom were long-termers; irreplaceable sources of information about use of the product and why certain things were done the way they were). In such an environment, does it make sense to start up a new project with high resource requirements and limited potential benefits? Especially when it is just a repetition of a previous project that was a complete failure?

So, in addition to costing Autodesk a lot of money and harming the quality of its core product, a failed AutoCAD for Mac would leave behind more Autodesk haters and be rather embarrassing.

I must admit that a lot of this is based on guesswork, but it’s educated guesswork. I’ve been educated by history, if nothing else. Autodesk’s corporate consciousness has an occasional habit of ignoring the lessons of history and repeating old mistakes. I hope AutoCAD for Mac – The Sequel isn’t one of those occasions.

Autodesk’s Revit rebellion reaction

It’s time to examine how Autodesk has reacted to the widespread criticism of Revit 2010. Is Autodesk listening? To be more specific, is Autodesk’s Revit team listening?

The Good

It has been good to see extensive public participation by Autodesk people in various discussions in different places. The Revit team isn’t hiding. It is asking for feedback on the Autodesk discussion groups, the AUGI forums and its own blogs, and getting lots of it. Much of it is negative, but it is to Autodesk’s credit that I’m not seeing much in the way of denial, or demands that the criticism must be constructive. I’ve been trying in vain for years to convince some people at Autodesk that denial is counterproductive and that criticism doesn’t have to be constructive to be useful.

The sort of messenger-shooting that I’ve seen some Autodesk people do from time to over the years (*cough* R13, CUI *cough*) is generally absent. I’m not seeing Adeskers arrogantly accusing users of their criticism being based on a failure to understand the product. I’m not seeing asinine comments that infer that the negativity is simply a symptom of the critics’ resistance to change. Actually, I’ve seen one such comment, but it wasn’t from an Autodesk person.

Overall, the Revit team’s responsiveness, openness and level of public availability is impressive. It’s so good that it puts other Autodesk teams to shame. When was the last time you saw an Autodesk person respond to criticism of AutoCAD in the Autodesk discussion groups or AUGI forums? Revit people are doing quite a bit of it, and by looking back I can see that they have been doing it for a while.

There was one attempt at a traditional corporate “the product is great, we just need to review our communications” message. Unsurprisingly, it didn’t work (read the comments). Denial, spin, obfuscation; these things never convince the people who need to be convinced, so why bother? While it’s good to see a reaction from somebody pretty high up in the chain of command, the people lower down have been doing a much better job of communicating with their customers.

The Bad

The trouble with all this communication is that it’s a couple of years too late. It’s no good putting a huge amount of effort into something, introducing it to users, then discovering too late that the users hate it. No amount of communication after the fact can make up for that kind of blunder. Exposing an early design to a handful of people in restricted circumstances can be useful, but it’s nowhere near enough. Lots of people need to be exposed to a product for a long time (as the Revit team now acknowledges – see an interesting Autodesk blog post here). The earlier it’s done, the better the product will be. As a bonus in these difficult times, this will lower the overall cost of development, because problems get exponentially more expensive to correct as the development cycle progresses.

From the public comments I’ve read, the Revit Ribbon was presented to beta testers as late as January, and by then it was very much a fait accompli. There was little chance of making it work significantly better, and none whatsoever of removing a bad design from the product before shipping. This scenario is, unfortunately, confined to neither Revit nor this particular instance. Although I can’t comment on my own Autodesk pre-release experiences, if you have read enough public discussions over the years you will undoubtedly have seen this kind of conversation a few times:

Angry user: “This feature is useless! The beta testers must have been blind to miss this!”
Beta tester: “Actually, we did see it and reported it right away. Autodesk just didn’t fix it.”

I would like to expand on this, but I am somewhat restricted by NDA. I’m not complaining about that (it’s a voluntary agreement), just stating the position I’m in.

Another thing that belongs in this category is the Revit team’s apparent disdain for its users’ wishlists. AUGI Revit people are convinced that their wishlists are being ignored, and I can see for myself that Autodesk’s own Revit wishlist discussion group is hardly a hive of activity.

The Ugly

Autodesk showed the cloven hoof with its exclusion of Phil Read from Autodesk University.* This reflects extremely badly on Autodesk. See here, here, here and here. Almost everybody seems to think this crude and futile attempt at censorship was a deplorable move, and I agree. Besides this being an example of messenger-shooting at its worst, it’s not a good look for the AU event itself. When you pay your AU fees, are you hoping to see the most knowledgeable, enthusiastic, passionate and inspiring speakers available? Or just the ones with opinions that align with Autodesk?

* My reaction is based on the assumption that this exclusion did take place. It has been widely reported and condemned, but not denied by Autodesk, so I think it’s a pretty safe bet. The only comment from AU management is, “Speakers for AU 2009 will be announced around June 15 – I cannot comment before.”

Not another SpacePilot PRO review

This post is not about the new SpacePilot PRO 3D controller from 3Dconnexion (a division of Logitech). This post is about the Internet coverage of the launch of that new device, journalism, blogging, freebies and ethics.

It has long been common practice for companies to give out free stuff to journalists. Free gadgets, free transport and other expenses for attending events, free beer, free lunch… oh, wait, there’s no such thing. As blogging has risen in prominence, that practice has been extended to providing free stuff for bloggers. It was traditional in the past for such freebies to go unmentioned in reports about the products of such companies. I think the first time I saw this kind of thing disclosed was by Ralph Grabowski, and I was impressed. Maybe it’s just the sites I read, but I see more of that kind of disclosure in blogs than I do in the traditional press (whatever that means these days).

It seems that 3Dconnexion is distributing its US$499 SpacePilot PRO devices like confetti (particluarly at SolidWorks World), hoping to get as much coverage as it can. It’s working. Not that I think there’s anything wrong with that. If a company wants to let potential customers know about its products, and if those customers read blogs, it makes sense for the company to send samples to bloggers in the hope that they get reviewed. As long as there are no strings attached, I see no ethical problem with that. If a negative review led to a reviewer being taken off the freebies list then I definitely would have a very big problem with that, but I see no evidence of that from 3Dconnexion.

Where I do see an ethical issue is when a freebie is received, a review is written, and no disclosure is made. I think readers are entitled to know about any free stuff associated with a review, and I think this applies equally to press and blogs.

Let’s have a look at some recent SpacePilot PRO coverage to see how we’re travelling at the moment. The following sites have mentions or reports without explicit disclosure. In many cases a mention is made of having one (or waiting for one) but it’s not clear if this is a free SpacePilot PRO, or if the writer has paid for one. If you’re one of these people, feel free to set the record straight either here or on your own site.

Here’s how I think it should have been done:

There are almost certainly other reviews and mentions that I’ve missed, so feel free to inform me and I’ll add to the above lists.

I hasten to point out that I’m not throwing stones here. I’m not accusing any of these people of writing positive reviews in return for a cool gadget. I’m just encouraging everybody to unambiguously declare any freebies they receive, that are associated in any way with whatever they write.

On Twitter, I see several of my fellow AutoCAD bloggers impatiently awaiting the arrival of their cool gadget. When they receive them, I expect we will see more reviews, and it will be interesting to see how many of those reviews include full disclosure, especially now I’ve raised the issue.

Here’s my own disclosure about my personal association with 3Dconnexion. I investigated the use of 3D controllers for a client and suggested the purchase of a couple of pretty expensive 3Dconnexion SpaceBall 5000 devices. Within months of purchase, 3Dconnexion made these obsolete without warning and failed to produce any new drivers for them, making them expensive paperweights.

When I attended AU 2006 (at Autodesk’s expense as a MyFeedback Scholarship), I turned up at the Press Room looking for a Press badge, as I am a Cadalyst writer. I received a Press person’s small bag of assorted goodies from various vendors. This included pens, small USB keys and the like, but a 3Dconnexion SpacePilot was the stand-out freebie. I later suggested that my client purchase a couple of SpacePilots to replace the obsolete SpaceBalls. Not because of the freebie, but because they were the cheapest suitable devices available.

So, on a personal level that’s one up and one down for 3Dconnexion. My view of 3Dconnexion is about the same as that of parent company Logitech. I like the devices, I’ll even use my own money to buy them, but I don’t think a good enough job is done of supporting recently purchased devices with updated drivers as new software arrives.

I haven’t received a SpacePilot PRO or the promise of one. I’m not sore about that. I haven’t asked or been asked. If they do happen to send me one, I’ll play with it and if I think it’s worth writing about, I’ll do so in an unbiased way and with full disclosure.

More on ODA, Autodesk and click-through agreements

Evan Yares has provided more information on the incident I mentioned in my last post. Here it is:

It was years ago. My guess was that the person who did it was just trying to spider the website pages, for marketing research, and didn’t realize he got all the libraries too.

In any event, I said hey you did this, they said no we didn’t, I produced download logs, they said there was no agreement and even if there was we hereby cancel it, I said if you want to see our libraries I’ll send ’em to you no strings, they said no thanks, then I just let it drop. Of course, I’m paraphrasing.

I wasn’t going to get in a fight with Autodesk. Trying to trick them into joining the ODA would have been both futile and dumb. I’d been trying for years to get them to join (I was an optimist, once upon a time), and it caused no damage for Autodesk to be able to see the ODA libraries. There wasn’t anything in them that they didn’t know better than we did.

Don’t read too much into Autodesk’s belief in the enforceability of click-through agreements based on this incident. I knew the guy who downloaded the files, and knew that he didn’t have the authority to bind Autodesk to an ODA membership agreement (it would have taken at least a VP to do that.)

This is interesting for more than just the amusement factor; it raises a serious point about the enforceability of click-through agreements. In this case it was a web-based membership agreement, but I’m more interested in software license agreements.

In most cases, the person doing a software installation is unlikely to be a Vice President or higher. It’s quite possible that the installer doesn’t even work directly for the company that is supposedly agreeing to whatever terms may be hidden behind the “I Agree” button. In fact, that’s the situation I’m regularly faced with when I install software for a client. The client certainly doesn’t view the “agreement” and may not even know that it exists. The client hasn’t authorised me to negotiate a contract with anyone, only to get some software working. There’s no “meeting of the minds”. The software vendor may think that the client is bound up tight by the terms of the EULA; the client hasn’t agreed to anything and either doesn’t know the EULA exists or doesn’t consider it to have any validity.

Does it matter? Maybe not. It only really matters when one party or the other doesn’t do the right thing. Fortunately, I have honest clients and I’m confident that they will act in an ethical way on an ongoing basis. But will the software vendors do likewise? I don’t know.

Buying 24″ monitors – is now the right time?

I’m doing my bit to reduce the impact of the global financial crisis. Yesterday, I went out and bought a couple of new 24″ monitors to replace my perfectly functional pair of 19″ LCDs. It now looks like I’m facing a huge wall of pixels and I don’t quite know where to look, but I felt like that after moving from my old 19″ CRT to the pair of 19″ LCDs, so I’m sure I will get used to it soon enough. The 19″ LCDs haven’t gone to waste, they are now adorning an older PC which was previously attached to the old and now slowly-dying 19″ CRT.

Why was it a good time for me to buy new monitors? Because of the way monitor aspect ratios are going. The “sweet spot” for monitors right now is 22″ or 23″, where a serious number of pixels are available for very little cash. Trouble is, the pixels are in the wrong place. Almost all monitors of that size have a resolution of 1920 x 1080, a ratio of 16:9, same as a full HD TV. A vertical resolution of 1080 doesn’t provide a significant advantage over an old 19″ 1280 x 1024 (4:3 ratio) monitor.

When I’m not doing CAD or image manipulation, I’m generally doing things that involve lots of vertical scrolling; word processing, reading web pages, that sort of thing. Often, those web pages have a fixed-width design (e.g. AutoCAD Exchange), so adding extra screen width gains me nothing but extra wide stripes on each side. With more and more software having a deep horizontal stripe dedicated to user interface elements, there’s not much point investing in only 56 extra pixels (5.4%) of height.

From my point of view it’s better to pay a bit extra and go for an extra 176 pixels (17.1%) of height: a 1920 x 1200 (16:10 ratio) monitor. These are available in various sizes, but the cheapest ones, and the ones that will fit side-by-side on my desk, are 24″. But these are becoming less common. Even as I’ve been looking over the past few weeks, the number of 24″ 1920 x 1200 monitor models available in my area has dropped off significantly. Unless you’re very careful, if you buy a 24″ monitor it’s likely to be 1920 x 1080.

Why? Many of these monitors are now being used for games consoles; 1920 x 1080 is all they will use. Same with HD TVs; 16:9 is the current fashion in LCD panel ratios, and it looks likely to stay that way. It makes sense for manufacturers to make 16:9 panels, so 16:10 panels are only going to get rarer.

That may make sense for the manufacturers, but it doesn’t help me as a vertical-pixel-hungry customer. Unless I’m prepared to go for much bigger, desk-hogging and expensive monitors, all I’m going to gain with a 16:9 screen is a bunch of width. Even a 27″ monitor I considered, at roughly twice the price of a 24″, offered “only” 2048 X 1152.

I made the decision. I bought a pair of 24″ 1920 x 1200 monitors while I still could. I found a good-value model I could view in the store, with a small enough bezel (important if you’re using them side by side), a height-adjustable stand, and an excellent warranty (3 years pixel-perfect). For me, it was the right time. Maybe it is for you, too?

Some thoughts on AutoCAD Exchange

I’ve added a link to Autodesk’s new AutoCAD community site, AutoCAD Exchange. As with most things Autodesk, there are pros and cons. Here are my first impressions.

I think it looks good in a Vista-black kind of way. I know some of you don’t like the black look in software, but I do. The layout looks a bit cluttered and confused at first, but I’m sure visitors will quickly get used to where to find things. The site appears to be designed around 1024-wide resolution. If you have more than this, as most CAD users do, then there are wide areas of wasted space either side of the good stuff.

The front page is basically a teaser. To get to the useful content or do pretty much anything, you need to register or sign in. I don’t particularly like this, and it gives the impression (false or not) that Autodesk wants to own and control you, even if you’re just viewing a site. The registration process is the same as for other Autodesk sites such as the discussion groups, so if you have an Autodesk identity, you’re already registered.

As it is a “community” site, on first sign-in you are invited to fill in more details, provide an avatar and so on. Some people might not like this, but it’s optional and Autodesk knows where I live so it makes no difference to me. I know where Autodesk lives, too. It has yet to be seen if Autodesk manages to develop a real community on this site, and if so, how open that community is allowed to be.

Autodesk is encouraging bloggers to add an Autodesk Exchange widget to their blogs. I won’t be adding one in a permanent position because this is my blog and not Autodesk’s. I kind of like my independence, and if a company wants space on my blog they can pay for it. Anyway, the widget is available in three sizes and here’s what the largest one looks like:

I’m likely to appear in one of those little interview videos soon, as they were shot during the bloggers’ visit to San Fransisco in early February. When you do get to see it, yes, that’s really me (and Melanie Perry) saying nice things about AutoCAD 2010, it’s not computer generated. Except for the background, that is, which is computer generated. It was bright green in real life. Other than that, no deception, lies, arm-twisting or bribes were involved. Oh, unless you count the free trip to San Fransisco as a bribe. I interviewed Autodesk, they interviewed me, and I actually had positive things to say about AutoCAD 2010. More on that later.

AutoCAD Exchange is an important and potentially very useful site for AutoCAD users. Check it out, and if you feel like it, report back. You can pretty much say what you like here.

Vernor v Autodesk – why I think Autodesk is right

Well, there’s a statement I wasn’t expecting to make. Let me preface these comments with a disclaimer. I have no legal qualifications whatsoever. I make no claims of knowing who is legally right in this David v. Goliath legal battle; that’s for the courts to decide. When I make the statement that I think Autodesk is right, I don’t mean legally right, I mean morally right.

I have been following this fight with interest, but only in a half-baked way, third-hand via commentators (like myself, now). Based on my skimming of that commentary, my natural inclination to support the underdog, and my general dislike of of Autodesk’s previous and current legal adventures, I had been of the firm but privately held opinion that Vernor was right and Autodesk was wrong.

Today, after noting that new filings had been made, I had a proper look at some (not all) of the actual court documents themselves (thanks to Owen Wengerd’s CAD/Court), and surprised myself by coming to quite the opposite conclusion. I am now convinced that I was totally wrong.*

Until today, I was hoping that the court would support Vernor’s assertion that the First Sale doctrine applies in this case. Why? Because I feel that Autodesk is morally wrong in attempting to prevent the transfer of its software from one party to another.** At one time, Autodesk allowed AutoCAD to be resold (despite the EULA of the time saying that it wasn’t allowed) and indeed actively supported the transfer process. I felt at the time that Autodesk’s introduction of this restriction of a customer’s ability to resell AutoCAD was morally wrong. I still feel that way.

I also feel Autodesk is morally wrong in geographically restricting the sale of its software, and in several other areas of its EULA. I would be quite happy to have a court find that Autodesk is legally wrong in those areas, too. Despite that, I feel that it would be A Bad Thing if Vernor won in this case.

Why? Because Vernor was selling software that effectively didn’t exist. He was selling used copies of Release 14, when those copies had already been upgraded to AutoCAD 2000. To me, that’s clearly morally wrong.*** If the court finds that First Sale applies here, then that opens the floodgates to allow anyone to sell old copies of any software that has been upgraded, and keep using the new stuff. I really don’t think that would be good for anyone.

Those of you who have been upgrading AutoCAD for the last 25 years, I hope you held on to all your old copies, because you could be sitting on a gold mine. Of course, unless the court is going to compel Autodesk to acknowledge all these new “owners” of AutoCAD and support them with the various magic numbers required to keep them alive, there are going to be a lot of disappointed buyers around, the word will get around, and the bottom will quickly drop out of the market.

* This is not a first, I assure you.

** It has been stated elsewhere that Autodesk can actually be persuaded to allow the transfer of its software outside the usual restricted areas of merged companies, deceased estates and so on. This may be so, but it’s not something I would rely on.

*** This is a quite different moral proposition from somebody continuing to use an old version of software after upgrading, alongside the new version, on the same computer. That’s something I find entirely morally acceptable, whatever any EULA may stipulate.

A year of nauseam

This is one of those awful self-indulgent blog posts you hate, so just skip it and read the more interesting stuff a bit further down instead.

It is now a year since I started this blog and this is my 200th post. Here are the site statistics for 2008:

Stats 2008

Here they are for 2009:

Stats 2009

I’m sure there are other CAD blogs out there with much more impressive stats than that, particularly the Autodesk ones. I’m pretty happy with the number of visitors I have, though. I’m not sure what I was expecting when I started doing this; maybe a couple of hundred people might be interested, maybe not. I certainly wasn’t expecting 168,000 visits in the first year. I wasn’t even sure I was going to keep it up after the first few weeks. But it seemed to grow in popularity quite quickly so I kept at it. Hopefully, I’ll retain my enthusiasm and keep it going for a while yet.

I’d like to thank all of you who find this blog worth reading, and especially all of you who add your comments, whether I agree with them or not. Please continue!

I’m supporting the New Zealand blackout

Thanks to Robin Capper for bringing this to my attention.

New Zealand's new Copyright Law presumes 'Guilt Upon Accusation' and will Cut Off Internet Connections without a trial. Join the black out protest against it!

http://creativefreedom.org.nz/blackout.html

Disclosure: I’m a software developer, artist (of sorts), copyright owner and part of a company that sells software to allow copyright owners to protect their interests. I’m also the victim of clueless corporations counterproductively interfering with my art. Most of all, I’m a supporter of the fair use of copyrighted materials.

This law in New Zealand needs to be turned back now. If it succeeds in Robin’s country, it will be mine next, then yours. I encourage you to support this viral campaign so it attracts some press attention. Excuse me while I go and turn my gravatar black.

Interesting times ahead for Cadalyst

As many of you may know, I’ve been writing for Cadalyst since 1995. Yesterday, I read in David Cohn’s summary of the history of Cadalyst that in 1991, Lionel Johnston sold CADalyst to Aster Publishing for $2.2 million.

How times have changed! Today, current owner Questex doesn’t think it’s worth keeping alive. I’ve been aware for some months of uncertainty about Cadalyst’s future, and Questex has finally decided that it doesn’t have one. Most of the staff have been laid off, with a tiny skeleton staff keeping things ticking over until the end of the month. As a Contributing Editor (i.e. writer), the financial effect on me is small, but others are less fortunate and have my sympathy.

There’s still hope, though. This is the official word from Editor-in-Chief Nancy Spurling Johnson:

Questex Media Group has decided to divest itself of Cadalyst, effective the end of February. A few of us are working actively on an employee buyout. We believe in Cadalyst and the CAD market and are positive about the future. There’s a lot to work out in the near term, but we are very, very optimistic that we can make this happen and not only keep Cadalyst moving forward, but make it a more valuable resource than ever for our readers and advertisers.

As Questex seems to think the Cadalyst name isn’t worth anything, with a bit of luck the employees won’t have to dig too deep to buy it out, and a long tradition will continue. With the unfortunate demise of AUGI World and uncertainty about any replacement, there’s a hole in the market right now. Sure, it’s a depressed market, but it still has a hole in it and even in a depressed state that market is surely much bigger now than it was in the “good old days” when the magazine was much thicker and the reviews were more critical.

If Nancy can pull off the buyout and Cadalyst continues without a publisher-owner, it’s possible that the result will be a better Cadalyst. It’s almost like a return to its roots; a small core of enthusiastic staff building up a publication. As a long-term reader, I’d be happy to see Cadalyst go back to the future.

The world has changed, of course, and I know I read Cadalyst almost exclusively on-line these days. Cadalyst could continue without printing a thing, either in the short term or permanently. Is there a future for a printed CAD magazine? I hope so. Despite the shift of readers to the on-line world, I still see newsagents full of magazines covering all sorts of topics, many of them more obscure than CAD. There are millions of us. Surely we deserve our own magazine?