>-----Original Message----- >From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] >On Behalf Of William Couture >Sent: 07 February 2007 15:25 >To: Microcontroller discussion list - Public. >Subject: Re: [EE] Does it take a baseball bat to apply a clue to an EE? > > >On 2/6/07, Aaron wrote: > >> >How about little things? >> > >> >For example, since he hasn't looked at extern EEPROM >availability in >> >several years, he thinks that he can only get the density >he needs as >> >an I2C part. Of course, this isn't true. But he's already >designed >> >it. And built prototypes... >> >> Why don't you do a design review before building prototypes? > >Because this is a small company. The designed was "reviewed" >by another EE-type (we have one "real" EE, and one "sort-of" >EE/Technician), but not by either software engineer. > Does your company have a defined product development process? Although you should try to attend final design reviews, they are not the correct stage in the process to be looking for dumb design decisions. All this kind of thing should have been sorted much earlier on, and your input should be required at any stage that potentialy affects the software developement. Regards Mike ======================================================================= This e-mail is intended for the person it is addressed to only. The information contained in it may be confidential and/or protected by law. If you are not the intended recipient of this message, you must not make any use of this information, or copy or show it to any person. Please contact us immediately to tell us that you have received this e-mail, and return the original to us. Any use, forwarding, printing or copying of this message is strictly prohibited. No part of this message can be considered a request for goods or services. ======================================================================= -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist