??? 10/29/09 17:01 Read: times |
#170216 - not exactly Responding to: ???'s previous message |
Erik Malund said:
What's wrong with letting the O/P do what he wants, and, only after he's done that, point out the presumed error of his/her ways
those cases have all ended up with "MAKE WHAT I HAVE WORK DARN IT!" Please show me any textbook that reads: "Do xyz and learn from the mistake" Referring to responses you made in the past you have pointed out that some in Farawayistan may not have the funds to purchase suggested items. Now you want them to purchase what they think they should use, find out it does not work and then purchase what works. Erik I wouldn't expect them to buy anything! I would expect them to explain why they have chosen what they've chosen, and, only after that is "on the table" would it be appropriate to discuss alternatives, beginning with "what is available for you to use?" After all, what's on hand is less costly and troublesome than what's not, even if more effort is needed in order to implement it. Now, in some cases, it might be unrealistic expectation on the part of the O/P. I'm not hostile to offering suggestions once the reason for the presumed "wrong choice" is known. I do, however, oppose your frequent suggestion that a student flatly refuse to use a given component (e.g. i8255) that's present on a student's EVB, in favor of something that isn't present and can't easily be accommodated on that board, or, much worse, suggest a different (often SiLabs) MCU, which would of course, be unrealistic under such circumstances. RE |