The frontier lab “Mandate of Heaven” is just whoever has the most compute available to serve the model that speaks the best English at that moment
You must have both to have the mandate
Frantically fixing a confusing product caused by frantic shipping is just more of the same.
Pause and step back. Get the team clear on what you’re building and why. Have clarity to guide the shape, what ships and what doesn’t.
Quality is a way of working, not a cleanup sprint.
@bolau_@paper I think it’s been great for me: every feature I built for almost 9 months used Paper!
I have no design background but it’s very quick to pickup and use, also faster than tools like Claude Design
Flying under the radar of today’s drama is Figma’s nonsensical handling of MCP availability lmao (Pi/OpenCode)
I literally just chose to use @paper a few months ago because it Figma MCP was unusable and it looks like the situation is as bad as ever. Very happy I moved on!
I used it really heavily at my last company (to the point I was a top 200 user globally):
- We had a Slack channel just for app feedback, where Devin would triage every issue or feature request.
- This was helpful because users would just talk to Devin to resolve their issue and an engineer would just go press merge if needed
- You could set it up with read-only permissions so it could go debug things deeply for async flows or infra issues
- It’s expensive but time to value was awesome so we just paid the premiums (Devin Review in particular was tremendously expensive but caught some good bugs in my experience)
It also let non-technical staff coauthor PRs with engineers, we could sort of babysit their threads and avoid having to setup local environments on their machines
I think a lot of the core experience seems commodified to people today but was a great unlock for us!
@goodhunt Good to get the endorsement, I never trusted Claude for these because the older models were kind of bad and slow (so you’d walk away and they wouldn’t work)