Home » Archives » February 2005 » Problem Solving 2192.1029.1777

[ Previous entry: Restart now... or restart later. ]
[ Next entry: FoxShow 033 ]
02/23/2005:

Problem Solving 2192.1029.1777


Programmers or developers or any human in the problem solving workforce, tend to have difficulty solving the problem if their minds are clouded beforehand with buffered and imagined scenarios that they think will cause complications to occur.

Anticipating problems which may possibly occur in the future is a good programmer virtue, yet sometimes, it can serve as a hindrance itself to attaining solutions.

It is always good to have a Plan B, but always keep in mind why you need that alternative. Forgetting the real reason of having conceived a plan B in the first place can sometimes mislead you.

I have this Plan B in case Plan A will not work considering I'm using an A-10 approach and Factor A-9 exists.

Enumerate first the real possible causes that prevent A-10 approach from working before jumping to Plan B, which most of the time is a lazy way out.

Never blame Factor A-9 too.

Sometimes we do have this set of possible causes which blind us.

And blind us big time, it does.

Validate those variables first. Sometimes the most efficient solutions are aligned with the most simple and obvious answers.

CLICK for a LARGER much SEXIER version.

Last week, I decided to include a TreeView control in one of my newly converted VFP8-to-VFP9 projects. During the development phase, my mind was already clouded with the possible DLL-Hell related stuff, possible VFP9-libraries-on-site compatibility issues, the well-behaved Windows 98SE machines in my clients site, green alien abductions and countless possible shenanigans that might occur.

And so it goes, after two failed installation attempts, DependencyWalker tinkering, InstallShield version upgrades (and even downgrades), CD archive searching, three CPU testings, OLE/DLL manual gathering and regsvr32-in', compilations and recompilations, VFP5 Developer's Guide skimming, screaming, punching, calling the gods of Asgard... and countless other efforts, I still... was unsuccessful.

Only to find out that the real cause of the problem lies in my code itself.

You might blame my alien-related paranoia for not detecting the problem right away, but... the main reason is that my mind was already clouded with too many factors that prejudiced/poisoned/muddled the problem solving process.

Free the mind, human.

Even the most complex problems are dealt with with an array of systematic step by step simple solutions that work.

You don't need to study rocket science to be able to do that.

(And go back to the pen and paper approach if needed. (Papers rock!))


Disclaimers are for castrated EARTHLINGS.
Powered: GREYMatter | GM-RSS

 

 
 
 
 

 

foxpro.main
foxpro.archives
richardbase.home

articles
downloads
snippets
utilities
knowledgebase.links
website.links

outpost.forum
the.site
the.catalyst
pixelcatalyst.lair

rss.feeds

February 2005
SMTWTFS
   1234
567891011
12131415161718
19202122232425
262728    
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004





GEEK count:
visitors since the aliens rebooted the counter last 02.23.2006 (was around 33,000++ before the alien intrusion | SINCE: 02.26.2004)