#architecture
12 posts
-
· 6 min
Bloom & Place devlog #1: why I'm building it
My final-year project is a casual puzzle game, but the real subject is loosely coupled architecture in Unity. Here's the pain that started it.
-
· 5 min
Bloom & Place devlog #2: the baseline I'm trying to beat
Before refactoring anything, I measured the prototype's coupling. Here are the numbers I have to improve on, including the line of code I'm most embarrassed by.
-
· 5 min
Bloom & Place devlog #3: a 1968 problem still eating Unity codebases
Constantine named coupling and cohesion before most game engines existed. Sixty years on, Unity projects keep rediscovering the same trap.
-
· 6 min
Bloom & Place devlog #4: dependency injection without the enterprise smell
DI has a Java-and-XML reputation in the Unity world. Strip the framework theatre away and what's left is a small, mechanical pattern that earns its keep.
-
· 5 min
Bloom & Place devlog #5: events as the runtime glue
DI tells systems who their dependencies are at construction. It says nothing about who they should talk to at runtime. That's what events are for.
-
· 5 min
Bloom & Place devlog #6: why VContainer (and not Zenject)
There are real DI frameworks for Unity. I picked the one whose pitch matches what I want the architecture to do, not the one with the biggest tutorial library.
-
· 5 min
Bloom & Place devlog #7: the yardstick, Ce, Ca, and instability
Three metrics from Robert Martin, one formula, and the discipline that keeps the formula honest.
-
· 5 min
Bloom & Place devlog #8: why Waterfall, not Agile
Picking Waterfall in 2026 sounds like a punchline. For an architecture-first thesis with metrics defined upfront, it's the model that fits.
-
· 5 min
Bloom & Place devlog #9: solution shape and the Waterfall plan
With the literature review done, the design phase opens. Here's the shape of the solution and the five-phase Waterfall plan I'm running it on.
-
· 7 min
Bloom & Place devlog #10: layers and the dependency graph
Where every system sits, what depends on what, and the before/after picture of what VContainer plus events actually changes.
-
· 6 min
Bloom & Place devlog #11: bindings and event flow
How every system gets registered with VContainer, why each lifetime was picked, and the seven events that carry runtime communication.
-
· 6 min
Bloom & Place devlog #12: interface contracts and the test plan
The interfaces two programmers agreed on before either wrote any code, plus the test plan that turns the architecture claim into a measurable outcome.