Cory Gideon
CE Engineering Manager at Wellabe, Inc
Des Moines, Iowa, United States
Actions
I have been in engineering for 15 years, most of which has been in consulting. I have had the privilege to speak at conferences around the globe, and it has been my passion to share what I’ve learned during my career and share ideas with others.
Links
Area of Expertise
Topics
Lego bricks for the web: The Microfrontend Approach
Modern web apps start small, and quickly grow into monolithic nightmares, making things increasingly difficult to maintain, scale, and evolve. Microfrontends address this challenge by breaking applications into smaller, independent pieces that fit together like Lego bricks.
In this session, we'll explore the microftontend architecture through the lens of modern .NET and Blazor applications. You'll learn how to decompose larger user interfaces into modular features, enable teams to work independently, and deliver updates without impacting the entire application. We'll cover the benefits, tradeoffs, and real-world considerations of adopting a microfrontend strategy, along with practical patterns for implementation.
What Attendees Will Learn
- What microfrontends are and when they make sense
- How microfrontends differ from traditional frontend architectures
- Techniques for building modular, composable UI experiences
- Strategies for team ownership and independent deployment
- Common challenges, including routing, shared state, and styling
- Practical patterns for implementing microfrontends with Blazor and .NET
- Lessons learned from adopting a microfrontend architecture in real-world applications
PixelForge: Lessons from Building a Game Engine in C#
Game engines power the experiences we enjoy every day, but what does it actually take to build one from scratch? As developers, we often use frameworks and engines as black boxes, rarely stopping to explore the systems that make them work.
In this session, I'll share my journey building PixelForge, a custom game engine written in C#. We'll dive into the core building blocks of a game engine, including rendering, game loops, input handling, asset management, and object lifecycles. More importantly, we'll explore the design decisions, mistakes, and lessons learned along the way.
Whether you're interested in game development, software architecture, or simply enjoy building things from the ground up, this session offers a practical look at how complex systems come together and what you can learn by creating one yourself.
What Attendees Will Learn
- The fundamental components of a game engine
- How rendering, input, and game loops work together
- Common architectural patterns used in game development
- Tradeoffs encountered when designing engine subsystems
- Performance and maintainability considerations in C#
- Lessons learned from building a complex system from scratch
When building your own engine makes sense and when existing engines are the better choice
Radish: Lessons from Building an In-Memory Store
Engineers are notorious for reinventing the wheel. Sometimes there's a legitimate need for custom functionality. Sometimes we believe we can improve on what's already available. And sometimes we're just curious how things work under the hood.
Curiosity was the motivation behind Radish, a simplified Redis clone written in Python. I'll walk through why I decided to build it and share the key lessons, challenges, and insights I gained from the experience.
What Attendees Will Learn
The core concepts behind in-memory key-value stores
How systems like Redis manage data and performance
Design tradeoffs involved in building infrastructure software
Common challenges encountered when implementing data structures, persistence, and networking
Practical lessons learned from developing a Redis-inspired system from scratch
When building something yourself is worth the effort, and when it's better to leverage existing solutions
Cory Gideon
CE Engineering Manager at Wellabe, Inc
Des Moines, Iowa, United States
Links
Actions
Please note that Sessionize is not responsible for the accuracy or validity of the data provided by speakers. If you suspect this profile to be fake or spam, please let us know.
Jump to top