BEGIN:VCALENDAR PRODID:-//github.com/rianjs/ical.net//NONSGML ical.net 4.0//EN VERSION:2.0 BEGIN:VTIMEZONE TZID:America/Phoenix X-LIC-LOCATION:America/Phoenix END:VTIMEZONE BEGIN:VEVENT DESCRIPTION:There are 2 hard problems in computer science: cache invalidat ion\, naming things\, and off-by-1 errors. \n\nThis session is about nami ng things. In software\, we need to name classes\, methods\, properties\, libraries\, and solutions. We also have to give names to variables\, pa rameters\, namespaces\, interfaces\, services\, resources\, etc. And mos t of the time\, they can'\;t conflict. Sometimes it'\;s easy but s ometimes it can be hard. \n\nWe'\;ll do a quick review of some of the easy guidelines that avoid some (somewhat easy) decisions then look into the things that require names that involve a deeper understanding of cont ext. What the contexts are\, their granularity\, and how that applies to alleviating naming issues will be covered. How the types of contexts an d their motivation and good compartmentalization makes for easier naming will be detailed. We'\;ll dig into some details of English grammar tha t should relegate naming is hard as a code smell—something that hints at deeper problems in the structure of code. And finally\, time permitting\, some techniques and ideas to relegate *naming is hard* to problems of th e past will be outlined. DTEND;TZID=America/Phoenix:20181006T163000 DTSTAMP:20260316T061712Z DTSTART;TZID=America/Phoenix:20181006T153000 GEO:33.293070;-111.796620 LOCATION:Chandler - Gilbert Community College - IRN-231 ORGANIZER: SEQUENCE:0 STATUS:CONFIRMED SUMMARY:There are 2 hard problems in computer science: cache invalidation\ , naming things\, and off-by-1 errors. \n\nThis session is about naming t hings. In software\, we need to name classes\, methods\, properties\, lib raries\, and solutions. We also have to give names to variables\, parame ters\, namespaces\, interfaces\, services\, resources\, etc. And most of the time\, they can'\;t conflict. Sometimes it'\;s easy but somet imes it can be hard. \n\nWe'\;ll do a quick review of some of the easy guidelines that avoid some (somewhat easy) decisions then look into the things that require names that involve a deeper understanding of context. What the contexts are\, their granularity\, and how that applies to all eviating naming issues will be covered. How the types of contexts and th eir motivation and good compartmentalization makes for easier naming will be detailed. We'\;ll dig into some details of English grammar that sh ould relegate naming is hard as a code smell—something that hints at deep er problems in the structure of code. And finally\, time permitting\, som e techniques and ideas to relegate *naming is hard* to problems of the pa st will be outlined. UID:0e63d4d7-018b-4b44-b19c-4ded6b40639c END:VEVENT END:VCALENDAR