| ??? 11/19/11 21:57 Read: times |
#184817 - Never blame manufacturer without proofs Responding to: ???'s previous message |
In this case, Mahmood wanted Microship to stand in the corner, despite there being no proof that they had any responsibility for the problem.
And experience says that programmers are more than likely to be responsible for this kind of issues. Because of something they didn't think about. Blaming the chip manufacturer without first having followed up on the actual issue is like blaming the compiler vendor when the source code doesn't do as intended. If you google around, you will find a large number of examples of code "that works" who suddenly doesn't work anymore. |
| Topic | Author | Date |
| NXP Promises ARM Cortex-M0 in DIL Package! | 01/01/70 00:00 | |
| Amazing! I thought DIL was DEAD. | 01/01/70 00:00 | |
| Me too! | 01/01/70 00:00 | |
| Hmm.. | 01/01/70 00:00 | |
| maybe | 01/01/70 00:00 | |
| dsPIC is a waste of time | 01/01/70 00:00 | |
| We Await The Results... | 01/01/70 00:00 | |
| Which one(s)? | 01/01/70 00:00 | |
| two | 01/01/70 00:00 | |
| Why so long? | 01/01/70 00:00 | |
| Well | 01/01/70 00:00 | |
| Two years | 01/01/70 00:00 | |
| Answers | 01/01/70 00:00 | |
| But what delays did you try before original release? | 01/01/70 00:00 | |
| shorter delays | 01/01/70 00:00 | |
| good thinking | 01/01/70 00:00 | |
| Can't get the error | 01/01/70 00:00 | |
What changed? | 01/01/70 00:00 | |
| Seems a little harsh | 01/01/70 00:00 | |
| Never blame manufacturer without proofs | 01/01/70 00:00 | |
| Proven Product Syndrome | 01/01/70 00:00 | |
| My response ... | 01/01/70 00:00 | |
| No Offense | 01/01/70 00:00 | |
| What I Do and Not Do | 01/01/70 00:00 | |
| NXP are mistaken | 01/01/70 00:00 |