251–260 of 269 posts
This is just a series of ploys to make more marketing about fable. They know that if they make it api only nobody is going to talk about it. And knowing that openai will have a comparable model soon means they need to stir up some hype and make people use/talk about it as much as possible. And bluffing that access will be restricted until a specific date is just marketing. Like saying buy in the next 24 hours get one…
Despite paying for Claude access, I don't use Fable but I find this always changing policy quite exhausting to follow. There is 2x usage, there is no 2x usage, there is 2x usage but only x hours, there is no 2x usage, there is Fable access, there is no Fable access, there is Fable access till x date, there is Fable access till x + y date. This is just exhausting. I just want to open and usage the default model and wi…
This is just a series of ploys to make more marketing about fable. They know that if they make it api only nobody is going to talk about it. And knowing that openai will have a comparable model soon means they need to stir up some hype and make people use/talk about it as much as possible. And bluffing that access will be restricted until a specific date is just marketing. Like saying buy in the next 24 hours get one…
Yep, sounds like the usual time pressure tactics. Perhaps because no one's actually trying it. In the mean time, their vibe coded frontend doesn't actually let me use Fable because it thinks i'm trying to hack open source software. What I'm actually doing is debugging null pointer crashes due to data corruption in the closed source software i work for these days, but no, you dirty hacker, you can't do that. So let's…
This is just a series of ploys to make more marketing about fable. They know that if they make it api only nobody is going to talk about it. And knowing that openai will have a comparable model soon means they need to stir up some hype and make people use/talk about it as much as possible. And bluffing that access will be restricted until a specific date is just marketing. Like saying buy in the next 24 hours get one…
Yep, sounds like the usual time pressure tactics. Perhaps because no one's actually trying it. In the mean time, their vibe coded frontend doesn't actually let me use Fable because it thinks i'm trying to hack open source software. What I'm actually doing is debugging null pointer crashes due to data corruption in the closed source software i work for these days, but no, you dirty hacker, you can't do that. So let's…
Why release a model with such strict filters? It would be more sensible from a buisness perspective if they had sensible filters in place right away.
Earlier quoted context omitted.
It's great for feature development. It queries you about you intentions, creates a spec for you to review and modify, creates a plan for it to follow, then farms out the work to subagents. Crap on it all you want, but it makes LLM work predictable.
It does not make LLM work predictable. Try it on the same type of project twice and see. You think you're saving time but youd accomplish similar results with 2 or 3 skills.
If there's some clarity and structure with clear expectations, it seems to produce fairly reliable, consistent results, and the process of validating specs with Claude can yield all kinds of unexpected dead-ends or holes in the idea you had. I find this very helpful.
But I'm curious too, what are the skills you'd use instead? superpowers are just skills themselves.
Earlier quoted context omitted.
In the three years I've been vibe coding, it's the only way I've found to consistently and reliably build complex apps. How do you do it?
Three years? Vibe coding became a thing roughly 1.5 years ago, around Sonnet 4 release. How would you even compare models from 2-3 years ago to today’s? Is this satire?
Based on this definition, yep, I've been vibe coding since 2023. The products were less sophisticated, and I was copying and pasting one function at a time, but it worked. More important: it was something I couldn't do on my own.
The modern version is that bonafide engineers accept AI-generated code. It's a good thing I'm not a bonafide engineer.
Earlier quoted context omitted.
That's funny, cause I'd argue superpowers barely does anything, and you need a much more complex setup to gain value.
I find it very useful. What do you use that’s better?
It's just always been very behind the curve. I don't think you should use anyone's honestly. You should create your own shell base, and point to skills you find might add value, and add them. Then as you learn things about the shape of how things work, what you end up doing is rewriting them to follow your rules from what you learned.
What you'll find is, you'll have significantly better skills and systems.
Very expensive, not sure how it fits in with many companies seemingly trying to get employees using models at about Sonnet tier pricing. I certainly would never pay API rates for it, using ccusage I am seeing myself "use" $150-$400 worth of fable per day. ( https://www.theinformation.com/articles/tesla-caps-employee-... )
Do you have numbers for how much you were spending on Opus before with ccusage? If tokens are equal, Fable should only be twice as expensive, but I think it does a lot more work by default.