About
A software engineer who never really separated technical work from making things.
I started professional software work in the world of Oracle, PL/SQL, Forms and Reports: business systems where data models, correctness and operational reality mattered every day. My work later expanded into Python, backend services, distributed systems, TypeScript, product engineering and cloud-oriented delivery.
I do not see those as disconnected eras. The tools changed, but the useful habits accumulated: model the problem carefully, understand boundaries, make failure visible, keep systems operable and resist complexity that has not earned its place.
Alongside software I have kept making visual and musical work — motion experiments, video, generative imagery, writing, sound and pieces that sit between categories. That work is not here as decoration around an engineering résumé. It is another place where I use structure, iteration and technical curiosity.
I am based in Sweden and work comfortably in English and Turkish while continuing to improve my Swedish.
- System before component. Understand the surrounding problem before optimizing the local solution.
- Make decisions explicit. Trade-offs should survive beyond the meeting or coding session where they were made.
- Operations are part of design. Monitoring, failure, recovery and maintenance are not afterthoughts.
- Old does not mean irrelevant. Mature technologies often contain the hardest-earned engineering lessons.
- Experiments may stay experiments. Not every useful exploration needs to become a startup or product feature.