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
+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!
>
>
Thirty years ago when I got out of college and got a job selling computers
(where I got my first exposure to Foxpro for DOS), I met an older in-house
service technician ( he started out fixing typewriters and then migrated to
computer repairs) who told me, "Computers would be a lot more fun if we
Been bitten by that one a few times too.
Paul H. Tarver
Tarver Program Consultants, Inc.
Tel: 601-483-4404
Email: p...@tpcqpc.com
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave
Crozier
Sent: Tuesday, September 26, 2017 9:59 AM
To:
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)
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
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 wrote:
> Agree with your addition. I think I was more or less thinking of
> self-inflicted bugs
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: p...@tpcqpc.com
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Dave
Crozier
Sent: Tuesday,
+ 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-
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
I used a similar code. Actually what I had to do was put the original code
(the one quoted in my first email on this) in a prg, called from the form
I had this code within a loop (that iterated some 400 times) in my
send_email form. But it would not work. When I took the code out of the
form and
I used a similar code. Actually what I had to do was put the original
code (the one quoted in my first email on this) in a prg, called from
the form
I had this code within a loop (that iterated some 400 times) in my
send_email form. But it would not work. When I took the code out of the
form
I used a similar code. Actually what I had to do was put the original
code (the one quoted in my first email on this) in a prg, called from
the form
I had this code within a loop (that iterated some 400 times) in my
send_email form. But it would not work. When I took the code out of the
I've just tested this code and it sent successfully, but not until I
turned on the 'less secure apps' setting on the Gmail account.
https://gist.github.com/anonymous/ddb479e315bcc45efb0d4703fc05b836
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
14 matches
Mail list logo