« The Build Process: Common Ground for Developers and Administrators | Main| LCTY London and Edinburgh 2010 »

I know you are not that guy...


...because you are reading this post.  But you know who I mean.  The developer who found some code that did a generic dblookup for a combo box with easily configured messages--and then pasted that code everywhere, without knowing what it did.  

Hey, code re-use is a good thing.  But he didn't see the part where it was checking to see if the database is on an OS2 server! Then there's the guy who continues to modify the code in that $$WebQueryOpen field, rather than moving the code to the more appropriate event handler.

This is the same developer that doesn't know about

A picture named M2 PlanetLotus.Org.  Or

 A picture named M3 OpenNTF.org.  Or

 A picture named M4  LotusUserGroup.org.  


He might know about the forums. He might even keep the handouts from his "Introduction to Notes" development course.  Every once in a while I run into one of these caveman developers - they stay in their caves and don't take advantage of the vast resources available in the Lotus community.  So what I do is tell them I know about some fantastic tip--I just don't remember the details... But look on PlanetLotus (or OpenNTF or wherever) and you'll find it.  

What do you do when you run into one of these developers?

Category    

Comments

1 - The Mens Supra Muska Skytop Shoes at its exterior using the snap closure. An adjustable belt for the supra uk has two benefits.

Post A Comment

Feeds

Custom Button Custom Button

Category Cloud

Disclaimer

The views expressed by the authors on this blog do not necessarily reflect the views of Teamstudio, those who link to this blog, or even the author’s mother, father, sister, brother, uncle, aunt, grandparents, cousins, step relations, any other blood relative - and sometimes not even the author himself or herself.

Comments on this website are the sole responsibility of their writers and it is assumed those writers will take full responsibility, liability, and blame for any libel or litigation that results from something written in, or as a direct result of something written in, a comment. The accuracy, completeness, veracity, honesty, exactitude, factuality and politeness of comments are not guaranteed. Oh, how they are SO not guaranteed.
en-us,en;q=0.5OFFCCBot/1.0 (+http://www.commoncrawl.org/bot.html)38.107.179.214www.getthemostfromnotes.comHTTP/1.180Lotus-Domino/tsblog.nsf/D6Plinks/KFRA-839TLR