As I was working on porting the rotation matrices for the helios.math.transform library, I took a detour to formalize the underlying linear algebra. My goal was to move beyond treating the rotational part of the model matrix as just a black box and instead understand it from a coordinate system perspective.
Over the weekend, I focused on refactoring mat4 and vec3. Additionally, I've made some adjustments to my toolset.
import {SocialLinks} from "../../src/components/SocialLinks";
For a game engine, the first step isn’t rendering a scene or simulating complex physics - it’s laying the foundational bricks. This weekend, I eased dove headfirst into that foundation for my personal C++ engine project, Helios, and it was a fantastic journey through the nuances of modern C++ design.
My background is in the web world - I've spent years wrangling Java, JavaScript (and countless frameworks based on it), PHP (from Zend to Laravel over Symfony and self-written solution), and the closest I ever got to the metal was writing C, of which I thought it would give me a head start for a game engine project. In a way, it did: I wasn't scared of pointers. But it also gave me a false sense of security.
Hi everyone!
For years, my world has been one of software architecture and senior-level development, mainly focusing on integration of frontend systems into large scale web applications. I’ve designed systems, worked with teams of various sizes, and treated software development as a true craft. But sometimes, a single problem can change your entire perspective. For me, that was Day 15 of Advent of Code in 2024.