Amazing to read these little historical tidbits.
When most software development was still changing how we did things, and was a trek through wonderland. It was a great time to be a software engineer.
Still some today, but now most software is a commodity like making cars. And tech careers have faded into the same muck as most others.
Unpopular opinion perhaps, I learned Nuke when it was still part of DD software and the first versions that came out of the Foundry were an absolute smoking pile with regard to the interface.
At that time Shake’s future was not yet in full-blown crisis but the writing was on the wall—some key people were moving over from Apple (if memory serves) which explains some of the ui similarities at the time.
Didn’t it used to render .Action setups?
Yes to a certain extent. Also could load tracker setups, what were called luts and a few other bits and pieces.
The studio I was at (2004?) bought nuke seats while it was still a DD internal tool. This included in-person training at DD. So the flame artists were sent there to learn it but I was booked and couldn’t go. Everyone that went ended up full time nuke and went on to work on big budget movies. I’m still here just plugging away on commercials 
Hahahahha! Wonder who this was
“There were early adopters, however,” notes Egstad. “Mostly in Europe, who were brave. I remember getting an email from someone I think in Sweden or in Denmark, asking about the 3D system. This would’ve been around 2003.
I did the first shot comped in Nuke at Method. 
For Clint Eastwood’s Invictus.
When I was at the OG Method (2004-2008) we were working on a Hummer spot where said beast drives off a pier and continues to scoot around underwater á la submarine.
The 3D artist responsible for the underwater section came from DD and had experience with Nuke (which we had a couple of seats of, v3 I think). He set up his passes with intention and his pre-comp was superior to that of the final comp done is Flame…which I always found humorous.
This is, of course, before the days where (at least in my experience) Flame artists were accustomed to working with so many passes and understanding how to use them. It was really cool and enlightening to see how he leveraged everything and his logic behind each pass.
Cool article but people need to stop using “architected.” It’s not a verb. Architects don’t “architect,” therefore no one does. The word everyone is looking for is “designed.” That’s what architects do. Architects design.
I disagree slightly here.
One of my job titles at HP way back was for software architect (on the LTO service software platform).
A software engineer designs code to work and be maintainable for a specific release. A software architect thinks in multi-generational terms and expandabilty, paltform aspects. While both are design tasks they do have different scope and considerations and thus using different terms seems appropriate.
Better yet, architects get someone else to design while they fly helicopters…
Would you employ “architected” as a verb personally?
I architect, they architect, etc…
I don’t think it’s useful; It’s harder to say and less clear. You still have to specify what was done, so it doesn’t clear up anything the way using “engineer” might replace “designed in a technical manner according to rules of physics and science”
Yes, I have heard it and have used it in verb form.
Might be personal preference or industry lingo. Doesn’t sound wrong to me.
If someone says I architected Flame’s 3D system, I would understand that as being the overall 3D system, as opposed to designing the 3D viewer UI, or the camera analysis node, which are specific components or code aspects.
@andy_dill - i felt obligated (obliged) so i googled it…
should have nuked it…
Sorry @allklier but I also disagree. Architected is for sure a made up word. Never heard it before this thread as a matter of fact.
Also sounds totally wrong to me at least.
But of course language evolves and made up words or made up verbs, can and do become part of a language.
Also I probably shouldn’t start a sentence with “But”, at least if this was back in the day.
But that boat sailed a long time ago so actually you’re right! Haha
So, you’re saying “architected” was in fact architected…
Andy, do we stop using Ask as a noun or Architect as a verb? You can only pick one.
I don’t know, sounds like a heavy lift.