Hi, i'm mustafa

I am a software engineer working remotely, and most of what I build is cross-platform: a Flutter app in front, a service behind it, and a database I designed rather than inherited. I like holding all three at once — the screen someone taps, the request it makes, the table that answers it — because the failures that cost real time almost never sit inside one of those. They sit in the seams between them. Increasingly there is a model somewhere in the middle, doing work a person used to do by hand, and the part I find genuinely interesting is deciding what it should never be allowed to decide alone.I am a software engineer working remotely, and most of what I build is cross-platform: a Flutter app in front, a service behind it, and a database I designed rather than inherited. I like holding all three at once — the screen someone taps, the request it makes, the table that answers it — because the failures that cost real time almost never sit inside one of those. They sit in the seams between them. Increasingly there is a model somewhere in the middle, doing work a person used to do by hand, and the part I find genuinely interesting is deciding what it should never be allowed to decide alone.