Tag Archives: Kean Walmsley

Autodesk has lost some of its best people

15 Replies

If you follow certain people on social media this may not be news to you, but Autodesk has just suffered a shocking loss. People at SOLIDWORKS World were amazed to see Lynn Allen, probably the most famous person in CAD, and for decades the face of Autodesk, in attendance.


Image credit: Craig Black via Facebook

No, she wasn’t spying on the competition; she’s praised aspects of what Dassault is doing and has described the event as “pretty amazing”. In her own words, she’s now a free agent. Lynn, a highly professional and entertaining presenter, was undoubtedly Autodesk’s biggest drawcard. No more.

This story is much bigger than one person,though. Other highly competent long-term Adeskers to move on include docs and tips wiz Heidi Hewett, highly professional AU manager Joseph Wurcher, Inventor guru Jay Tedeschi, marketing manager Justin Hoey and PR director Noah Cole. Just the people I’ve mentioned here have well over a hundred years of experience and knowledge, but they are just a handful of the 13% of employees Autodesk is losing this time round. This cull is following on from another 10%, not that long ago.

The entire Neuchatel office in Switzerland has been closed, although Kean Walmsley survived (thankfully). I guess if you’re just holding station on improving your products and moving into rent-the-same-thing-every-year-and-jack-the-prices-up mode then there’s not much call for research and development.

I’m not going to speculate on whether any of the people I’ve mentioned were pushed out, took advantage of an attractive redundancy offer, or just decided it was an opportune moment to jump from a ship of questionable soundness. That’s a private matter between those people and their former employer. I will say that if Autodesk really wanted to retain these people it could probably have made that happen.

Why would Autodesk allow this much knowledge and skill to walk away? Same answer with everything Autodesk does these days that has people scratching their heads: money. Long-termers cost more money, so lopping them looks like an easy way to cut costs. If they’re competent and knowledgeable they’re worth every penny, though. Top people can be many times more productive and valuable than not-so-top people. Given Autodesk’s not-yet-successful attempt to be Adobe, the beancounters are desperate to make it look like the bottom line is about to improve.

While it’s true that the graveyard is full of indispensable people, my experience tells me that losing top people is almost always a false economy. Because the financial penalties of lost institutional knowledge often aren’t directly attributable and don’t show up on a spreadsheet in a handy “losing X cost us $Y” format, it’s easy to pretend those penalties don’t exist. They do, they’re real, and they’re coming Autodesk’s way.

I wish all of the people affected by these events all the best with their future. Onwards and upwards!

Edit: Principal User Experience Designer Bill Glennie, familiar to many pre-release testers of Autodesk products, has also gone.

AutoCAD 2018 – why did the DWG format change?

105 Replies

In my review of AutoCAD 2018, I had this to say about AutoCAD 2018’s changed DWG format:

Why does AutoCAD 2018 need a new DWG format? It probably doesn’t. The 2013 DWG format is capable of holding pretty much anything you want… Although Autodesk cites performance reasons with certain drawings, I strongly suspect the new DWG format was introduced purely to make life difficult for competitors, and to encourage wavering customers to stay with Autodesk for fear of losing compatibility. In other words, it seems likely this is an anti-competitive change rather than a technical one.

In a recent blog post, highly respected Swiss-based Autodesk development and research person Kean Walmsley had this to say on that subject:

The main reason for the break in compatibility is some longer-term work that’s going on inside the AutoCAD codebase. For now this is really only surfacing in small ways – I expect it’s contributing some performance benefits, for instance – but the work is absolutely critical to the long-term viability of the product.

Kean’s a straight-shooter and I’m always ready to be corrected if it can be shown that I’m wrong. So I would be interested to learn more detail about this long-term work that’s critical to the long-term viability of the product. It might be good news for customers or really terrible news. If the groundwork is being laid for a file format that’s more heavily cloud-reliant or subject to continuous change, say, that would be an absolute tragedy for customers.

Autodesk is clearly manoeuvring customers into a position of maximum tie-in using various nefarious means, and if the DWG format change is part of that then it’s to be condemned. Maybe further information would help alleviate such concerns. Kean can’t provide that information, and neither can the selected bloggers who were given some insight under NDA last week, but I’m sure someone at Autodesk could. That is, if there really is nothing to worry about.

Kean also had this to say:

AutoCAD continues to be a core part of Autodesk’s business – and it continues to receive significant investment in terms of development resources – but don’t expect that to translate to buckets of shiny new features: AutoCAD’s feature maturity means the investment is rightly being focused in other areas (at least for now).

This had me wondering if Kean mistyped “immaturity”, because almost every AutoCAD feature from the last decade was released immature and only the lucky few eventually got finished. There’s a huge mass of outstanding work left to do in AutoCAD just to bring its existing half-baked features up to scratch, practically all of which could be done without disrupting customers with a new DWG format.

As for the feature set itself being mature, I can’t agree with that, either. Maybe it’s considered mature within Autodesk because of defeatist thinking about what’s possible with DWG-based CAD software? Kean’s comments seem to reinforce that impression. From where I’m standing, the lack of progress in recent AutoCAD releases demonstrates a severe lack of imagination and hunger to improve the product, not any inherent natural plateau in CAD development.

I believe this because Autodesk’s keener competitors have shown that no such plateau exists. Bricsys has proven that it’s very possible to improve an AutoCAD-like DWG-based product out of sight with genuinely useful and productive new features, and they can do it without changing the DWG format. Incidentally, my preliminary tests indicate BricsCAD V17 opens and saves DWG significantly faster than AutoCAD 2018, again without the need for a new format. More on that in a later post.

