PHP

Our monthly PHP meetup. A virtual shindig courtesy of Zoom. Check back here for the details around 6:15 pm

**PLEASE READ THE FOLLOWING IMPORTANT NOTES:** 1. The dates listed for this series are about 95% reliable. We are finalizing our 2026 schedule, so minor adjustments are still underway. 2. Each class in this series has an attendance fee, on a first-come, first-served basis. 3. Each class, from BOTH a sign-up and fee perspective, is a separate entity. **Introduction:** **The breakdown of the six-class series is as follows:** **Class 1: TBD** **Class 2: TBD** **Class 3: TBD** **Class 4: TBD** **Class 5: TBD** **Class 6: TBD**

Bring your work or your hobby, hang out, and code with us. Follow @buckeyecocoa for more information.

**Latest Dojo Location!** **Knotty Pine Brewing** 1765 W 3rd Ave, Columbus, OH 43212 We're going to try a new dojo location for a few weeks and see how it works Dojos are informal Python group study sessions where everyone interested in Python gathers to learn about Python, help others with Python, or just hang out. Everyone is welcome from Python beginners to experts. Bringing a laptop is encouraged (we'll have extension cords and power strips). If there's something you want to learn leave a comment on this invite so we can plan ahead. We're looking for speakers for our Monthly Meetups! Fill out the form if you are interested in presenting to the Python Community. https://forms.gle/ehSfUAC2WgR34Crq9

**PLEASE READ THE FOLLOWING IMPORTANT NOTES:** 1. The dates listed for this series are about 95% reliable. We are finalizing our 2026 schedule, so minor adjustments are still underway. 2. Each class in this series has an attendance fee, on a first-come, first-served basis. 3. Each class, from BOTH a sign-up and fee perspective, is a separate entity. **Introduction:** **The breakdown of the six-class series is as follows:** **Class 1: TBD** **Class 2: TBD** **Class 3: TBD** **Class 4: TBD** **Class 5: TBD** **Class 6: TBD**

**Welcome to Drunken Philosophy** a casual, curious social discussion **Optional topic for this meetup: What's up with all the AI hate?** A recent survey found that 74% of Americans have a negative view of AI, and I want to know why. Come out and debate whether AI is good or bad. My hot take: a labor-saving tool that could potentially help cure cancer gets called dangerous because it might raise unemployment or cause a speculative investment bubble, that tells you a lot more about capitalism and the economic system we live under than it does about the tool itself. As a computer programmer, I think AI is a wonderful tool that has increased my productivity by at least an order of magnitude. I'd go so far as to say Claude Code is the best tool I have ever used. Debate me and name a better one. Is AI potentially dangerous? Yes, but so are a lot of tools. Chainsaws. Steam engines (early ones would occasionally explode and kill everyone in the room). Do you think cavemen sat around debating whether fire could be used as a weapon or for self-harm, and decided not to discover it? I have two friends who hate AI for opposite reasons: one thinks it's a fad and not useful, and the other thinks it's going to take over everything and cause human extinction. Come out tonight, have a friendly debate, and make some friends. No lectures. Friendly crowd. Drop in for one drink and stay if it's fun.

**Important time note:** Please plan on arriving between 5:30 and 6:00 as the elevators lock after 6 and you'll need to message us and we'll need to come get you. The building address is 4450 Bridge Park The entrance is 6620 Mooney St, Suite 400 You will need to scan your ID at the door to get a visitor badge. **Abstract** Like it or not, AI agents are now capable of turning a quickly written paragraph of requirements into a pull request that is ready to be integrated into real-world production applications and it's now our responsibility to make sure AI doesn't go rogue and take down prod - or corrupt our data by misunderstanding the requirements or our existing schemas. In this session we'll explore strategies to protect our codebases through unit and integration testing, documentation, and code review along with additional ways of providing context and guard rails to our AI agents as they carry out the work we've assigned them to do. By the time we're done, you'll have a firm grasp of the problem and understand some helpful options for protecting your codebase from vibe coding mishaps getting YOLOed into prod. **YouTube Link** TBD