Anyone can write udfs and custom tags it takes very little skill.
Writting well crafted ones might make you mid-level. Custom tags with
something like checking the execution mode missing definetly would
make you look low level...Likewise making a UDF isn't that complex but
not varing all your varia
If someone can write CFCs, custom tags and UDFs, I automatically upgrade
him/her to mid-level. For me this would be a sign that the person is a
mid-level developer.
Johnny
> Breaking encapsulation In CFCs (or custom tags or UDFs) by referencing
>shared scope variable (application, session, r
I'm pretty conscientious about documenting my open-source work.
Probably moreso than most folks... But then my documentation is also
all web-ready and a test-case for the framework. The majority of it
does end up being "language"-reference (documentation for individual
tags, functions and CFC's) bu
poorly formatted code + no documentation or comments= bad;
poorly formatted code + bad documentation or comments = bad;
[poorly formatted code + good documentation or comments = bad;]*
[well formatted code+ no documentation or comments= GOOD;]*
well formatted code + bad docu
poorly formatted code + no documentation or comments = bad;
poorly formatted code + bad documentation or comments = bad;
[poorly formatted code + good documentation or comments= bad;]*
[well formatted code+ no documentation or comments = GOOD;]*
well formatted code + bad docu
At 10:39 PM 5/9/2005, you wrote:
>Not all documentation is good; in fact, most is bad (in my experience.)
In my experience, most is non-existent. But, I've never had a problem
with documentation that is there. And I still have a hard time imagining a
time where comments make it hard to follo
