Returning to Orlando Code Camp

Orlando Code Camp will always be special to me.

For around ten years, I helped lead the Orlando .NET User Group and organize Orlando Code Camp. That community shaped a big part of my professional life. It gave me a place to learn, teach, meet people, test ideas, and stay connected to the developer ecosystem in a way that no online platform could fully replace. So getting to come back and speak there again felt different from a normal conference session.

A lot has changed since the earlier days of Code Camp. The tools are different. The platforms are different. The way developers learn is different. Cloud is now the default for most modern teams. Open source won. DevOps moved from buzzword to baseline expectation. And now AI is changing the way we write, review, test, deploy, and maintain software.

But the most important part of the developer community has not changed. People still need places to learn together. That matters even more now.

AI tools like GitHub Copilot can help developers move faster. They can explain unfamiliar code, suggest implementations, generate tests, help troubleshoot errors, and make it easier to get started with new frameworks or platforms. That is powerful. But speed by itself is not the same thing as growth.

Developers still need judgment. They still need fundamentals. They still need people who can explain not just what a tool does, but why a pattern matters. They still need to see how others approach problems. They still need community. That was the part I kept thinking about as I prepared for Orlando Code Camp this year.

My session focused on GitHub, modern software delivery, and how developers can move faster with the right platform and practices. But underneath the technical content was a bigger message: the way we build software is changing, and developer communities have an important role to play in helping people navigate that change. It is easy to look at AI-assisted development and assume the future is just about individual productivity. One developer, one assistant, more code. But that is too small of a view. The real opportunity is helping teams build better software systems. That means better workflows, better automation, better security, better review practices, better deployment paths, and better ways to share knowledge. GitHub sits right in the middle of that conversation because it is where so much of the software delivery lifecycle already comes together.

Source control is there. Pull requests are there. Automation is there. Security scanning is there. Deployment workflows are there. Increasingly, AI-assisted development is there too. That is why I keep coming back to this idea: GitHub is not just where code lives anymore. It is becoming the place where modern software delivery is coordinated. For me, talking about that at Orlando Code Camp felt like a full-circle moment.

The community that helped shape me as a developer and leader is now part of the same conversation that is reshaping software development everywhere. How do we use AI responsibly? How do we help teams move faster without creating chaos? How do we teach fundamentals when tools can generate so much of the syntax? How do we make sure developers are not just producing more code, but building better systems?

Those are not questions that get answered by tools alone. They get answered in talks, hallway conversations, workshops, meetups, open source projects, mentoring, and communities like Orlando Code Camp. That is why I still believe community matters.

The tools will keep changing. The platforms will keep evolving. The way we build software will keep getting more interesting. But developers still need each other.

And I am grateful that Orlando Code Camp continues to be one of those places where that can happen. See you next year!

Scroll to Top