Lineage

Chapter One

The Journey Begins

I started as a mathematics student. Patterns, logic, proofs—I loved the moment an ugly problem folds flat and becomes obvious. That instinct for how things work underneath is the foundation everything else stands on.

Then I discovered I loved explaining it. Tutoring taught me that teaching is not transferring information; it is engineering the “aha” moment on purpose, for people who walked in convinced they were bad at math. Clarity, patience, no jargon—that habit runs through every project I touch.

Chapter Two

Into the Digital Realm

Then I learned to code, and the math stood up and started walking around. I went into corporate data analytics, where the datasets are massive, the stakes are real, and someone always needs the answer by Thursday.

Data taught me a suspicious mind: what does this number actually mean, and who is it lying to? I got good at spotting the pattern nobody else saw and, harder, explaining it so a room of busy people would act on it.

Chapter Three

Creating Worlds

Then came games, where everything I owned—math, code, design—went into one cauldron. I built Story Time, a turn-based strategy game with over 40 characters, then Clash of History, Animas, and the rest of the Exhibits.

Games taught me polish the hard way: every mechanic, animation and sound either serves the player or annoys them. There is no third option. Then someone plays your thing and says “one more turn,” and every late night is paid off.

Chapter Four

The Current Chapter

Which brings us to now: solving technology problems for anyone who walks up the tower stairs. Data analytics, games, websites, teaching—whatever the challenge.

Math student, tutor, data analyst, game developer. That path leaves an odd but useful toolkit: the theory under the code, the data under the decision, and the craft that makes software pleasant instead of merely functional. If you need any of it, let’s talk.

The Creed

The Philosophy

Technology should serve creativity, not sit on it. Data should tell stories, not molder in spreadsheets. A website should be a place, not a filing cabinet with a logo. And a good game follows you home.

Three principles guide every project:

• Craftsmanship: Quality code, polished design, details fussed over
• Clarity: Every element earns its place or gets escorted out
• Impact: Work that matters and helps someone

To Be Continued

The Next Chapter

The story keeps unfolding. Chapter Seven has a blank space in it, roughly the shape of your project.