AI output is only as good as the context you give it.
If you simply ask someone “Bring me an ice cream”, you’ll most likely not get the ice cream you actually wanted.
If you ask “Bring me a chocolate ice cream”, your odds improve a little.
But if you ask “Bring me a Magnum Double Classic chocolate ice cream”, your odds of getting exactly what you want are almost 100%.
AI doesn’t magically know what you want (yet 👀), so the better the context, the better the output.
In software development, this is critical.
Without the right context, the end result can easily become AI slop that takes more time to fix than it would have taken to build properly from scratch.
You dont want a yacht. You dont want a big house. You dont want a super car, a $40,000 watch, or shoes you worry about getting dirty. You want free will.
You want to wake up naturally on a Tuesday and you want to go to bed when you’re done having fun. You want to say yes to everything that excites you without having to request time off. You want to go to the the gym at noon, in absolutely no hurry. You want to spend 18 hours a day doing what you love. You want to be exactly where you desire being, always. You want to spend as much time with the people you care about as possible.
You’re saying you wanna be rich? In what?
Effective today, we are:
1) Doubling Claude Code’s 5-hour rate limits for Pro, Max, and Team plans;
2) Removing the peak hours limit reduction on Claude Code for Pro and Max plans; and
3) Substantially raising our API rate limits for Opus models.
@trq212 Would be interesting to understand if you have some rules/specific workflows with different Claude models to ensure tokens are used wisely. That’s one of the most difficult parts in my opinion, even on the Max plan
My first app is now live on the App Store 🥳
It’s a simple self-improvement app designed to help you stay consistent with a daily rhythm: make promises, focus on them, then review what you got done.
More features are coming soon 👀
Check out Promitto:
https://t.co/FeMEeTEnf8