Accueil / Articles / What GPT Really Stands For and Why AI Engineering Is Still Engineering

Cet article est publié en anglais.

What GPT Really Stands For and Why AI Engineering Is Still Engineering

Unpack Generative Pre-trained Transformer, attention, fit and predict, and see why good AI work still depends on ordinary engineering judgment and better questions.

845 mots

Plenty of developers can say what GPT does without being able to say what it is. You use the words "GPT", "LLM", "transformer", "embeddings" and "RAG" for years, and it feels like understanding until you sit through a structured AI engineering course and every one of those words turns out to have a basement under it. A seven-day sprint is enough to find that out.

Generative, pre-trained, transformer

The acronym GPT expands to Generative Pre-trained Transformer. That sounds simple until you ask what each word is doing.

Generative means the model produces content. For a language model that's text, built by predicting what should come next from patterns it picked up earlier. Pre-trained means you aren't meeting a blank model: a big training run on enormous amounts of data has already happened before your first prompt.

Transformer is the word that makes people stop. It sounds like a product name, but it names a whole architecture, and one of the central ideas inside it is attention.

Attention and the handshake problem

A handshake puzzle gives a decent first picture of attention. Put five people in a room and have everyone shake hands with everyone else. Person 1 shakes four hands, person 2 shakes four hands, and so on, which gives:

5 × 4 = 20

That number counts each handshake twice, so you halve it:

20 / 2 = 10

In general form the count is N(N - 1) / 2. It's a combinatorics exercise, but it also models something bigger, which is the number of relationships between tokens. An attention mechanism doesn't walk through a sentence left to right and treat each word as an island. It has to decide which parts of the input matter to which other parts.

That's where Query, Key and Value come in. Treat them as a rough lookup system:

  • Query is what you're searching for.
  • Key is what information is available.
  • Value is what actually gets returned.

The real mathematics is a lot heavier, but this picture gives you a place to start. It also points at a habit worth keeping: if you can't say what a piece of code or math is doing, you probably don't understand it yet.

What a seven-day sprint covers

The material goes well beyond transformers: Python data structures, Pandas, missing values, outliers, preprocessing, machine learning models, evaluation metrics, APIs, deployment and RAG. Code that used to feel like something you just type starts to have consequences. Take this line:

model.fit(X_train, y_train)

You've probably seen that pattern a hundred times. It means the model is being trained on the training data you supply, learning its parameters from those examples. The next line is a different operation:

model.predict(X_test)

Here you ask the trained model to apply what it learned and produce predictions for data it never trained on. Both lines look nearly trivial. Knowing what they stand for is the hard part.

AI engineering is still engineering

The biggest lesson isn't about any library. A model doesn't cancel the need for good software design, and you still deal with:

  • checking and cleaning what goes in, and the quality of the data itself
  • APIs and how errors get handled
  • speed, testing and deployment
  • monitoring and security
  • a steady stream of tradeoffs

Sometimes the right engineering call is not to use AI at all. An LLM being able to solve a problem doesn't make it the right tool. If a deterministic rule handles the case reliably, cheaply and in a way people can inspect, bolting a probabilistic model on top tends to make the system harder to understand, not better.

Better questions beat buzzwords

Seven days won't make anyone an expert. It does hand you better questions, and those are worth more than another list of vocabulary:

  • What does this line of code really do?
  • Why does the design include this particular component?
  • How does the system behave when the input is bad?
  • Where does my data end up?
  • What is the model picking up from its examples?
  • Could plain code do this without a model?

The goal isn't to sound like you understand AI. It's to understand enough that you can build with it responsibly, and the first step is the unglamorous discovery that GPT means Generative Pre-trained Transformer.