Author Topic: tribal knowledge  (Read 345 times)

0 Members and 1 Guest are viewing this topic.

Offline munkeyman1985

  • Contributor
  • Posts: 5
  • Country: us
tribal knowledge
« on: November 07, 2019, 02:36:55 pm »
I ran into an interesting problem at work. A test written using NI TestStand need to be moved to a new folder structure because of a revision change. My coworkers confidently jumped on and changed each string one line at a time. There is a better way, and when I found out what was happening I talked them through it. 

I now realize I have some simple steps I use to save a lot of time. How can I share that with the rest of the teem. They often just dump things in a folder and every idiot that can access will change it. Would like some way of sharing it while maintaining the integrity of the information.  Any suggestions?
 

Offline RandallMcRee

  • Frequent Contributor
  • **
  • Posts: 372
  • Country: us
Re: tribal knowledge
« Reply #1 on: November 07, 2019, 04:56:06 pm »
I ran into an interesting problem at work. A test written using NI TestStand need to be moved to a new folder structure because of a revision change. My coworkers confidently jumped on and changed each string one line at a time. There is a better way, and when I found out what was happening I talked them through it. 

I now realize I have some simple steps I use to save a lot of time. How can I share that with the rest of the teem. They often just dump things in a folder and every idiot that can access will change it. Would like some way of sharing it while maintaining the integrity of the information.  Any suggestions?

Use source control--e.g. github.com
If you have just a modicum of discipline great benefits shall accrue. Namely, the blame button.   ;D
 

Online Gribo

  • Frequent Contributor
  • **
  • Posts: 430
  • Country: ca
Re: tribal knowledge
« Reply #2 on: November 08, 2019, 05:31:04 pm »
In Teststand, you should use relative paths, not absolute.
 

Offline ejeffrey

  • Super Contributor
  • ***
  • Posts: 1994
  • Country: us
Re: tribal knowledge
« Reply #3 on: November 08, 2019, 07:51:21 pm »
Yes, use version control. For everything.  And when your tools don't play well with version control complain to your vendors that their tools are defective.  A common cause of this is files with important user editable configuration mixed in the same file as ephemeral or unimportant information (such as recently opened files, window positions, or even just datestamps).  Automated deployment tools should then fetch the appropriate code from version control so that you know what version is running in production.

Peer review is annoying but super valuable: people are less likely to commit garbage in the first place if they know someone will look at it, and peer review can catch style issues like using relative vs. absolute paths.

Relative paths or variable expansion can help of course but don't necessarily save you when you re-organize your project.
 

Offline DimitriP

  • Super Contributor
  • ***
  • Posts: 1055
  • Country: us
  • "Best practices" are best not practiced.© Dimitri
Re: tribal knowledge
« Reply #4 on: November 08, 2019, 08:24:53 pm »
Quote
every idiot that can access will change it
It depends.
First, pardon the condesending tone.
Are you just another team member or the team lead/manager/supervisor etc ?
If the former, you do nothing.
If the latter, you must propagate the idiots out of your team.

Anything else is a bandaid that may or may not eventually come back and bite you on the ass.






   If three 100  Ohm resistors are connected in parallel, and in series with a 200 Ohm resistor, how many resistors do you have? 
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf