About Me
Engineer by profession, game developer by curiosity.
Nicolai Andreas Alexander Scheerer
> aka. "FoorFex"
I hold a bachelor’s degree in Electrical Engineering and Information Technology and work as a technical consultant in the industrial automation field.
Game development is my creative hobby: a place where I can combine technical problem-solving with gameplay ideas, art, sound, and the challenge of turning small concepts into working experiences.
As a father, my development time is limited, so progress often comes in small steps. I am not racing toward the finish line. I enjoy the journey of learning, experimenting, and becoming a more capable solo developer with every project.
// SOLO DEV LOADOUT
Skill Atlas
A living snapshot of what I can do, what proves it, and where I am heading next. Open a discipline to inspect the build.
ProgrammingTurning game ideas into reliable, readable systems.Building · 2/53 project proofs
Object-oriented design and testable game architecture
Refactor a prototype into tested, loosely coupled gameplay systems.
Game DesignShaping mechanics, rules, feedback, and player decisions.Building · 2/52 project proofs
Prototyping mechanics around a clear player experience
Build and playtest one mechanic through three documented iterations.
Visual ArtCreating the visual language that makes a game readable.Exploring · 1/5Proof in progress
Shape language, composition, and a repeatable Blender workflow
No published project evidence yet — this is intentionally rated Exploring.
Create a small modular environment kit and use it in one playable scene.
Audio & MusicSupporting mood, feedback, and rhythm through sound.Exploring · 1/5Proof in progress
Interactive audio fundamentals and purposeful game feedback
No published project evidence yet — this is intentionally rated Exploring.
Design and implement a complete audio pass for one prototype.
ProductionKeeping a solo project scoped, documented, and moving.Building · 2/52 project proofs
Small milestones, ruthless scope control, and useful postmortems
Ship a four-week project with a public roadmap and retrospective.
DeploymentGetting builds out of the editor and into people’s hands.Building · 2/52 project proofs
Automated builds, environment configuration, and observability
Create a CI pipeline that tests, builds, and deploys on every release.