jackyli02

The landing page feels quite Claude design-y. Is that what you used? If so it's one of the better Claude design landing pages I've seen. Nice work!

The framing of tests-as-source-code resonates, but I think it extends further than testing specifically. From my experience building with AI coding tools, I spend increasingly more time reviewing and validating code than writing it. You end up acting like an engineering manager running a team of junior devs: scoping tasks tightly, reviewing output critically, deciding whether what came back meets the requirement. Tests are one expression of that, but so is code review - they're both forms of validation. The broader shift is that the developer's primary output is becoming judgment about correctness rather than the code itself.

Essentially the same thing Elon has been saying for years. Physical AI plays to a real Chinese advantage: manufacturing density. China doesn't just have cheap labor, it has the iteration speed that comes from having chip fabs, robotics assemblers, and end-user factories within the same industrial corridor. Compared to foundation models, the gap in embodied AI narrows fast when the bottleneck shifts from compute to real-world manufacturing.

This is explicitly framing hand-written code as the wrong workflow. That's a significant shift from even six months ago. My sense is this will become more common at companies building on top of APIs and integrations (Zapier's core domain), where the code is more glue than architecture. Whether it scales to systems-level work is a different question. The failure modes of agent-written code are still poorly understood, and "built mitigations" is doing a lot of heavy lifting in that job listing.