Hacker News Reader

I remember bugs always end up being more expensive then the first time I implemented the feature… so for me always sol always max… I don’t want to pay for a bug later

View on HN

Using Sol or Fable for implementing is like having your Principal Staff Engineer with 30 year tenure routinely write CRUD functions for a REST API.

You use the big models to plan. Not just the overall plan, but which files need to be edited etc. Then they give that to the lower end model. So Luna or Sonnet, which are perfectly capable of following instructions and still creative enough to not get stuck.

> Using Sol or Fable for implementing is like having your Principal Staff Engineer with 30 year tenure routinely write CRUD functions for a REST API.

A Principal Staff Engineer who costs $2400 a year and never feels any work is beneath them? Hell yeah.

OK OK, usage limits

If you have bcherny levels of token quotas, you can use Fable for everything =)

The rest of us need to optimise a bit.

Where I'm at too, though max overthinks like crazy. xhigh is my sweetspot.

Reply on news.ycombinator.com