I run workshops about the use of modular systems in facilitating non-expert participation in architecture. One I did (at the CAAD Futures Conference in 2023) was with Zometool. It was a blast and really successful.
In preparation I also got to interview the late great Steve Baer, inventor of the Zome (among many other things - seriously look him up, he's one of the most brilliant people of the past 100 years imo). It was a huge honor.
The book chapter the organizers were supposed to do about the conference workshops never materialized (hrmph), but I've done other little collaborative build projects since, so one day I'll document them all together.
I have come to modal editors after decades of modeless, I enjoy them - but respect, understand, and appreciate Tesler's efforts, and I always enjoy reading about them.
I have been an Adobe user since 1996. Starting with Photoshop 3. Then, using the rest of their programs since 1999.
Between this and the fact that they've just 1. Changed all the old accounts to "Adobe Creative Cloud Pro" 2. DOUBLED the monthly fee, now charging you for the AI features whether you want them or not, and 3. Removed any tiers that have full program access but no AI, I am walking away forever when my current month expires.
Not to mention, students now only get the old $19.99 membership for the first year.
I teach visualization and representation tools to architecture students. I had always taught them Adobe products before. Now I can't in good faith sign them up to have their expertise tied to using this program stack forever. So tomorrow I am giving them a lecture on free to use and FOSS versions of the same tools. And I'm going to teach the class from them in perpetuity. Congratulations, Adobe that's 50+ students a year who won't be using your products when they graduate.
No, the concepts are the same. The button you push is incidental.
For example, the GNU Image Manipulation Program now has non-destructive workflows and adjustment layers - and can easily easily be configured with photoshop-like keybinds anyway.
That's not to mention free-to-use tools like Affinity.
The things an architecture student needs it for are:
Photo adjustment:
Lightroom -> Darktable
Photo retouching:
Photoshop -> Affinity Pixel or Gnu Image Manipulation Program
Vector drawing (which for us is mostly processing from 3d modeling programs):
Illustrator -> Affinity Vector or Inkscape
Board and Book Layout
InDesign -> Affinity Layout or Scribus or VivaDesigner
Plus, for motion graphics and video processing, my partner and I have had great luck replacing AfterEffects and Premiere with Blender and DaVinci Resolve, respectively.
And ... believe it or not, I've had excellent luck with LibreOffice Draw as a PDF editor, so anything they would have needed Acrobat Pro for is covered by that (and / or PDF SAM).
The real "sticky wicket" is Revit. Autodesk has been a FAR more abusive company for FAR longer, but it's what we're stuck with - although the emergence of the BIM Workbench (Building Information Modeling) with the release of FreeCAD 1.0 [0] and the continued development of BlenderBIM (oh, now called BonsaiBIM) [1] at least gives some hope.
Anyway, for the Adobe replacements, here's more [2] based on [3]
> Autodesk has been a FAR more abusive company for FAR longer, but it's what we're stuck with - although the emergence of the BIM Workbench (Building Information Modeling) with the release of FreeCAD 1.0 [0] and the continued development of BlenderBIM (oh, now called BonsaiBIM) [1] at least gives some hope.
I believe AutoCAD is the epitome of what is wrong with Autodesk. It's expensive, there is no permanent license, there is basically no real alternative, and they aggressively go after pirated copies.
If I were a vibecoder, instead of silly toys like a half-broken compiler that nobody uses, I'd focus all my energy and tokens on creating a real Autodesk alternative. And if it really worked, including seamless witch, the authors would quickly make tons of money.
I think at the current level of LLM code I have observed there's basically zero chance they can produce a competitive cad/cas. Maybe they could approximate an open source kernel like opencascade but I don't see the point in that when freecad already exists.
Unfortunately it looks like BricsCAD has gone the SaaS way, but they are an extremely mature alternative to classic AutoCAD 2d and 3d [0]
Additionally, Rhino has always been a good drafting tool [1] but my understanding in the current WIP (which if I'm guessing will probably be released as 9.0, within the next 6-12 months) is making a huge push to include better drafting tools. McNeel, the developer, has no plans to go to a subscription model.
Our use case for After Effects was video stabilization. We have had good luck with Blender for this. I've also noticed that the old simple motion graphics I used to do - title overlays, etc - Blender can do easily. As for more intensive motion graphics, I can't speak too much to that.
As for any After Effects-style NLE capabilities - DaVinci Resolve knocks those out of the park. You'll also probably hear a lot of people singing the praises of Natron for NLE and Motion Graphics, and from our experience with that it seemed like the learning curve was non-trivial, but anything AE (and some aspects of Premiere Pro) could do, it could match... Good luck!
I think it is the opposite of detrimental and should have been best practice 10 years ago already. Same goes for software development, which I regard as a creative exercise as well. Today the software landscape is different and learning the common industry workflows is probably the least difficult part of any design curriculum.
Detrimental would be to subject students to the whims of Adobe, which doesn't really have that much moat any more.
Probably different at huge companies, but small employers I know don't care how you get your work done. If anything they're happy if they don't have to buy/rent licenses for you.
…now that I think about it, don't architects predominantly work in smaller companies?
Speaking as a lifelong graphic designer with over 20 years experience under my belt: it really doesn’t matter what kind of software you use, HOWEVER, not using the industry standard can bite you in the ass quite fast. PDF export can be finicky, colour management is hit or miss, collaboration is nearly impossible…
I wish someone would come and take Adobe’s monopoly down for good, but as it stands, shunting Adobe for something else in a professional environment is more trouble than it’s worth.
It's absolutely very important for students to understand what standard they'll be held to in industry. But few architects need an intricate understanding of the real publication-facing aspects of the programs. In our case, using these tools is pretty much always in support of getting the output of 3d modeling / BIM tools / photography of physical models into presentable shape. Going away from Adobe might be unwise were I teaching graphic design students, but for these students, those more sophisticated, domain-specific expertises are a lot less essential.
Great article. Where my mind goes as a counterpoint that proves the point is the famous Bill Atkinson lore about -2000 lines of code[0].
As a practicing architect (of buildings) I had a special fondness of working on minimalist projects. Buildings are a complex problem space. You typically can't design out unnecessary complexity entirely. So you have to work backward from goals (the finished condition) to infrastructure (the building structure) to figure out how to make the end product look like almost nothing (Mies's "beinahe nichts").
That's all to say that "complexity impresses" as the article says, but the discerning understand that simplicity can be even more impressive.
It also puts me in the frame of mind of another famous one - Fred Brooks's "No Silver Bullet" [1] and the idea of essential vs. accidental complexity. Or as I like to think of it in a slightly more nuanced way - not necessarily "accidental" but at least "incidental."
Yeah, in retrospect that was always a little on the nose, wasn't it? A real 'my t-shirt is raising questions that I thought were answered by the shirt' kind of deal.
Bookmarked for constant reference.
As a designer, Japanese printmaking is a constant source of inspiration, and the effort that went into putting this together is pretty astounding. Thank you to the author for the hard work, and to the OP for surfacing it!
RIP Sheldon Brown. His enthusiasm for and ability with bicycles - and his clear and engaging way to communicate both to you - were a large part of getting me back into cycling as an adult.
The em-dash=LLM thing is so crazy. For many years Microsoft Word has AUTOCORRECTED the typing of a single hyphen to the proper syntax for the context -- whether a hyphen, en-dash, or em-dash.
I would wager good money that the proliferation of em-dashes we see in LLM-generated text is due to the fact that there are so many correctly used em-dashes in publicly-available text, as auto-corrected by Word...
Which would matter but the entry box in no major browser do was this.
The HN text area does not insert em-dashes for you and never has. On my phone keyboard it's a very lot deliberate action to add one (symbol mode, long press hyphen, slide my finger over to em-dash).
The entire point is it's contextual - emdashes where no accomodations make them likely.
Yeah, I get that. And I'm not saying the author is wrong, just commenting on that one often-commented-upon phenomenon. If text is being input to the field by copy-paste (from another browser tab) anyway, who's to say it's not (hypothetically) being copied and pasted from the word processor in which it's being written?
Check out the History of the Germans season on the Hanseatic League [0]. The bulk goods trade was in the Baltic / Northern Europe was actually huge. The Hansa themselves traded all the way from London to Novgorod. Anyway, it's an absolutely fascinating subject and period.
I run workshops about the use of modular systems in facilitating non-expert participation in architecture. One I did (at the CAAD Futures Conference in 2023) was with Zometool. It was a blast and really successful.
In preparation I also got to interview the late great Steve Baer, inventor of the Zome (among many other things - seriously look him up, he's one of the most brilliant people of the past 100 years imo). It was a huge honor.
The book chapter the organizers were supposed to do about the conference workshops never materialized (hrmph), but I've done other little collaborative build projects since, so one day I'll document them all together.