The project I practised JavaScript with.
A small inventory dashboard: add products, change stock with + and −, and search, filter and sort the list. Built with HTML, CSS and plain JavaScript while I was learning the language.
Game design taught me how things should feel. Software engineering is teaching me how to make them hold.
Emir Şeren
Click it, then ←→↑
(00)PracticeHow I learn
I learn software by building1 things, breaking2 them, and understanding3 why they work.
- 1Small projects with a clear goal. StockFlow is how I practised JavaScript.
- 2Bugs teach me the most. I try to find the cause before I change anything.
- 3I want to know what the code I use is doing, including code written with AI tools.
I’m working toward full-stack development one step at a time: JavaScript first, then TypeScript, React and the back end. Along the way I care about the parts people skip — the empty state, the error message, the focus ring.
Things I’m picky about
- Kerning in buttons
- Loading states
- Focus rings
- Naming things
- The 8 pixels nobody measured
(01)Selected workInteractive mockups
Four projects and a playground.
These are projects I’ve worked on while learning software development. Each preview below is a simplified re-creation of the real app, running on sample data — try them.
What a larger full-stack app looks like.
An AI-assisted full-stack issue and sprint tracker with projects, roles, authentication, Kanban workflows, comments, activity feeds, testing and deployment.
Your data stays in your browser.
Upload your own Instagram data export and see who doesn’t follow you back, who you don’t follow back, and your mutuals. Everything is processed locally — no login, no scraping, no upload.
Charts, indicators and backtests on the desktop.
A Windows desktop app for technical analysis of Binance USDT-M futures, using public market data with no API key: charts, indicators, trade setups, backtesting and desktop notifications.
(02)AboutGame design → software
Translation, not a restart.
I study Digital Game Design, with full-stack development as my goal.
People sometimes ask whether that makes the degree a detour. I don’t think so. A lot of what I learned designing games carries over to building software — I’m learning the new names for it, and the tools that go with them.
In game designIn softwareWhat carries over
Systems designArchitectureRules that interact without breaking each other.
PlaytestingUser testing & debuggingWatching someone struggle with your thing, and not explaining it to them.
Game feelInteraction designTiming, feedback, response. The gap between “works” and “feels right”.
Level pacingInformation flowWhat someone sees first, what they learn next, and when.
PrototypingIterationMake it ugly, make it work, then make it good. In that order.
BalancingTrade-offsEvery number you change moves three others.
(02.1)Rules I work by
- R01Make it work. Make it clear. Then make it fast.
- R02Every state gets designed: empty, loading, error, done.
- R03Motion should explain something, or it should go.
- R04Name things for the next person. Usually that’s me.
(02.2)NowAutumn 2026
- Studying
- Digital Game Design, at university.
- Learning
- TypeScript, now that the JavaScript fundamentals are done.
- Looking for
- An internship in software development.
(02.3)ToolkitCurrent skills first
What I use now, and what I’m learning next.
A
Using now
What I build with today.
- HTML
- CSS
- JavaScript
- Git
- GitHub
B
Learning next
In this order, after JavaScript. Not skills yet.
- TypeScript
- React
- Testing
- Node.js / Express
- SQL / PostgreSQL
- Next.js
- Docker / deployment
C
AI-assisted workflow
Tools I work with, not languages.
- Claude
- Cursor
- Codex
- Antigravity
D
Game design background
Ways of thinking that carry over.
- Systems thinking
- Prototyping
- Playtesting
- Interaction thinking
On AI-assisted development
I use AI tools to explore ideas, debug faster, and learn from the code I’m building.
(03)PlaygroundExperiments, small on purpose
Rules, weight and timing.
Game design taught me that how something feels is a set of numbers someone chose. This is where I choose them on purpose.
E.00
Game feel lab
The square from the top of the page runs on a tiny physics engine I wrote for this site. These are its settings. Change them, and it changes up there too.
Coyote time
A few frames of grace after you run off a ledge, where jump still works. Players never notice it. They notice when it’s gone.
Jump buffering
Press jump a moment before you land and it still counts. Without it, the game feels like it’s ignoring you.
Squash & stretch
Pure illusion — the hitbox never changes shape. But it’s what makes a square feel like it has weight.
(04)Contact
Your move
I’m open to internship opportunities in software development. I’m also happy to talk about a project, a game mechanic, or an interface that bugs you.