So ... Who is Mr. Grigor?
There are more than 15 years now, since I've first met 3D Studio MAX, and since then I have a special bond with "her". Even then "she" was amazing, very powerful and full of mysteries to me, but ... the fate decided that I have to leave her, that my future lays in the world of finance, banking and other boring words.
Nevertheless, I still was watching her from time to time, how "she" evolves, going stronger, going powerful - almost impossible for me to catch up with her, so I gave up.
Meantime, I had a great opportunity to end with all this financial world and switch toward a domain that was more appealing to me and that was close to my nature - the domain of Computer Science - Ahh ... Algorithms, Data Structures ... Heterogeneous Programming and C++ ... - marvelous words for those who understand their purpose and make use of them and what a curse for those who are forced to learn without understanding them.
In the end, armed with Computer Science knowledge, I started to search for purpose in my life, and here the fate reminded me of my bond to now 3ds Max, especially that I now live so close to "her" cradle.
I joined Autodesk, Inc. without any hesitation, and now I have the chance to talk to "her" on daily basis, either through C++, Python or MAXScript, depending how intimate the talk is. Moreover, in my position of Developer Technical Consultant, my primary task is helping plugin developers to know "her" better and perhaps to overcome the difficulties they encounter in their endeavor of mastering the way to reach "her" heart - the mighty 3ds Max SDK.
If you need an official Autodesk company response or a contact for press-related activities please contact Autodesk Public Relations.
The contents of this site are my own personal opinions and do not represent my employer's view in any way. In addition, my thoughts and opinions often change, and as a weblog is intended to provide a semi-permanent point-in-time snapshot you should not consider out-of-date posts to reflect my current thoughts and opinions.
The code provided in this blog is provided "as is" and with all faults. I (and my employer) specifically disclaim any implied warranty of merchantability or fitness for a particular use. The operation of the code provided is not warranted to be uninterrupted or error free.