I am an Electrical & Electronics Engineering student at Bülent Ecevit University who builds hardware, writes low-level C and Rust software, and learns by going deeper than the first explanation.
My interests span both hardware and software. I do not want to limit myself to only one layer of a system—I want to understand how physical components, electronics, firmware, and higher-level software work together.
Right now, my active work centers on <strong>ESP32 / ESP32-S3 embedded systems in ESP-IDF (ISO C99 & FreeRTOS)</strong>, circuit analysis, KiCad schematic capture, Python hardware tooling, and Rust systems programming on Arch Linux.
I love open source, freedom, and making things that are useful, unusual, or simply fun. I use this website to document my progress, share real schematics and firmware, and connect with people who enjoy building and learning together.
<imgclass="zoomable-img"src="assets/images/hardware-software-bridge.svg"alt="Diagram showing three connected layers: Layer 1 Circuits and Electronics, Layer 2 Embedded and Low-Level C Programming, and Layer 3 Tools and Human Judgment."width="760"height="220">
<spanclass="section-label">02 // Hardware, Software & AI Philosophy</span>
<h2id="philosophy-heading">Why I Want to Understand Both Sides of a System</h2>
<divclass="callout-box amber">
<spanclass="callout-title">Core Principle</span>
<pstyle="margin-bottom:0;">
“I want to understand both hardware and software because I do not want to depend completely on tools or people who understand the parts I do not. My goal is to understand systems deeply enough to make decisions, guide AI effectively, recognize when something is wrong, and take responsibility for what I build.”
</p>
</div>
<h3>The Car Analogy</h3>
<p>
I often think about technology through a simple car analogy: if I want to drive a car responsibly, I should understand at least the basics of its steering, dynamics, brakes, and other important systems. If I understand how the car works and how to drive it, I can make good decisions, recognize problems early, teach someone else, and know what to ask for when something needs attention.
I approach AI in the exact same way. I use AI tools when experimenting, but I do not want to use AI blindly—I want to understand the hardware registers, pin strapping rules, and software architecture deeply enough to evaluate output critically and take full responsibility for the final system.