10 Practical Tips for IT Thesis Defense & Committee Q&A

Why strong coders still fail defenses

Committees grade communication and evidence as much as raw code. Slides overloaded with text, brittle cloud-only demos, or hand-wavy security answers sink otherwise solid projects.

1–3 — Slides & story

• Use the 10/20/30 spirit: concise slides, rehearse timing, large fonts.
• Lead with problem → your solution → demo path; put architecture/ERD early.
• Replace paragraphs with diagrams; narrate the “why,” not only the “what.”

4–6 — Reliability

• Prefer localhost + Docker or a known-good machine over flaky Wi‑Fi.
• Keep a screen recording of the full happy path.
• Seed credible demo data (names, prices, images)—not “asdf” rows.

7–9 — Typical hard questions

• Why this stack? Answer with trade-offs: team skill, ecosystem, time-to-MVP, operational cost.
• Scale / performance? Acknowledge limits; discuss caching, indexing, pagination, async, horizontal scaling as future work.
• Security? Mention validation, auth storage (prefer HttpOnly cookies for refresh where appropriate), password hashing, HTTPS, basic OWASP awareness.

10 — When you truly do not know

Say you did not implement that path, restate what you did implement, and outline how you would research or measure it. Blustering erodes trust fast.