Being selected for Team Albania for ECSC 2026 changes the way I train. A normal learning plan can stay inside one subject for weeks. A competition plan cannot. ECSC rewards teams that can move between web exploitation, binary analysis, cryptography, forensics, hardware, and incident response without losing momentum.
Training for coverage
My first goal is not to know every trick. It is to build a reliable process for unfamiliar problems. For each category I keep a short playbook: what to inspect first, which tools to reach for, and which assumptions to test before spending time on a complex path.
For web challenges, that means mapping trust boundaries, sessions, inputs, and server-side behavior. For binaries, it means checking protections, program flow, memory behavior, and the smallest controllable primitive. Crypto work starts with identifying what is custom, repeated, biased, or incorrectly composed.
The common idea is simple: reduce the unknowns before trying to be clever.
Speed comes from repetition
Competition speed is not frantic typing. It is recognition. I am building repetition through focused CTF sessions, short timed drills, and write-ups made immediately after solving a challenge. The write-up matters because it turns a one-time solution into a reusable mental model.
I also maintain scripts for repetitive work: decoding, packet inspection, common enumeration, and result formatting. Automation should remove mechanical steps, not replace understanding.
Preparing as a team
ECSC is a team competition, so communication is part of the technical work. A useful update states what was tested, what failed, what remains uncertain, and what another teammate can try. Clean notes prevent duplicated effort and make handoffs possible when a challenge crosses specialties.
My objective for 2026 is bigger than a placement. I want to arrive as a more complete security engineer: faster at forming hypotheses, calmer under pressure, and better at turning individual knowledge into team progress.