Robotics and electronics
They let me see how sensing, motion, energy and control relate to one another.
How robotics, coding, electronics and sport connect to my learning, and the steps I work through when I study something.
Robotics, coding and electronics interest me because an idea does not stay in my head; it becomes something I can measure, test and improve. Cycling, basketball and swimming show that rhythm, repetition, balance and recovery matter not only in sport but also in learning.
This site is not a résumé that exaggerates completed achievements. Inside it there are learning routes, safe project guides, programme and occupation research, quizzes and opportunities, in Turkish and English. On this page I describe honestly the learning approach behind them.
When I publish something here I say plainly whether it is personal experience, a teaching example, a guide or a project record. The presence of a project guide in the Academy does not mean that I completed that project. Liking a subject does not make a lesson correct either; a lesson is only as good as its sources and testing. The reverse holds too: a lesson being on this site does not prove I am competent in that field.
I gained a place in the Electrical and Electronics programme at Kıraç Borsa İstanbul Mesleki ve Teknik Anadolu Lisesi, a vocational and technical Anatolian high school, and my enrolment has been completed. What I publish is limited to the name of the school and the name of the programme; beyond that I do not publish personal document details, the school address or a daily schedule. Detail: Education Journey.
They let me see how sensing, motion, energy and control relate to one another.
They teach me to break a problem into steps, test it and explain what went wrong.
They strengthen rhythm, repetition, recovery and the idea of sustainable progress.
They require me to check sources, explain things clearly and say plainly where I do not know.
For me, learning is not complete after watching a video or reading a page. The topic needs to connect to a real question, become a small application, produce errors and be tried again after feedback.
| Step | What I ask myself | What I am left with |
|---|---|---|
| 1. Be curious | What is the real problem here? | The question I wrote in my own words |
| 2. Break it down | What smaller parts make up the problem? | A list of the steps, inputs, outputs and limits |
| 3. Build | What is the smallest working or understandable example? | Code, circuit, sketch, table or explanation |
| 4. Test | Where do expectation and reality differ? | The test result and the note I keep on what failed |
| 5. Revise | What changed after feedback? | The second version, and what I changed |
| 6. Share | Can another person understand and repeat the method? | Sources, explanation and safety boundary |
In the short term I want to make small things regularly and write down what each one taught me. In the medium term I want to connect different school subjects inside one project. Further on I want to think about accessibility, safety, ethics and real user needs alongside what I build.
These are not promises about a particular occupation, school or result; my interests can change over time. Before asking “What will I become?”, I ask which problems increase my curiosity and persistence while I work on them.
Which schools I went to and how my way of learning changed each time.
Open my school years →The difference between guides, examples, work logs and a personal project record.
Open the projects →A way to record errors, feedback and second versions.
Open the journal template →Habits I carry from cycling, basketball and swimming into learning.
Open the sport approach →