I like when you spend 15 minutes trying to work out why the chip wont program, till you realise its not actually in the programmer. (just avoided putting the *wrong* chip in the programmer oence too, it wasnt even a pic.... hehe 12V programming voltage on some random pin.... mmmmm) ----- Original Message ----- From: "Dave VanHorn" To: Sent: Wednesday, July 02, 2003 10:00 PM Subject: Re: [OT]: You know you have been working too late when... > At 02:04 AM 7/2/2003 -0500, Alex Kilpatrick wrote: > >It is 2 am here in Texas. I just spent fifteen minutes trying to figure > >out why my circuit wasn't working. Turns out the PIC was still in the > >programmer. :-) > > > >Anyone want to add some bonehead mistakes to the list? > > Nothing stands out in memory, but I have had days when I come back into > work, and it takes me an hour to understand how the code I wrote the night > before actually works. > > I seem to get into something called "flow state" pretty easily, and time > becomes mostly irrelevant, and I get a hell of a lot of work done. > http://www.guydickinson.com/knowledge/archives/000676.php > > It's easily disrupted by interruptions though, which is why I tend to work > later on programming, and use the normal 9-5 hours for phone calls and > other maintenance tasks. > > -- > http://www.piclist.com hint: The list server can filter out subtopics > (like ads or off topics) for you. See http://www.piclist.com/#topics -- http://www.piclist.com hint: The list server can filter out subtopics (like ads or off topics) for you. See http://www.piclist.com/#topics