The Beginning
I built my first PC when I was 11. Naturally, the first thing I did with it was play Minecraft. Not the Java edition kids play today with shaders and RTX lighting — I'm talking about the era where 16x16 textures were the standard and your render distance was a suggestion at best.
At some point, I stumbled across resource packs. Someone had completely retextured the game to look like a medieval RPG, and it blew my mind. The cobblestone actually looked like cobblestone. The swords looked sharp. The UI was custom. It was the same game, but it felt entirely different. I remember thinking: “Wait, you can just... change how the game looks? And people just do this for free?”
That was the moment. I didn't know it yet, but that curiosity — that need to understand how someone pulled that off — would set the trajectory for everything that came after.
Making My Own
By 14, I wasn't just using other people's packs anymore. I was making my own. It started simple — I wanted to change the look of diamond ore because the default texture was ugly to me. So I opened up the pack files, found the texture, and started editing it in Photoshop.
That one texture turned into ten. Then twenty. Then I was retexturing entire biomes. I learned about UV mapping for 3D block models, figured out how JSON configs controlled which texture went where, and spent hours tweaking individual pixels until they looked right at 16x16 resolution. If you've never tried to make a convincing wood grain in a 16-pixel square, trust me — it's an exercise in patience and obsession.
The obsession was real. I'd stay up way too late adjusting the hue on a grass block by two degrees because it didn't blend right with the dirt texture next to it. I was doing digital art, file management, and config editing all at once, and I had no idea I was learning actual skills. It was just fun.
The Rabbit Hole
Here's the thing nobody tells you about resource packs: they're secretly a crash course in software development. You just don't realize it because you're having too much fun.
File structures? I learned those navigating assets/minecraft/textures/block/ directories. JSON? Learned it by writing model definitions and blockstate files. Image manipulation and color theory? Learned those making textures that actually looked good together. Understanding how a rendering engine interprets assets? Learned that by debugging why my custom models showed up inside-out in game.
None of this felt like “learning to code.” It felt like modding a video game. But every single one of those skills transferred directly into real development later. The file system intuition, the comfort with config files, the understanding that software is just layers of abstraction — all of it came from making block textures for a game about punching trees.
From Pixels to Code
At some point, changing how the game looked wasn't enough. I wanted to change how it worked. Resource packs could retexture and remodel, but they couldn't add new mechanics or change game behavior. For that, you needed mods and plugins. And for those, you needed to actually write code.
The jump felt natural. I already understood the game's file structure, I was comfortable with JSON and config files, and I had the same obsessive drive to get things exactly right. The transition from “I want this block to look different” to “I want this block to behave differently” was a straight line.
What I didn't expect was how perfectly the mindset transferred. That pixel-level attention to detail? It's the same thing as debugging code line by line. The patience to iterate on a texture until it's right? Same patience you need to refactor a function until it's clean. Resource packs taught me to be obsessive about craft, and that's honestly the most important skill in development. Not syntax, not frameworks — the willingness to care about the details nobody else notices.
Full Circle
That same creative obsession that had me tweaking grass textures at 2 AM is the exact same energy I bring to everything I build now. Interactive web experiences where every animation has to feel just right. Trading systems where every millisecond of latency matters. Creative coding projects where I'm pushing pixels around a screen, except now the canvas is a browser and the pixels are divs.
The path from digital art in middle school to media communications in high school to Interactive Development at RIT — it all traces back to that moment I opened a resource pack and thought “I could do this myself.” Every step was just the next logical thing to be obsessed with.
And honestly, with tools like Claude Code and AI agents, the game is changing again. The same way resource packs let one person completely transform a game's visuals, AI lets one developer build what used to take a whole team. The tools evolve, but the obsession stays the same. Find something you care about, go absurdly deep, and let that momentum carry you to the next thing. That's the whole playbook.