BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTART:2011-10-29T15:30:00Z
DTEND:2011-10-29T16:45:00Z
SUMMARY;ENCODING=QUOTED-PRINTABLE:Programming Standards and Guidelines - Rick Schummer
DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Application program code not only tells the computer what to do, but should enhance the ability of another developer to read it and allow the a developer to easily understand its intent. Effectively, code is a way for developers to communicate with each other. Just as in daily life, if the developers speak a different dialect of the same natural language, it can easily lead to bad communication, misunderstandings, and other potential problems.=0D=0A=0D=0AThe purpose of programming standards and the creation of a standards document is to consolidate and clearly define the approved standards and guidelines currently being practiced by the development staff at your company. The document should be a living document; the standards and guidelines it describes should undergo regular review as the development team determines better ways to practice their craft. All code written is expected to follow these guidelines in force at the time it is written, unless technically prohibited. =0D=0A=0D=0AWhy do we need a written set of standards and guidelines for developers? Shouldn't we expect a developer to be mature enough to follow best practices and accepted industry standards with respect to software development and programming? Naturally, good and experienced developers have the innate ability to write good code and over time have developed some standards they follow. But as you bring different developers together, each with their own experiences and standards, you start to get code that is harder to read and understand. Having standards is a way to have everyone get on the same page, and enhances the ability to read, enhance, and support each other's code.
LOCATION;ENCODING=QUOTED-PRINTABLE:Gilbert
UID:SWFOX20112011-10-29T15:30:00Z
PRIORITY:3
END:VEVENT
END:VCALENDAR