|
Re: Why the sudden burst of code postings?
You should attempt to tell the world about what you have done, including any especially good parts.
You obviously want your actions, and your bragging about the parts that are worth copying, to be notorious, in a good way.
The intent of the rule is obvious. Please, especially don't be weasels who satisfy the letter of it, but purposefully fail to satisfy its spirit.
Publish/announce early, often, widely, and proudly. When you are doing that correctly, you will know it without needing to ask for confirmation.
Blake
__________________
Blake Ross, For emailing me, in the verizon.net domain, I am blake
VRC Team Mentor, FTC volunteer, 5th Gear Developer, Husband, Father, Triangle Fraternity Alumnus (ky 76), U Ky BSEE, Tau Beta Pi, Eta Kappa Nu, Kentucky Colonel
Words/phrases  I avoid: basis, mitigate, leveraging, transitioning, impact (instead of affect/effect), facilitate, programmatic, problematic, issue (instead of problem), latency (instead of delay), dependency (instead of prerequisite), connectivity, usage & utilize (instead of use), downed, functionality, functional, power on, descore, alumni (instead of alumnus/alumna), the enterprise, methodology, nomenclature, form factor (instead of size or shape), competency, modality, provided(with), provision(ing), irregardless/irrespective, signage, colorized, pulsating, ideate
|