Nobody said you did. He suggested several possibilities. One was working in industry to understand real-world development, deployment, or support needs. Another suggestion is considering real-world issues. That&#x27;s main one as the other merely supports it.<p>An example would be putting Racket to use on industrial scale projects with groups of programmers from different backgrounds. These would discover any pain points of language&#x2F;tooling plus opportunities for improvement. Doesn&#x27;t have to be Google: just practical, diverse, and outside Racket&#x27;s normal sphere.<p>The reason I used Racket as an example is that they already do some of that at least in their forums. Maybe some commercial sector but I lack data on that. They&#x27;ve evolved to be constantly more useful for both academic and practical stuff through such feedback.<p>If you doubt that or that they&#x27;re purely academic in a bubble, then feel free to share why. You may have data I dont have but Ive seen them adapt based on external feedback and usefulness in specific cases. Not a Racket user or insider, though.