Good is debatable. The docs I want point out the weird shit in the system. The AI docs I've read are all basically "the get user endpoint can be called with HTTP to get a user, given a valid auth token". Thanks, it would have been faster to read the code.
finally! I'm building an app that's essentially a "sidecar" to an llm subscription and works via mcp and has a web ui to make reviewing deliverables easier, uses the user's subscription for intelligence instead of requiring to pay for tokens inside the app. The problem until now is I couldn't trigger AI work from the web ui, that limitation will be soon gone, it fixes a huge ux issue for me, I honestly thought it would happen sooner but I'm glad the industry is catching up.
it's gambling until you learn how to set up proper harnesses then it just becomes normal administration. It's no different than running a team, humans make mistakes too, that's why we have CI pipelines, automated testing etc... AI assisted coding "JUST" requires you to be extra good at that part of the job.
Was the product. It's fundamentally unsound, but beyond that, why would you be in that thing? The Metaverse had barely any content worth using, there was no reason to buy it beyond disposable income and novelty.
I think it was totally predictable, I was telling my colleagues at Meta back then the Metaverse was completely toast in 2020 for a variety of reasons that only Mark Zuckerberg in his infinite wisdom couldn't see clear as day.
The Metaverse was not something that Meta was good at, they went about it all wrong and it was doomed to fail.
it's not the CLI, it's the model. The model wasn't trained to do that kind of work, was trained to do one shot coding, not sustained back and forth until it gets it right like Claude and ChatGPT.
It will be like that at some point soon, just not now. Are you trying to make the point that because this technology is not yet perfect the fact that it can already do so much is unimpressive?
reply