A Letter to a First-Year Computer Engineering Student

6 minute read

Published:

Dear first-year student,

Welcome. The 2026–27 academic year is starting, and you have chosen a field that changes faster than almost any other. That can feel exciting and frightening in the same week. I am writing as a teacher of computer engineering, and I want to say a few things that teachers often say too late, usually in the last lecture, when you can no longer use them.

You are here to build a way of thinking

The first thing to understand is that a degree is not a list of tools. Languages, frameworks and editors will change several times during your career. What stays is the ability to take a vague problem, break it into parts, reason about what can go wrong, and check your own answer.

That is why the early courses matter more than they look. A course like Computer Fundamentals and Introduction to Programming may feel basic, but it gives you the mental model of what a computer actually does: numbers in binary, instructions in order, memory that holds state. Everything later rests on it. If this layer is shaky, every later course feels like magic. If it is solid, later courses feel like variations on ideas you already know.

Why the fundamentals pay off

Students sometimes ask me whether they really need to study data structures when a library already provides a list, a map and a sorting function. My answer is yes, and the reason is not nostalgia.

A library hides the work, but it does not remove the trade-offs. Someone still has to decide whether to search through a list or look something up in a hash table, whether memory or speed is the scarcer resource, and why a program that is fast with a hundred records becomes unusable with a million. Data Structures and Algorithms teach you to ask those questions before they become emergencies. Operating systems teach a similar lesson about the machine underneath: processes, memory, files and scheduling are the reason your program behaves the way it does.

You will not use every topic directly in your first job. But engineers who understand fundamentals can learn a new tool in days, because they recognise the idea inside it. Engineers who only know the tool start again from zero every time it changes.

How to study so that it sticks

Most of us study in the way that feels productive: rereading notes, highlighting, copying a solution neatly. A well-known 2013 review of learning research by Dunlosky and colleagues compared ten common study techniques. It rated practice testing and distributed practice as the two with high utility, and it rated rereading and highlighting as low utility.

In plain words: test yourself, and spread your study over time. Close the book and try to write the algorithm from memory. Solve the exercise before you look at the answer. Do a little every day instead of everything the night before an exam. It feels harder, and that is the point; the effort is what builds the memory.

Two habits help a great deal. First, always run your code, and run it on bad input as well as good input. Second, when you get stuck, write down exactly what you expected and what happened. Half of all bugs are solved during that sentence.

Using AI tools without outsourcing your thinking

You are the first generation of students who will study with capable AI assistants available all the time. Used well, they are a patient tutor: they can explain an idea three different ways, suggest test cases, or point out a mistake in a program at midnight.

Used badly, they let you skip the very struggle that creates understanding. A simple rule works well. Try the problem yourself first, for a fixed amount of time. Then ask the tool for a hint, not the answer. When you receive code, do not paste it; read it line by line, and explain to yourself why each line is there. If you cannot explain it, you do not own it yet.

Also remember that these tools can be confidently wrong. You can only catch that if you understand the subject, and that is one more reason to learn the fundamentals. Exams, interviews and real engineering problems will all ask you to think without a prompt box. Practise that now, while mistakes are cheap.

Ask questions, and build small things

Many students stay silent because they think everyone else already understands. Almost always, they do not. A question you are embarrassed to ask is usually the question half the room is waiting for someone else to ask. Come to office hours, ask in class, and form a small study group where explaining things to each other is the main activity. Explaining is one of the fastest ways to find out what you really know.

Alongside coursework, build small things. A calculator, a text-based game, a script that renames your files, a simulation of something you find interesting. They do not need to be impressive; they need to be finished. Small projects teach what lectures cannot: how to start with nothing, how to debug your own confusion, how to decide when something is good enough. Two earlier posts on this site show what I mean: Games as a Way to Understand Algorithms and Learning by Simulation.

Take care of yourself, and keep your pace

Last, and most important: this is a long road, not a sprint. Sleep is not a luxury for students who have time. The US Centers for Disease Control and Prevention notes that enough sleep supports attention and memory, and recommends adults aged 18 to 60 sleep at least seven hours. An all-night session before an exam usually costs more than it gains.

Move your body, eat regularly, and keep some friendships and hobbies that have nothing to do with computers. You will be a better engineer for it. And be patient with yourself. Some concepts, such as pointers, recursion and concurrency, confuse almost everyone at first. Confusion is not a sign that you chose the wrong field; it is what learning feels like just before it works.

You do not need to be the fastest student in the room. You need to be curious, consistent and honest about what you do not yet understand. If you can manage those three things, the rest of the degree becomes much more manageable than it looks today.

I wish you a good first semester.

Sources: Dunlosky et al., “Improving Students’ Learning With Effective Learning Techniques” (Duke Scholars record), CDC, About Sleep