Slow API calls. Hidden error return values from other apps. Memory leaks poor multi threading transaction locks that are not released.
On Tue, Sep 26, 2017 at 9:52 AM, Paul H. Tarver <[email protected]> wrote: > Agree with your addition. I think I was more or less thinking of > self-inflicted bugs initially. > > Paul H. Tarver > Tarver Program Consultants, Inc. > Email: [email protected] > > > -----Original Message----- > From: ProfoxTech [mailto:[email protected]] On Behalf Of Dave > Crozier > Sent: Tuesday, September 26, 2017 9:39 AM > To: [email protected] > Subject: RE: [NF]Debugging Pain Survey > > + Bad product (Component Documentation) either not correct or just plain > wrong. > ... Currently struggling with C# Office Interop and finding conflicting > Microsoft documentation. > ... now my first port of call is sites such as StackOverflow and not the > manufacturer... > > > -----Original Message----- > From: ProFox [mailto:[email protected]] On Behalf Of Paul H. Tarver > Sent: 26 September 2017 15:25 > To: [email protected] > Subject: [NF]Debugging Pain Survey > > Since this could technically apply to any programming language, I'll tag it > as [NF], but Foxpro was the inspiration for the question. > > > > This past weekend, I was working on a significant refactoring of an > existing > application and I found myself in that never-ending land of try and re-try > until all of the dumb, crash causing bugs were out of the way and I could > get on with working on logic issues and other more important thoughts. > There > are a lot of different "bugs" that get in the way of programming success > many of which I experience on a regular basis. So, I thought it might be > fun > and interesting to try to find out what programmers think their biggest > sources of bugs are. > > > > Below is my short list of bug sources in no particular order. Rank them in > the order of the pain they cause you from most to least: > > > > Typos > > Bad Variable References > > Bad Object References > > Logic Errors > > Unexpected Data Variations > > Incorrect Data Types > > Local vs Public Variables > > Cut n Paste Code > > Unexpected User Actions > > > > PS: if you can think of more sources of bug pain, please add them as > required. > > > > Paul H. Tarver > Tarver Program Consultants, Inc. > > Email: <mailto:[email protected]> [email protected] > > > > > > > > --- StripMime Report -- processed MIME parts --- multipart/alternative > text/plain (text body -- kept) > text/html > --- > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/cajidmy+yvvredlp6uovmsdgudz1d_lybnz2p+exbk3ounkh...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
