This commit is contained in:
2026-07-04 02:06:24 -07:00
parent 6e8907ebf6
commit 68dfdfa33b
20 changed files with 564 additions and 19 deletions
+3 -5
View File
@@ -1,11 +1,9 @@
---
title: About
description: Who we are and why we're building in public.
description: Who I am and why I'm building in public.
draft: true
---
**Codegirl Games** is a game studio and content company with a simple mission: build and release affordable, full-feature games while teaching others how game development actually works.
**Codegirl Games** is a place with a simple mission: build full-feature games while showing others lessons I learned along the way.
We're not pretending to have all the answers. We're learning in public comparing languages on the same project, applying patterns from books like *Game Programming Patterns*, and building a game engine through trial and error.
If you want honest process over polished marketing, you're in the right place.
I'm not pretending to have all the answers. I'm learning in public: comparing languages on the same project, applying patterns from books like _Game Programming Patterns_, and building a game engine through trial and error.
+1 -1
View File
@@ -4,4 +4,4 @@ description: Devlogs, lessons, language comparisons, videos, and book reviews.
draft: true
---
Tutorials, devlogs, and experiments from our game development journey.
Tutorials, devlogs, and experiments from my game development journey.
@@ -1,6 +1,6 @@
---
title: "Game Programming Patterns — first impressions"
description: A book review of Robert Nystrom's Game Programming Patterns and how we'll use it in our projects.
description: A book review of Robert Nystrom's Game Programming Patterns and how I'll use it in my projects.
date: 2026-06-28
type: review
book: "Game Programming Patterns"
@@ -8,6 +8,6 @@ tags: ["patterns", "books"]
draft: true
---
*Game Programming Patterns* by Robert Nystrom is the reference we're using as we build. The patterns aren't abstract — we're applying them to real code in our tower defense and engine experiments.
*Game Programming Patterns* by Robert Nystrom is the reference I'm using as I build. The patterns aren't abstract — I'm applying them to real code in my tower defense and engine experiments.
Expect follow-up posts that map specific chapters to our codebase: State for unit AI, Object Pool for projectiles, and more.
Expect follow-up posts that map specific chapters to my codebase: State for unit AI, Object Pool for projectiles, and more.
@@ -1,6 +1,6 @@
---
title: "Why we're comparing languages on the same game"
description: Introducing our tower defense language comparison series — Odin, C, and C++.
title: "Why I'm comparing languages on the same game"
description: Introducing my tower defense language comparison series — Odin, C, and C++.
date: 2026-07-01
type: lesson
series: td-language-comparison
@@ -9,8 +9,8 @@ tags: ["odin", "c", "cpp", "tower-defense"]
draft: true
---
We're building the same tower defense game in multiple languages — starting with Odin, then C, then C++ — to compare what each language is actually like for game development.
I'm building the same tower defense game in multiple languages — starting with Odin, then C, then C++ — to compare what each language is actually like for game development.
This isn't a benchmark blog. We're documenting ergonomics, tooling, bugs, and the feeling of working in each language day to day.
This isn't a benchmark blog. I'm documenting ergonomics, tooling, bugs, and the feeling of working in each language day to day.
More posts in this series coming soon.