BEGIN:VCALENDAR VERSION:2.0 PRODID:-//ChamberMaster//Event Calendar 2.0//EN METHOD:PUBLISH X-PUBLISHED-TTL:P1H REFRESH-INTERVAL:P1H CALSCALE:GREGORIAN BEGIN:VTIMEZONE TZID:America/New_York BEGIN:DAYLIGHT RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU DTSTART:20070101T000000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:Eastern Daylight Time END:DAYLIGHT BEGIN:STANDARD RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU DTSTART:20070101T000000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:Eastern Standard Time END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=America/New_York:20260528T173000 DTEND;TZID=America/New_York:20260528T193000 X-MICROSOFT-CDO-ALLDAYEVENT:FALSE SUMMARY:AI Meet Up & Exchange DESCRIPTION:What is the goal of the AI Meet Up? \nOur mission is simple: we want to bring together our community to broker meaningful conversations that help you navigate AI in your business and career. The meet up features a speaker to educate and initiate conversation and connections. \nTopic: Managing the "Messy" Parts of AI Development Presenters: Matt Houseman and Michael Emerick\nFor the May session\, we're planning to do a deep dive into what it actually looks like to build a tool using AI as a teammate. Most people use AI to write snippets of code\, but we've been working on a framework\, using Agentic AI and Microsoft Copilot\, to manage the entire lifecycle of a project while keeping things clean and controlled. \nThe Project: From Unstructured Data to Actual Insights We'll be using a tool we built as our case study: an application that takes a pile of unstructured invoices and turns them into organized data and spend observations. \nInstead of just showing the finished product\, we want to walk through how it actually came together in less than two hours: The Blueprint: How we used "Procedural Guidelines" to keep the AI from going off the rails during the roadmap and technical design phases. The Workflow: A look at how we move from a high-level problem into specific user stories and prompts. Being Honest About Bugs: We'll show the points where the AI tripped up like a side-nav bar overlapping the content or multi-file upload glitches and how we used those moments to refine our prompts and fix the code live. \nLet's Build Something Live Once we've shown the "how-to\," we want to hand the keys to the audience. We're planning to: Take a live request: We'll ask the group for a new feature or an "edge case" maybe something like predicting future spend or flagging duplicate payments and try to implement it on the spot using the framework. Brainstorming Other Workflows: This approach isn't just for developers. We want to hear what kind of "messy" manual processes the group is dealing with in their own roles so we can talk through how to apply this same structured AI approach to solve them. \nOur goal is for everyone to walk away with a practical mental model of how to use AI as a reliable\, predictable collaborator for any complex project. X-ALT-DESC;FMTTYPE=text/html:

What is the goal of the AI Meet Up? \;


Our mission is simple: we want to bring together our community to broker meaningful conversations that help you navigate AI in your business and career. The meet up features a speaker to educate and initiate conversation and connections. \;


Topic: Managing the "\;Messy"\; Parts of AI Development \;

Presenters: Matt Houseman and Michael Emerick


For the May session\, we&rsquo\;re planning to do a deep dive into what it actually looks like to build a tool using AI as a teammate. Most people use AI to write snippets of code\, but we&rsquo\;ve been working on a framework\, using Agentic AI and Microsoft Copilot\, to manage the entire lifecycle of a project while keeping things clean and controlled. \;


The Project: From Unstructured Data to Actual Insights \;

We&rsquo\;ll be using a tool we built as our case study: an application that takes a pile of unstructured invoices and turns them into organized data and spend observations. \;


Instead of just showing the finished product\, we want to walk through how it actually came together in less than two hours: \;

·\; The Blueprint: \;How we used "\;Procedural Guidelines"\; to keep the AI from going off the rails during the roadmap and technical design phases. \;

·\; The Workflow: A look at how we move from a high-level problem into specific user stories and prompts. \;

·\; Being Honest About Bugs: We&rsquo\;ll show the points where the AI tripped up&mdash\;like a side-nav bar overlapping the content or multi-file upload glitches&mdash\;and how we used those moments to refine our prompts and fix the code live. \;


Let&rsquo\;s Build Something Live \;

Once we&rsquo\;ve shown the "\;how-to\,"\; we want to hand the keys to the audience. We&rsquo\;re planning to: \;

·\; Take a live request: We'\;ll ask the group for a new feature or an "\;edge case"\;&mdash\;maybe something like predicting future spend or flagging duplicate payments&mdash\;and try to implement it on the spot using the framework. \;

·\; Brainstorming Other Workflows: This approach isn'\;t just for developers. We want to hear what kind of "\;messy"\; manual processes the group is dealing with in their own roles so we can talk through how to apply this same structured AI approach to solve them. \;


Our goal is for everyone to walk away with a practical mental model of how to use AI as a reliable\, predictable collaborator for any complex project.

LOCATION:4925 Ritter Rd\, Mechanicsburg\, PA 17055 Mechanicsburg PA 17055 UID:e.3328.1449118 SEQUENCE:3 DTSTAMP:20260425T121258Z URL:https://harrisburgregionalchambercredcpa.growthzoneapp.com/chambereventscalendar/Details/ai-meet-up-exchange-1716457?sourceTypeId=Hub END:VEVENT END:VCALENDAR