miranaproarrow

wait this is new to me so is this like a different kind of tla?

Exactly! THANK YOU!!

I'm not saying Its reassuring, and I think all your points are valid.

The only difference right now between my manager getting this claude design web app to production are the infrastructure and interfacing with it.

To get to prod it has to go through our monorepo pipeline, which currently requires using a cli, using a cli/command prompt requires using terminal, getting claude to use terminal also requires you to even know what a terminal is and spawning claude in there. Steering claude to do all that without knowing what or how to use a terminal is, and setting up your environment still all requires some technical knowledge or the language to tell claude to do that.

That's just getting to production. What about getting the claude design which is in a web environment without any context of all that monorepo with all its backend services. So all the interactivity that are all faked or mocked. Has to be converted to a real react components that's actually wired to the Rest API. How do you get the manager to speak to claude to do all that, with claude only being on the claude design harness?

What if manager designed a new feature that the backend service doesn't support? now your asking to make changes on the backend too.

So I think your points are valid that sure we may get to this at some point. But how exactly without the manager having to learn some technical language of steering claude and the infrastructure to support it.

My manager who vibe coded our entire webapp in claude design. Has difficulty understanding why its still not production ready.

My job is to wire to our backend data, and a lot of these wiring require me to be in there and actually think about the features. These take time, and I just haven't figure out a way to speed this process up with Claude.

Ive never read a paper cover to cover before but after wrestling with opus 5s english this paper is such a relief to read, its like my eyes has been washed off opus stink

gate= some sort of a guard or test

name= a variable name or fields

load bearing= coupled dependencies that can break other things if you change it

Ive given up trying to fight claudes language, and Im afraid Im getting used to it and can even understand what claude is saying faster or should I say I can parse it faster now.

whats troubling here is that one of the anthropic devs on twitter or github don't seem to acknowledge this issue, If they don't acknowledge there's nothing for them to fix

how is lean different from tlaplus for helping you with reasoning during the design phase?

I literally just discovered tlaplus last week after struggling with reasoning about the explosion of permutations about configuration policies Im designing, and Im still learning the math but Im finding it easier to reason with tlaplus than in code is lean like that?

claudes/codex performance suffers after 250k anyway and my workflow reset after every 200 so this is a non-issue

Do you have specific SDR in mind? I thought the v2 dongle doesnt have the range of Wifi? SDR is something Ive just recently want to learn to help me understand electromagnetism