FXPert
Member
Yea, they type newbie in the subject line incase the others can't tell
robertmee said:Yet, I see the same companies make the same mistakes over and over. It is all about the $$ capital expenditure up front with no account taken for the final product.
... shops is a huge name in the particular industry I service. They've been around for decades, but due to attrition, layoffs, etc. they produce some of the worst control work I've seen.
Just my experience!Oakley said:I've been following this thread since it's inception, but have kept quiet (until now) ...
I have observed a fundamental failure in the way business is run. You cannot go on bid cost alone - there must be an evaluation by competent people. And here is where the Sales force comes in! Why evaluate? Costs $$$, Just throw a figure out (which is usually pulled out of sales people A$$)and if they accept it a bonus is guranteed! Enough said.
The first comment is that engineering (or others) put out an RFQ then let unexperienced people evaluate the bids - which typically lead to lowest cost winning.
When I (or my team) evaluate bids, we have an engineering developed matrix that we complete.
We evaluate past performance, assigned resources, ability to quote the project based on the RFQ, technical ability (goes back to past performance), process risk, etc.
If the resources are not familiar, then we ask for resumes and past references.
All this may be more workload for us, but we have data that will back up our decision for our selection. Management has a much harder time rejecting our selection based solely on costs.
One thing I have never understood are those that ask how an instruction works. Everyone has access to the same documentation. My attitude has been to just stick the new instruction in a rung and see what it does! As long as the outputs are connected to anything real what harm can it do? I do the same thing for C and Mathcad code. I am learning Java now. I make plenty of mistakes. I just do it where they only cost my time. When I figure something out I save it away so I can reference it later.MASEngr said:The reason I can do that is because I'm not afraid of making mistakes.
Peter Nachtwey said:The idea is to make mistakes where you know nothing bad will happen.
Peter Nachtwey said:One thing I have never understood are those that ask how an instruction works. Everyone has access to the same documentation. My attitude has been to just stick the new instruction in a rung and see what it does! As long as the outputs are connected to anything real what harm can it do? I do the same thing for C and Mathcad code. I am learning Java now. I make plenty of mistakes. I just do it where they only cost my time. When I figure something out I save it away so I can reference it later.