About Me
I am an undergraduate in the Control and Automation Engineering programme at Istanbul Technical University. I came to the field from the hardware side — taking apart motors and power supplies long before I could write the differential equations that describe them — and that order has shaped how I work ever since. I like a model best when I can measure how badly it disagrees with the bench.
What I Work On
Most of my time goes to three related things. The first is control: building plant models, designing compensators, and then discretising them so they survive a fixed-point or floating-point microcontroller with a finite sample rate. The second is electronics: the amplifier, filter, driver and protection circuitry that stands between a controller and the physical world, which is where most projects actually fail. The third is software: firmware in C, analysis and tooling in Python and MATLAB, and robotics middleware under ROS.
How I Approach a Problem
- Model first, but cheaply. A first-order approximation with an honest uncertainty band is worth more early on than an elaborate model built from datasheet values nobody verified.
- Simulate before energising. Simulink and LTspice cost nothing to be wrong in. Burnt drivers and bent shafts do.
- Instrument everything. If a loop misbehaves on hardware, the logs should already contain the answer — setpoint, measurement, control effort and timing, captured every cycle.
- Fail safely. Watchdogs, current limits, end-stops and sane power-on states are part of the design, not additions after the first accident.
- Write it down. Schematics, tuning parameters and test conditions belong in version control alongside the code.
Beyond the Coursework
Since 2024 I have been part of the software sub-team of the ITU AUV Team, which designs and builds an autonomous underwater vehicle for international robotics competitions. Underwater work is an unusually honest teacher: sensors drift, communications are poor, buoyancy and drag couple the axes together, and nothing can be debugged interactively once the hull is sealed. It has taught me more about robustness and about integration with mechanical and electrical sub-teams than any single course could.
I also maintain a separate portfolio covering my game development and interactive software work. The engineering discipline behind both is the same — state machines, real-time loops, numerical stability and performance budgets — but the audience is different, so the two are kept apart.
Languages
| Language | Level |
|---|---|
| Turkish | Native |
| English | Professional working proficiency — technical reading, writing and presentation |