Has early Scratch experience led to fulfilling careers?
Evaluating the Impact of Scratch on Professional Programming

In a recent post on X, the renowned developer @ID_AA_Carmack raised a provocative question regarding the efficacy of visual programming languages for children.
The Core Inquiry
John Carmack observed that while the Scratch environment is consistently marketed as a primary gateway into the world of coding, there seems to be a void of anecdotal evidence supporting its long-term professional utility.
"I still see the Scratch “visual programming” environment positioned as an introductory path to programming for kids, but unlike game modding, I have never heard a “success story”, where someone credits their early experience with Scratch as key to a fulfilling career. Anyone?"
Comparative Analysis: Scratch vs. Modding
Carmack suggests a dichotomy between "visual blocks" and the more hands-on approach of modifying existing games.
| Feature | Scratch | Game Modding |
|---|---|---|
| Interface | Visual/Block-based | Text-based/Internal files |
| Perceived Path | Introductory Pro | Practical Pro |
| Success Stories | Well-documented |
The Logic Flow
The following diagram illustrates the perceived pipeline of learning that Carmack is questioning:
Technical Considerations
From a mathematical perspective, Carmack is essentially questioning the probability of a professional outcome given a specific starting point:
To illustrate the difference, a "Scratch" logic block might look like this in pseudo-code:
when green flag clicked forever move 10 steps.
Whereas a modder might interact with actual code:
void OnPlayerJump() {
player.velocity.y += jump_force;
PlaySound("jump.wav");
}
Carmack's Current "To-Do" List
- Identify a developer who started with Scratch.
- Verify if Scratch was key to their professional success.
- Compare these findings against the "Modding" trajectory.
Ultimately, the post serves as a call for evidence to see if visual programming is truly a bridge to a career or merely a digital toy.