hexagon logo
Register Sign in
  • Replies 8 replies
  • Subscribers 222 subscribers
  • Views 91 views
  • Users 0 members are here
Options
Related

Programmer/Authors Notes

acgarcia
Just wanted to see what everyone else is doing. I need to get in the habit of documenting like the date I proved a program in $$ comment for record keeping and just general notes of changes I made.

Does anyone have a specific format or style that they can share for ideas? I'm thinking something like my Name, Date, maybe CAD revision, drawing names and revisions?

Thanks.
Parents
  • We make a simple text block, list the 'Issue'(revision) of the program, declare what type of changes we make then add the programmer's initials and the date of change.
    This matches the description of change in our program log. None of this information shows on any report, you just see that the revision of the program has been updated and you can dig from there.
Reply
  • We make a simple text block, list the 'Issue'(revision) of the program, declare what type of changes we make then add the programmer's initials and the date of change.
    This matches the description of change in our program log. None of this information shows on any report, you just see that the revision of the program has been updated and you can dig from there.
Children
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement