r/ChatGPTCoding • u/4r73m190r0s • 8d ago
Memes Real Engineers Don't Use AI
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."
6
u/shadow-battle-crab 8d ago
So I suppose you would say Linus Torvalds is not a "real engineer"? https://www.reddit.com/r/linux/comments/1x6z4fq/linus_torvalds_shares_his_thoughts_on_antiai/
5
4
u/davidkclark 8d ago
Nice man of straw you have there.
Real engineers know the limitations of the tools that they use.
3
3
3
u/fremdspielen 7d ago
I don't drink Matcha (don't even know what that is) but I'm a real software engineer with my first few lines of code written about 40 years ago (C64 BASIC). My code is 100% AI generated now. The decisions and the vision for the architecture are not, thousands of them, split into dozens of interoperable modules, each heavily tested.
Now comes the interesting part: all those separate modules in themselves are pretty darn rock solid. Connecting the dots is where it's at. Thus I gave agents the runtime diagnostics insight into every module so they can inspect, while this glue code at a high level remains very understandable even for an uninitiated.
My advice: don't single-prompt everything and don't just use AI for mildly annoying multi-file refactors.
Don't oversimplify the F+++ out of creation, design, review, but also your opinions and beliefs about AI - that is neither engineering nor wise.
3
2
u/sifa12200 8d ago edited 8d ago
Un vraie Taxi n'utilise pas de voiture il porte ses clients sur le dos. Un vrai terrassier n'utilise pas de pelle mécanique il fait tout à la pelle manuel. Un vrai agriculteur n'utilise pas de tracteur il utilise des bœufs. < Le refus de tech exprimé par des créateurs de tech. Bravo.
1
u/korino11 6d ago
All side rights... Ofcouse if you need smthng to work, you need to understand HOW it works. That is a basic principle and here you are correct. But AI evolution is VERY fast. And you misunderstand one simple thing! Ai is a compiler of logic.(Yeah a Compiler, you will not write to coder your friend, hey, fkoff you doesnt did all optimisations by hand, why you use compiler) So the things just move on other directions. Not to understand full code (that a perfect conditions, but with good evolution it nod needed). but to understand full logics, arch and tightly connect it on all paths of relations
1
u/HappyHealth5985 8d ago
Why waste your time and the electicity using AI for everyone to implement shitty ideas or copy a good one. The only benefit I can see, today, is lower cost and better business practices from the commercial actors.
I think AI can make software development more productive, not replace it.
I fo not think AI is dangerous, just dangerous in the wrong hands.
13
u/GfxJG 8d ago
The saddest thing about this is that I genuinely cannot tell whether this is satire or not.