Back to Kean:

This is a tricky balance – and could easily be interpreted as a big company not caring about (some of) its users and only being interested in milking its cash-cow – but the work happening behind the scenes is significant and I believe will ultimately prove to be of real value to our customers.

Real value? History has taught me to be dubious about that. Many things that Autodesk promotes as being of value to customers turn out to be of net negative value. Time will tell with this one.

Sorry, but I really don’t believe that Autodesk cares about AutoCAD and its users as anything but an income source. I know there are still honest, hardworking, enthusiastic people within Autodesk (like Kean) who want to improve the product on behalf of customers. Good luck to those people, because their efforts are being stymied by management. The results we’re seeing out here in customer land are dismal, and no matter what spin is put on that, it must be disheartening.

Autodesk people, caring about users? Sure. Autodesk, the public listed company, as directed from the top? Nope. Autodesk’s actions and inactions tell me otherwise. Zero cares are given. No words can fix that, no matter who they come from.

AutoCAD really is being treated as a cash cow; hang one of those bells around its neck and be done with it.


(Original image: Daniel Schwen)

Autodesk’s Kean about moving to the Cloud

3 Replies

Autodesk’s API guru Kean Walmsley is the second Autodesk person I’ve seen who has been brave enough to stick his head above the parapet by discussing the Cloud, in writing, and in a medium that allows for public comment. Kean has always seemed like a straight shooter to me. Please note that his blog represents his personal opinions rather than an official Autodesk position. He’s after your comments, so please go and let him know what you think on his post. Add your comments here if you’re more comfortable with that, and I’ll make sure Kean sees them.

Taking control of your command line history

13 Replies

Thanks to Kean Walmsley’s post on his Through the Interface blog, I have learned something that would have been handy to know for the last decade or so, but which somehow escaped my knowledge. I learned how to increase the size of AutoCAD’s command line history cache. It defaults to 400 lines, which isn’t enough for me. I think this information deserves a wider audience than the ubergeek developers who frequent Kean’s blog, so here goes.

Although it’s not directly mentioned on Kean’s post, you can find the current command line history cache length setting like this:

(getenv "CmdHistLines")

This will return a value showing the number of command lines AutoCAD remembers, e.g. “400”. Although this is used as an integer value, it is passed to and from the Registry as a string. You can set a new value as shown below. Again, use a string, and note that values outside the range 25 to 2048 will be ignored:

(setenv "CmdHistLines" "2048")

Also, if you don’t like AutoCAD repeatedly stopping during a long listing (e.g. SETVAR ? *), you can turn off that feature by setting the QAFLAGS system variable to 2. Don’t set it to 8191 as suggested in Kean’s post, because that will change a lot of other settings, few of which are documented publicly.

The John Walker interview, and other observations

1 Reply

I have been thoroughly enjoying Kean Walmsley’s interview of Autodesk co-founder John Walker, which he has now finished. Kean’s link to part 4 is currently broken (edit: now fixed) and that broken link has been picked up by others (edit: also fixed in Between The Lines), so here are the correct links: Part 1, Part 2, Part 3 and Part 4.

One of the best things about the interview is that it contains some frank criticism of Autodesk (and Microsoft, for that matter). On an Autodesk blog. Think about that. OK, it may be criticism of some stuff that is now ancient history, and it was made by someone who isn’t actually an Autodesk employee any more, but when was the last time you saw even that? It’s refreshing to see just a tiny crack appear in the never-say-anything-negative Autodesk facade.

I remember a time when Autodesk people were allowed to speak reasonably freely in public, often did so, and were even known to make admissions that not everything always smells of roses. John’s fellow Autodesk founder Duff Kurland once wrote this wonderful, wonderful response to a question of mine on the CompuServe ACAD forum (it was about Autodesk removing Visual Basic support without warning, if you’re curious):

We screwed up. We screwed up twice.

He then went on to explain the detail of how and why Autodesk had screwed up and exactly what they had learned from the experience. Can you imagine any Autodesk person saying that now? If they did, can you imagine that person remaining an Autodesk employee afterwards in anything other than a sweeping-up capacity? Nor me, and that’s a real shame. It would be easy enough to justify it by saying Autodesk is a public company and has a glossy corporate image to preserve, but nevertheless it’s still a real shame.

Back to John Walker. Although John has been away from the AutoCAD scene for an age now, I’ve still been enjoying his comments for many years in The Autodesk File, which I’ve always said should be compulsory reading for all new Autodesk employees. I haven’t always agreed with John’s views on everything, but they are intelligently presented, sometimes confronting, and often entertaining. Besides, it’s hard for me to argue with somebody who has succeeded in the way he has; he could always say, “Well, I did this. What have you done?”

Here are some of my favourite John Walker quotes (from The Autodesk File):

If we continue, as we have done consistently for the last eight years to measure every proposal against the standard, “How does this benefit the customer?”, I believe the success we’ve experienced to date will be just the base upon which far greater achievements can be built.

…we must never forget our customers. It is the customer, ultimately, that we are working for, and it is the customer who we must always strive to satisfy. All the rest will take care of itself, in the fullness of time.

Around here, I’ve been known to say things like, “I don’t care what you think. What do the customers think?”. That may sound arrogant, but to me it’s just plain old common sense. The evidence that it works is all around us.

Finally, and if you’re trying to lose weight, have a read of John’s The Hacker’s Diet. It’s also common sense and my slowly shrinking gut is evidence that it works.