Shao Meng: The Claude Code era still needs senior front-end engineers
Citing Lovart as an example, Shao Meng pointed out that in PGC+UGC communities, covers uploaded by users range from small images of a few KB to ultra-high-definition large images of tens of MB, and non-developers often do not proactively pay attention to performance. He believes that the Skills of Claude Code / Codex focus more on code architecture performance and do not cover image and video resource issues, so senior engineers who can identify and drive performance issues across teams will only become more important in the AI programming era.
Topics
View original postYou say front-end is dead? As long as you have Codex / Claude Code, anyone with hands can build a website? Then could I ask you "AI Native" product managers and designers to remember to pay attention to performance when doing Vibe Frontend Coding 😂 Performance score 47, piles of large gifs and large pngs, and many more issues that don't even need a deep look—simply a negative example of front-end performance ... https://t.co/ElOmUw8pu5
View original
听你们说我们前端已死？ 只要有 Codex / Claude Code，有手就能做网站？那能不能拜托你们这些 “AI Native” 的产品经理和设计师们，Vibe Frontend Coding 时，记得关注一下性能 😂 Performance 47 分、成堆的大 gif、大 png，更多问题都不用深看，简直前端性能反面典型 ... https://t.co/ElOmUw8pu5
Body · AI translation
First: sorry, Lovart, I'm just using you as an example 😄
The reason I used Lovart is mainly because of the nature of its product: a community- and template-style platform combining PGC + UGC, where the covers users use can vary wildly—they might be blurry little images of a few KB, or ultra-high-definition images of tens of MB, the kind that are tens of thousands by tens of thousands... The design and operations teams are no exception to the latter problem, exporting original images straight from design software and shoving them directly into the operations backend...
At this point, if you're a non-technical person who knows nothing about front-end engineering, I really don't quite believe you'd consciously pay attention to performance issues, especially in the early stage when all kinds of data are still in the mock phase and look ideal.
Going further, even if your Claude Code / Codex itself has Skills that pay attention to front-end performance, it will focus more on the performance of the code architecture itself, and won't cover the various image and video resources that may arise in the future.
Going further still, even a professional front-end developer who has experience with and awareness of this kind of resource issue may let the problem slide—because of poor communication with the product design and operations teams, or because performance concerns have to give way to visual effects—until customer complaints arise on a large scale, or the boss tries it out and finds it laggy 😄
So, within a team, having an engineer who is experienced in engineering, able to spot problems, and willing to raise and push for solutions across teams is still important in the era of Claude Code / Codex—and will only become more and more important!