top of page

Gabriel
Cruceanu

UNITY DEVELOPER, PROGRAMMER, GAMIFICATIONER

ABOUT ME

I have extensive experience in managing complex systems with steep learning curves and unforgiving accuracy requirements. My specialty is operating sophisticated equipment where every control has purpose and consequence. I've operated environments where managing 30+ individual systems simultaneously is baseline expectation. That's corporate language for saying I love playing and making games.
 
I've learned that shortcuts create disasters, checklist discipline prevents avoidable failures, and understanding your equipment's limitations prevents catastrophes. Performance under extremely high stress with permanent consequences is fundamental to my operations. I've learned, at times the hard way, that 20 minutes of preparation and steady progress can be lost in 0.4 seconds of inattention. That's corporate language for saying I'm committed to the work I do and ensure output is of high quality.
 
There's no pause button when things go wrong, mistakes have immediate and total consequences. After all, I've learned that staying calm when everything goes wrong is the only path forward.
 
One must simply imagine Sisyphus happy.

What else do you do?

I game. A lot. Mostly games that demand commitment. I'm a completionist at heart, chasing achievements and checking every corner of a map for any hidden collectible. Often the main story has to wait until I'm done with the side quests. An achievementaholic one may say. Or, more corporate buzzwords: achievement-driven, completion-brained, 100%-wired, progress-maxxing, achievement-pilled, etc. You can track my current obsession here.

Where do I see myself in 5 years?

Somewhere between a functional developer and a nuclear assault cavalry on a mutated toxic steed with WW2 era rifles.

Talk about my skills?

I'd rather show them directly.

How do I work?

If something fails, I point at it. If something works, I say so. Argue with the problem until it gives up. I poke things, break a few parts on purpose, put everything back together in a way that it finally stops screaming. If something collapses, I just sigh, fix it, pretend I meant to do that. Keep going until the system behaves out of fear, respect, or just exhaustion.

Whats a weakness I have?

I struggle pretending that a bad idea is good and cannot fake it. Sometimes I deliver high-impact deconstructive (not destructive!) criticism, and I have to remind myself to soften the landing so people don't think I'm starting a coup.

How do I handle stress?

I pretend I’ve been here before and convince myself it’s under control. Doesn't matter if I'm debugging, presenting, or dealing with a feature that refuses to live. I just imagine catastrophic failure is one keypress away. Somehow, it usually works.

What lesson took me some time to internalize?

Doing simple really fucking well is an art form.

Education

BSc Computer Games Development - First Class Honours - University of Northampton

Technical Skills

Languages: C#, JavaScript, PHP, HTML/CSS


Frameworks: Unity, Unreal Engine, Vue.js, BootstrapVue


Developer Tools: JetBrains Rider, VS Code, Visual Studio, SQLite​

​

Others that may be of interest: SQL, VR, AR,  MySQL, and many other things I experimented with

Contact
Saw something you like about my work, want to discuss a collaboration, or simply want to say hi?

GET IN TOUCH

bottom of page