Fundamentals: control flow, methods, tracing
The half that decides if you pass. Tracing, off-by-ones, scope and array logic. Doable with steady practice.
- Tracing
- Loops
- Arrays
- Methods
- Recursion
- Strings
PROGRAMMING I · EXAM PREP · 1:1
Four to five sessions before the exam. We work through past papers, close the gaps on OOP, inheritance and methods, and teach you how to attack tasks you have never seen before.
Dennis LIVE Senior Java Engineer · Programming I tutor responds ≤ 4 h Free first conversation →
Already decided? Straight to a session →
Past-paper trace, live
// trace exercise: what does this print? int n = 5; for (int i = 1; i <= n; i++) { if (i % 2 == 0) continue; System.out.print(i + " "); }
Six task archetypes that show up in almost every Programming I exam. We train each one separately, until you stop thinking and just type.
What is in s after the loop runs?
public class Tier { private String name; private int alter; // ... public String laut() { // ? } }
// Complete equals() correctly: public boolean equals(Object o) { if (this == o) return true; if (o == null || _______ != o.getClass()) return false; Person p = _______; return alter == p.alter && _______; }
Exception in thread "main" java.lang.NullPointerException at Person.equals(Person.java:17) at App.main(App.java:9) → What is in name? → Who is calling .equals()?
Most German universities split Programming I exams into a fundamentals block (Java syntax, control flow, tracing) and an OOP block (classes, inheritance, polymorphism). The split below mirrors a typical Klausur, including the past papers we coach against.
The half that decides if you pass. Tracing, off-by-ones, scope and array logic. Doable with steady practice.
The half that decides your grade. Inheritance, polymorphism, abstract classes and interfaces. The classic stumbling block.
If you start now and invest 4 to 5 sessions, you have a real chance. Less time? We compress. More? We go deeper, e.g. into generics or your own data structures.
You share your screen, we walk through your last exercise and your exam material. We see where you really stand, not where you think you stand.
We train what shows up in part 1 of every exam: reading methods, code tracing, loop logic. You type, we ask.
The hardest block. Classes, inheritance, polymorphism, equals/hashCode, on the actual material from your course. We build a mini model together.
You solve your university's past paper under time pressure. We discuss each task: what you nailed, where you spun out, and which types are likely to come back.
I built Study IT because I have seen first-hand how computer-science teaching at university falls apart.
Our tutors are working developers, not student side-jobbers.
Reach me directly: marcel.schmidtpeter@study-it.education
Ausbildung zum Fachinformatiker, dann Softwareentwicklung in der Industrie. Er weiß, was Prüfer:innen erwarten und wo Erstis bei OOP, Datenstrukturen und Algorithmen stolpern.
„Programmieren versteht man, wenn man weiß, warum eine Lösung funktioniert. Mein Ziel: dass du Code nicht abschreibst, sondern selbst hinkriegst."
Pay per session or grab the exam package. First chat is free, if it does not fit you have lost nothing.
If your exam is not the bottleneck, one of these probably fits better.
15 min talk, then decide. If we cannot help you, we tell you straight.