Independent Game Development

**Location**: Tysons-Pimmit Regional Library (Virginia) Conference Room A game development **Working Session** involves 3 key parts: 1. Tell people what you're going to do 2. Actually do stuff 3. Show people what you did That's what we'll be doing for this meeting. We'll briefly tell each other what we're going to do, then work on our projects, then at around 5:30 wrap up to show each other what we did and chat for a bit. You don't have to stay the whole time, so feel free to drop in and out as you have time. All game development skill levels welcome. Whether you're bringing a game you're trying to ship in a month, or you're just planning on following some tutorials or trying out a new tool to improve your skills, use this time to make progress. Working sessions also train you to think about the scope of your work: pick a chunk of work that you can complete in the time that we have. That way you can end the working session with a feeling of accomplishment! **What to bring**: Laptop, Charger, maybe a power strip if you have one handy, any other game development tools you need. Try to download any software you need before the working session. There is Wifi at this location, but it may be slow if you have to download any large files.

**Location**: Tysons-Pimmit Regional Library (Virginia) Conference Room A game development **Working Session** involves 3 key parts: 1. Tell people what you're going to do 2. Actually do stuff 3. Show people what you did That's what we'll be doing for this meeting. We'll briefly tell each other what we're going to do, then work on our projects, then at around 5:30 wrap up to show each other what we did and chat for a bit. You don't have to stay the whole time, so feel free to drop in and out as you have time. All game development skill levels welcome. Whether you're bringing a game you're trying to ship in a month, or you're just planning on following some tutorials or trying out a new tool to improve your skills, use this time to make progress. Working sessions also train you to think about the scope of your work: pick a chunk of work that you can complete in the time that we have. That way you can end the working session with a feeling of accomplishment! **What to bring**: Laptop, Charger, maybe a power strip if you have one handy, any other game development tools you need. Try to download any software you need before the working session. There is Wifi at this location, but it may be slow if you have to download any large files.

Join local video game developers, artists, musicians and writers to talk about the art and science of game development. Bring a device and demo your game, talk shop, find like minded folks to join forces with, have a snack or a beverage among new friends. We are an informal meetup where we share what we've been working on and socialize. Come for all or just a bit of the time!

Join our new group’s fourth meeting. Meet fellow tech enthusiasts west of the beltway. ​Our meetings are a great place to work on and show off what you do. We are always welcoming. ​Our format is great for people who have started on but not finished one or several side projects. ​We will start off with basic introductions and what we are working on, along with what our goals are for the session. We’ll break the rest of the meeting into two working sessions. In between, we’ll do a quick check-in to see how folks are going. We also have some polls available which we use to shape our events: ​[https://submatrix.net/article/Meetups/e9ym4fr8Ca](https://submatrix.net/article/Meetups/e9ym4fr8Ca) You can also find or RSVP to our events on these platforms: https://luma.com/vw8ha8bj https://www.linkedin.com/events/7444552350616272896

Spec-driven development flips the traditional workflow on its head: instead of code being the source of truth, the specification becomes the backbone of design, collaboration, and delivery. In this session, we’ll explore how GitHub Spec-Kit enables teams to treat specifications as first-class artifacts—living documents that drive architecture, implementation, and verification. You’ll learn how Spec-Kit helps teams clearly express intent using structured, version-controlled specs that live alongside code. We’ll walk through a practical workflow that starts with defining system behavior and constraints, then progressively refines those specs into testable, automatable outcomes. Along the way, we’ll show how specs can reduce ambiguity, improve cross-functional collaboration, and make design decisions explicit before a single line of production code is written. This talk will cover: --What spec-driven development is (and what it isn’t) --How GitHub Spec-Kit fits into modern developer workflows --Using specs to align product, engineering, and AI-assisted development --Real-world examples of turning specs into implementations with confidence Whether you’re building greenfield systems, integrating AI into your stack, or trying to reduce costly rework, spec-driven development offers a scalable way to move faster without sacrificing clarity. Attendees will leave with concrete patterns and a clear mental model for adopting GitHub Spec-Kit in their own projects.