Let’s come together and discuss how we can attract more people to technology in general and DevOps specifically. We'll cover how to effectively bring people into technology and support their learning. We'll spend some time identifying challenges faced by the local DevOps community and develop a starting point of strategies for addressing them.
Kim Crayton (https://twitter.com/KimCrayton1) is a Community Engineer and Technology Edutainer, because who said doing GOOD has to be BORING!
She has years of experience working with learners of all ages, skill level, and abilities and is now using her knowledge to develop technical people, ideas, organizations, and communities. Her current efforts focus on creating environments that support the safe sharing of common attitudes, interests, and goals, which she is doing with The CAYA Project (http://CAYAMediaGroup.com), as well as bringing a bit of FUN to the technology learning experience.
She is the past co-organizer of CodeNewbie-Atlanta, founder of the CAYA Media Group (content designed to inform, encourage, and promote diversity AND inclusion in tech), founder of JrDevMentoring (http://www.jrdevmentoring.com/), KimCrayton1 on Medium (https://medium.com/@KimCrayton1), and a contributor to the Hypepotamus newsletter and the freeCodeCamp blog. Kim is currently pursuing a Doctors of Business Administration - Technology Entrepreneurship. Her doctoral study topic is: “Successful Strategies Utilized in the Development of Junior Software Developers.” She is also working on her passion projects: The ABC’s of Coding, Tech Talk For Non-Techies, #MentoringMinute (https://twitter.com/hashtag/mentoringminute), JrDevMentoring (http://www.jrdevmentoring.com/), @100000Intros (https://twitter.com/100000Intros), @TheSpectrumCode (https://twitter.com/TheSpectrumCode), and @CommEngReport (https://twitter.com/CommEngReport).
5:30-6:00pm: Networking, food, and beverages
6:00-7:30pm: Kim Crayton & Discussion
All attendees are expected to abide by our Code of Conduct (https://www.meetup.com/devops/pages/19194929/Code_of_Conduct/).