Education

Thesis FAQ and key guidance

A short orientation page for thesis work, practical expectations, and the most important things to know before starting.

Before starting

Choose a topic that is narrow enough to finish well, but meaningful enough to demonstrate real engineering or research value.
Clarify the expected outcome early: literature review, prototype, experiment, software artifact, dataset, or system integration.
Agree on the language of the work and presentation in advance, especially if the topic is developed in both Hungarian and English contexts.
Start collecting references from the beginning so the final writing phase is not separated from the technical work.

Keep progress visible through short updates, versioned files, and clearly named milestones.
Bring partial drafts early. It is much easier to improve a rough chapter or prototype than to repair a full late-stage submission.
Document decisions, assumptions, and open questions while working, not only at the end.
When software is involved, keep the repository runnable and reproducible so evaluation and continuation stay straightforward.

The written thesis should explain the problem, context, method, implementation, evaluation, and conclusions in a coherent structure.
Figures, tables, and experimental results should support the argument, not just decorate it.
Code, experiments, and references should be organized so another person can understand what was done and why.
A strong thesis shows both technical execution and reflective thinking about limitations, tradeoffs, and future work.

Do not leave writing to the final weeks. Write continuously alongside the implementation.
Make the scope realistic. A finished and well-evaluated smaller system is better than an oversized unfinished one.
Back up everything: text, code, figures, data, and notes.
Ask questions early when something is unclear. Small uncertainties tend to become large delays if they remain implicit.