3 ms·
My dad was in purchasing for various aircraft manufacturers, including McDonnell Douglas and Boeing. It was literally his job to try and keep this nonsense und
by treeman79 3y ago
My dad was in purchasing for various aircraft manufacturers, including McDonnell Douglas and Boeing.
It was literally his job to try and keep this nonsense under control.
It was extremely frequent that the engineers would request some screw with hyper specific requirements and would end up costing dozens of dollars or so per screw. Even more for the specialized tooling that would go with it.
From his perspective, the engineers loved designing new things rather than looking up, if anything previously existed.
So he would try and take the requirements and see if there was some off-the-shelf substitution that would meet the requirements. Saved companies a fortune again and again.
- codeisawesome 3y agoThis sounds rather familiar, in Software :)
- roflyear 3y agoMore software companies need this role. I tried to make this my role recently (with cloud services and whatever) and succeeded somewhat but not entirely.
- aidenn0 3y agoVery different in software. Many engineers can get away with spending many hours of their time on building software they need, but sure as heck can't unilaterally get the company to shell out a few hours worth of their salary buying the equivalent for them.
- kmoser 3y agoThe more relevant problem being alluded to by the parent of your post is that engineers would rather write their own code than find an existing library (which is more often than not free) that does the same thing.