About
Building systems that measure energy loss and act on it
I am an inventor, researcher and software developer from Türkiye. My core work is a patented system that monitors energy loss in public buildings and responds to it. Around that sit competition engineering, research projects, and the writing that holds both together.
- Base
- Türkiye
- Languages
- Türkçe, English
- Focus
- Energy systems, hardware, software
- Working on
- Energy loss monitoring for public buildings
How I got here
I started from a problem I could point at. Public buildings — schools, public offices, municipal facilities — run all day under an institution’s budget rather than under one person’s attention. Energy is lost there quietly and continuously, and the usual answer stops at a report. I wanted detection and response to belong to the same system. That work became a registered Turkish patent, TR 2025 014583 B, granted in 2025, and it is still the project I judge the rest of my work against.
Taking it in front of juries taught me more than building it did. The same system was shown at Indonesia Inventors Day 2023 and at BUCA IMSEF 2023 in İzmir, where it took a bronze medal in engineering and energy, and it reached the finals of the TEKNOFEST Environment and Energy Technologies competition in 2024. Every jury asked a different version of the same question: what exactly did you measure, and what does that measurement not prove?
From there the work widened. I worked on TEKNOFEST Efficiency Challenge in 2024, on Flying Car Simulation in Northern Cyprus in 2025, and on Unmanned Underwater Systems in İstanbul in 2025, reaching the finals in each. In parallel I ran research projects under TÜBİTAK 2204-A: a psychology project that placed second in its regional round in 2024, and a technology and design project selected in 2025. Two eTwinning projects earned National Quality Labels. I also completed the Entrepreneurial Skills Pass with a score of 100%, along with the GençBizz and GençBizzTech programmes.
How I work
I design backwards from the failure case. Before deciding what a system should do well, I decide what it must not be allowed to do quietly: lose energy without leaving a record, report a fault nobody acts on, produce a number nobody can reproduce. Most of the architecture follows from that list.
Three habits carry across every project. Write the claim down before building anything, so it can be checked later. Instrument early, because a prototype that cannot be measured is an opinion. Keep what was observed separate from what was concluded, in reports and in conversation alike.
Competitions are useful here. A deadline forces a decision and a jury forces an explanation. Four TEKNOFEST finals and two seasons of the NASA International Space Apps Challenge, where our team was nominated as Galactic Problem Solver in 2024 and again in 2025, put that discipline on a schedule I do not control.
I usually work in a team, and I try to be the person who writes things down: the interface between two subsystems, the reason a part was chosen over another, the test that has not been run yet.
What comes next
The patent is registered; it is not installed. The next stretch of work is the ordinary part — turning a granted claim into a system that runs in a real building over a full season and produces evidence somebody else can audit. That is slower and less visible than a competition weekend, and it is the part that decides whether the idea was worth anything.
Beyond that, I want depth rather than breadth. The record so far spans energy, mobility, simulation and underwater systems, which is a fair map of what I can learn quickly and a poor map of what I know thoroughly. Narrowing is the next step, not adding.
And I intend to keep publishing method: what was attempted, what failed, and what the evidence actually supports. The projects, awards and patent sections of this site are where that is written down, and I am glad to discuss any of it in detail.
About
Areas of expertise
Energy and environmental systems
The line of work behind my patent and most of my competition entries: finding where energy is lost in an operated building or vehicle, and making the system do something about it.
- Energy loss monitoring in public buildings
- Monitoring linked to intervention, not only reporting
- Efficiency-driven vehicle work for TEKNOFEST Efficiency Challenge
- Environment and energy technology projects
Hardware and prototype engineering
Turning a written design into something that physically exists, survives a jury inspection, and can be operated on a competition field.
- Sensing and data collection hardware
- Electric vehicle subsystems
- Unmanned underwater system builds
- Bench testing and iteration between rounds
Software development
The software side of the same projects, from simulation models to applications built against a fixed deadline.
- Simulation work for TEKNOFEST Flying Car Simulation
- Application development under hackathon deadlines
- Data handling for monitoring systems
- Bilingual technical documentation
Research methods and scientific writing
Designing a study so that its result can be defended, and writing it up so that someone else can check it.
- TÜBİTAK 2204-A research project reports
- Psychology research design
- Patent drafting and filing with Türk Patent ve Marka Kurumu
- Presenting to juries in Turkish and English
Interests
Infrastructure nobody is watching
Buildings and facilities that run under an institution's budget rather than one person's attention, where losses accumulate without anyone noticing at the moment they occur.
Measurement before opinion
How a claim is actually supported: what was measured, under which conditions, and what the number does not prove.
Competition ecosystems
TEKNOFEST, TÜBİTAK 2204-A and NASA Space Apps as structures that impose deadlines, rules and a jury willing to argue with you.
People and technical systems
The behavioural side of engineering, which is what led me to run a psychology research project alongside the hardware work.
What I want the work to add up to
I want the systems I design to close their own loop: detect a problem and act on it, rather than filing it for someone else to read. That is the principle behind the patent, and I would like it to hold for everything I build after it. The measure of success is not a medal count but one installed system whose results a stranger can audit.
Goals
Take the patent from registration to installation
Move the energy loss monitoring and intervention system from a granted claim to a system running in a real public building, producing evidence that can be checked independently.
Near term
Go deeper in one engineering line
The competition record spans energy, mobility, simulation and underwater systems. I would rather finish one of those lines properly than start a fifth.
1-2 years
Publish method, not only results
Write up what was tried, what failed, and what the measurements actually support, so the work is useful to people who are not judging it.
Ongoing