Vu Hung @vthung - Twitter Profile

vthung retweeted

about 2 months ago

Sam Altman (CEO of OpenAI): "You don't need to write prompts anymore. You need loops and graphs that write them for you." in 78 minutes he explains how to use LLMs better than almost anyone does Prompts → Agents → Loops → Graphs that is the whole difference between using AI and having AI work for you same model, same tokens, and the only thing that changes is the shape you run it in watch it today, then save the full graph engineering guide below

21

807

103

2K

290K

vthung retweeted

Superman

@thesupermannx

about 2 months ago

China published the most uncomfortable paper on vibe coding. ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds. The findings are brutal. The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning. They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself. Two major predictors emerged. Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds. But that wasn't even the main takeaway. Computer science achievement was a massive, dominant predictor of success. Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed. In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone. Why? Because vibe coding isn't about writing code. It’s about debugging logic. When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works. They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe. You can prompt your way past syntax. You cannot prompt your way past a fundamental lack of engineering intuition. The hype told us that learning to code is dead because language is all you need. The data just proved the opposite. To truly master the vibe, you still need to understand how the machine thinks.

thesupermannx's tweet photo. China published the most uncomfortable paper on vibe coding.

ETH Zurich tested 100 developers in a controlled, commercial-grade vibe coding environment to see who actually succeeds.

The findings are brutal.

The researchers tracked computer science achievement, written communication skills, and general cognitive reasoning.

They wanted to see what actually predicts vibe coding proficiency when you never touch a line of source code yourself.

Two major predictors emerged.

Written communication proficiency mattered. The ability to structure thoughts and articulate intent unambiguously in text directly impacts what the AI builds.

But that wasn't even the main takeaway.

Computer science achievement was a massive, dominant predictor of success.

Even when researchers controlled for general intelligence and reasoning skills, CS background still heavily dictated who built working software and who completely crashed.

In fact, CS knowledge contributed roughly twice the unique predictive variance of writing skills alone.

Why? Because vibe coding isn't about writing code. It’s about debugging logic.

When an AI agent builds a complex application and quietly breaks an edge case under the hood, a non-technical user looks at the glowing UI and assumes it works.

They don't know what questions to ask. They don't know what logic to challenge. They lack the mental models to recognize architectural catastrophe.

You can prompt your way past syntax.

You cannot prompt your way past a fundamental lack of engineering intuition.

The hype told us that learning to code is dead because language is all you need.

The data just proved the opposite.

To truly master the vibe, you still need to understand how the machine thinks.

312

7K

1K

6K

806K

vthung retweeted

Uncle Bob Martin

@unclebobmartin

3 months ago

I’m significantly older than you. I started coding in the late 60s. My current strategy is to not read any of the code written by my agents. That’s the only way I can take advantage of their productivity. What I do instead is to surround the agents with extreme constraints. Unit tests, gherkin tests, QA procedures, quality metrics, mutation testing, test coverage, and a plethora of others. In the end, I have very high confidence in the code they produce because they’ve had to run the gauntlet of all of my constraints and tests.

568

19K

2K

14K

5M

vthung retweeted