Remember those days? Indie game dev was the obsession. Pixel art, late nights coding... building worlds, brick by digital brick. Game development had that magnetic pull. Creative sandbox meets hardcore engineering. Felt like pure creation.
Then reality nudges you. Priorities shift. Gamepads get swapped for keyboards. Hello, JavaScript.
Building web apps? Yeah, they solve real-world problems. No doubt about it. But something felt...different. Missed that raw spark from game dev. That constant loop: art meets engineering, rapid iterations, problem-solving on the fly. Sculpting a model in Blender, then diving deep to optimize performance. That dynamic tension.
Started seeing the web in a new light. Not just static pages anymore. Tools like Three.js cracked it open. Interactive experiences. Dynamic canvases. The web, totally redefined.
And then the term dropped: "Design Engineer." Felt like a lightning bolt. Finally, a label for that hybrid skillset I was gravitating towards.
Design Engineering? It's the endless iteration cycle. It's the tightrope walk between visual finesse and technical grunt work. It's laser-focused on the experience. Building meets art. Performance meets pixel-perfect detail.
This journey? It's live. Always learning. But every line of code, every UI tweak, it’s about building right at that intersection. Art and engineering. Converged. That's the sweet spot.