And then compare the $45B revenue from Anthropic to see if it's mostly break even or if one of Anthropic/SpaceX came out ahead on the contract.

This is not ground-breaking by any means, but achieving this in a 3B model and sharing the approach + weights advances engineering and certainly more contribution that 'silly little slop videos' imo.

This is merely speed of development and not the velocity of a company towards higher value. There are many PMs confidently (using the same AI tools), without a clear deep understanding of the user problems or why the requirements will be adopted by their target users (or even who the target users really are), writing these done elaborately.

So yes this will lead to faster end-end execution. But if the product is used or if it sits unused will depend on things beyond the above.

Consciousness *may* be something similar. If it is (e.g. the purest form of energy) then it is not inconceivable that it has some properties that not not tractable if we only look at more granular manifestations of it.

Who is We? I thought software engineers were going to be redundant and AI could do it all itself? (not to take anything away from Claude code + Claude both of which I love)

For example, backspin/underspin balls will move slower after the first bounce and feel 'damper' while topspin will jump. So it's def. possible (and in fact reliable) to read the spin from the spin and trajectory of the ball.

The main remaining part is the poor docx / pdf / final output but will create a skill/workflow to get around that.

Worked really well end-end!

A simplified but clarifying way to think about it is that MCP exposes all the things that can be done, and Skills encode a workflow/expertise/perspective on how something should be done given all the capabilities.

So I'm not sure why the article portrays one to be conflicting with the other (e.g. "the narrative that “MCP is dead” and “Skills are the new standard” has been hammered into my brain. Everywhere I look, someone is celebrating the death of the Model Context Protocol in favor of dropping a SKILL.md into their repository.").

You can just not choose to use a skill if it's not useful. But if it's useful a skill can add to what an MCP alone can do.

If your (well paid) job is to write and communicate clearly, and for a major announcement you come up with this...not much left to say.

So its a pleasure to see a thoughtfully done product landing page (which strongly signals that the same care will have gone into the product). The page is performant, no gratuitous visual effects. It clearly highlights the core product value propositions in the context of product visuals. Addresses key hesitations clearly and upfront (e.g. no cc required, pricing information), and a simple, obvious call to action.

Hopefully more people follow this template than the slop generated by auto generators.