I understand that people assume you are up to speed on their project. I can be
a little slow on picking up something in the middle without examples and
comments. It's a lot like reading someone else's code (or your own code a month
later).I know I am guilty of this, my presentations on my projects were short.
I assumed other people knew what as happening, and I was often wrong about
that. This is a wonderful forum and the people are always a help. In my case
I'm having to learn a lot, I haven't used Unix sense AutoCad forced me to
Windows in the 90s' and now a move to Linux is a little overwhelming.
Scott
On Wednesday, June 30, 2021, 1:24:46 PM CDT, Bari <bari00...@gmail.com>
wrote:
On 6/30/21 12:59 PM, Scott Harwell via Emc-users wrote:
> I wish there was a little more "mansplaining" in some of the "docs". I still
>haven't decided how to set center of rotation for "A" and "C" in the
>Kinematics example.
I agree. Can we adopt a code of technical writing or CoT for short?
What happens if somebody violates the CoC? Do they get their bits
banned? Do they get a strongly worded letter followed by stern looks?
A social psychologist would not be surprised by the reactions and
dynamics over this. We have the people that want rules and authority to
feel comforted vs those that don't require any amendments to "do unto
others".
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
_______________________________________________
Emc-users mailing list
Emc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-users
