Egemen Soylu / Software engineer + creative technologist
I build systems, software, images and sound.
Engineering depth and creative practice, treated as one body of work — from enterprise data systems and modern backend architecture to moving image, creative code and music.
01 / Selected work
Different media. Same urge to make.
Selected public work across systems, moving image, music and experimentation. Engineering work appears here only when the publication boundary is clear and the project says something useful about how I work.
Debian Workstation Setup
A modular, Debian-first workstation bootstrap: small shell scripts, explicit package groups and reusable configuration instead of one opaque provisioning blob.
Petri Modeling Studio
A local-first visual modeling environment built around framework-independent TypeScript cores, Petri-net and state-machine plugins, deterministic simulation, analysis and browser/desktop editor surfaces.
Hiç / Nothing
A spoken-word piece built from writing, voice, rhythm and an abstract audiovisual landscape — somewhere between poetry, music and motion design.
Duygu Soylu — Kör Kuyu
A character-led AI-assisted music video: visual development, generated source imagery and image-to-video material shaped into a finished edit for Duygu Soylu.
Mesaj / Message
An early AI-assisted music-video experiment: generated character and scene imagery developed into moving sequences, then selected and edited into a coherent visual world for Duygu Soylu.
Tek Yol Müzik
An earlier kinetic-typography piece for the intro of a rap track, exploring gravity-like motion in After Effects without a dedicated physics plugin.
02 / Engineering
Tools change. Engineering judgment compounds.
I do not divide my career into an embarrassing “legacy” chapter and a fashionable “modern” one. The technologies changed; the underlying work — data, boundaries, failure modes, delivery and maintainability — kept accumulating.
- Enterprise systems
Oracle, PL/SQL, Forms & Reports
Data-heavy business applications, relational modeling, stored procedures, reporting and systems where correctness matters because people actually run their work through them.
- Backend & distributed systems
Python, APIs, services and operational thinking
Backend engineering expanded the same concerns across service boundaries: interfaces, queues, performance, observability, failure handling and systems that need to keep behaving after deployment.
- Product engineering
TypeScript, SQL, infrastructure and end-to-end systems
Modern product work spans application architecture, PostgreSQL, Node.js/TypeScript, containers, cloud-oriented delivery, telemetry and the product decisions around the code — not only the code itself.
03 / Studio
The other half is not a sidebar.
Music, motion and visual experiments use many of the same muscles as engineering: structure, iteration, technical curiosity and the patience to make an idea concrete.
Moving image
Music & sound
Creative technology
04 / Working method
Understand the system. Then make the thing.
I tend to work from the whole system inward: understand the problem, expose assumptions, model the important parts, decide what must stay simple, then build and test the smallest version that proves the idea.
That approach applies whether the output is a backend service, a product workflow, an audiovisual piece or an experiment that may never become a product at all.
- Evidence over labels. Show the work instead of ranking skills with percentages.
- Constraints are design material. Legacy, performance, cost and operations shape the solution.
- Build for reality. Deployment, failure and maintenance are part of engineering.
- Keep room for play. Experiments are allowed to exist before they become useful.
05 / Contact
Have a concrete problem worth building around?
Software engineering, architecture, technical leadership, product work or a creative-technology project: the useful starting point is the problem and its constraints, not a list of buzzwords.