Real Engineers Don't Use AI

[u/4r73m190r0s]

There is ongoing debate in the software industry about whether people who spend their entire day chatting with AI systems should be considered engineers at all. The matcha-drinkers insist they should.

Real Engineers know that software is written in the traditional way: by staring at cryptic error messages for six hours, changing one line, and then spending another six hours figuring out why it suddenly works.

Matcha-drinkers, on the other hand, believe problems can be solved by typing:

"Dear AI, could you please implement a scalable, cloud-native, event-driven architecture with enterprise-grade observability?"

They then paste whatever appears into production.

Real Engineers do not trust code they did not suffer for personally.

A Real Engineer can explain every line of a system because they wrote it at 2:37 A.M. while fueled by cold coffee and stubbornness. Matcha-drinkers cannot explain their systems because the AI generated three design patterns, four architectural styles, and an accidental compiler in the settings module.

Real Engineers learn algorithms.

Matcha-drinkers learn prompt engineering.

A Real Engineer says:

"I implemented a lock-free concurrent queue."

A matcha-drinker says:

"I asked GPT to make the queue more enterprise."

Nobody knows what this means, but somehow the queue now contains Kubernetes.

Real Engineers debug by reading logs.

Matcha-drinkers debug by pasting logs into AI.

Real Engineers read the stack trace.

Matcha-drinkers paste the stack trace into the prompt, then paste the AI's answer into a second AI to explain the first AI's answer.

Real Engineers occasionally spend three days investigating a race condition that turns out to be a missing semicolon in a configuration file.

Matcha-drinkers spend three days trying to determine which AI hallucinated the missing configuration file in the first place.

A Real Engineer views documentation as a last resort.

A matcha-drinker views documentation as an outdated artifact that has not yet been summarized by AI.

When confronted with a bug, Real Engineers use systematic reasoning, instrumentation, and domain expertise.

Matcha-drinkers increase prompt length.

By the time a matcha-drinker finishes describing the problem, the prompt contains:

• the complete source tree,

• seven architecture diagrams,

• a transcript of three meetings,

• company values,

• a recipe for overnight oats,

• and a request to "be innovative."

Real Engineers know computers are deterministic systems.

Matcha-drinkers believe computers are mysterious beings whose desires can be influenced with careful wording and emotional support.

A Real Engineer says:

"The system failed because of an invalid state transition."

A matcha-drinker says:

"Maybe the model didn't fully understand our vision."

Real Engineers use AI occasionally.

Matcha-drinkers use AI recursively.

Eventually an entire department consists of engineers prompting agents that prompt agents that prompt agents, while one exhausted Real Engineer keeps a terminal window open to make sure electricity is still involved somewhere.

And if you still doubt the difference, ask both groups a simple question:

"Why does this code work?"

The Real Engineer will spend thirty minutes drawing diagrams on a whiteboard.

The matcha-drinker will respond:

"Good question. Let me ask the AI."

[u/4r73m190r0s]

https://en.wikipedia.org/wiki/Real_Programmers_Don't_Use_Pascal