14 Reasons to write my own product configurator.
1. I am a masochist any enjoy abuse.
2. I wish to spend the rest of my life living and breathing macro code and bask in the knowledge that the company is paying me big $ and benefits to do this instead of spending a couple of $k for a piece of software.
3. Job security, no single person will be able to understand my code.
4. I can quit here and get more money from some other stupid company for doing the exact same thing.
5. I will be unable to be an engineer.
6. I will create the results that where specified in the documentation only to discover that was not the result that was desired.
7. I am prepared to assume responsibility for the correct functioning of my code after any or all of the following events
a. The IT department change network software ( including anti-virus)
b. The IT department moves network drives.
c. IT decides to migrate from 32bit to 64 bit.
d. Microsoft changes operating systems
e. Solidworks/Autocad release an update
f. Visual basic changes format
8. The company releases new product designs before the old ones are configured and want them available for the next advertising campaign
9. I will spend days writing code just to prove that what somebody wants what can’t be done. Like automation of drawing cleanup.
10. Someone will want to combine two extremely different product configurators. ( reference Item 9)
11. Everybody will leave an automation planning meeting agreeing to the same thing but already planning the strategy that will get them what they want, not what they agreed to. I will enjoy the abuse this creates(ref Item 1)
12. I will thank my company for putting me in this position, because I used to drink for no particular reason, now I have a reason.
13. Support the drug companies Prozac, valium, cymbalta etc.sale are down.
Stress tests and heart caths are fun
