Re: [NF]Debugging Pain Survey

2017-09-28 Thread Laurie Alvey
How true! Laurie On 28 September 2017 at 01:38, wrote: > On 2017-09-26 10:59, Dave Crozier wrote: > >> The one that bites everyone: >> >> The difference between what you see . and what you THINK you see! >> > > > "Well it works fine on my

RE: [NF]Debugging Pain Survey

2017-09-27 Thread mbsoftwaresolutions
On 2017-09-26 10:59, Dave Crozier wrote: The one that bites everyone: The difference between what you see . and what you THINK you see! "Well it works fine on my machine." ___ Post Messages to: ProFox@leafe.com Subscription Maintenance:

Re: [NF]Debugging Pain Survey

2017-09-26 Thread Ted Roche
On Tue, Sep 26, 2017 at 10:25 AM, Paul H. Tarver wrote: > So, I thought it might be fun > and interesting to try to find out what programmers think their biggest > sources of bugs are. > "The Last Guy" If you wrote the original code, well, then, it's not a bug, it's a billable

Re: [NF]Debugging Pain Survey

2017-09-26 Thread John Weller
+1 :-) John Weller 01380 723235 079763 93631 Sent from my iPad > On 26 Sep 2017, at 15:59, Dave Crozier wrote: > > The one that bites everyone: > > The difference between what you see . and what you THINK you see! > >

RE: [NF]Debugging Pain Survey

2017-09-26 Thread Paul H. Tarver
Ken Dibble Sent: Tuesday, September 26, 2017 10:34 AM To: profoxt...@leafe.com Subject: Re: [NF]Debugging Pain Survey I am embarked upon such a project right now, cleaning up/refactoring/commenting a bunch of code from a recent, very fast-moving project now that user demand for changes has slowed dow

RE: [NF]Debugging Pain Survey

2017-09-26 Thread Paul H. Tarver
...@leafe.com Subject: RE: [NF]Debugging Pain Survey The one that bites everyone: The difference between what you see . and what you THINK you see! Dave -Original Message- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Paul H. Tarver Sent: 26 September 2017 15:52

Re: [NF]Debugging Pain Survey

2017-09-26 Thread Ken Dibble
I am embarked upon such a project right now, cleaning up/refactoring/commenting a bunch of code from a recent, very fast-moving project now that user demand for changes has slowed down. Here's my list of most common issues: 1. Typos 2. Bad Variable References (really, just a subset of Typos)

RE: [NF]Debugging Pain Survey

2017-09-26 Thread Dave Crozier
The one that bites everyone: The difference between what you see . and what you THINK you see! Dave -Original Message- From: ProFox [mailto:profox-boun...@leafe.com] On Behalf Of Paul H. Tarver Sent: 26 September 2017 15:52 To: profox@leafe.com Subject: RE: [NF]Debugging Pain Survey

Re: [NF]Debugging Pain Survey

2017-09-26 Thread Stephen Russell
; To: profoxt...@leafe.com > 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

RE: [NF]Debugging Pain Survey

2017-09-26 Thread Paul H. Tarver
, September 26, 2017 9:39 AM To: profoxt...@leafe.com 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

RE: [NF]Debugging Pain Survey

2017-09-26 Thread Dave Crozier
+ 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-